algenty/grafana-flowcharting

Invalid Xml Definition : Grafana 9.0.6 Flowcharting 0.9.1

cgauloise opened this issue · 4 comments

cgauloise commented

Hello, I am new to Grafana
I encounter a problem that was reported 2 years ago (issue #185). I used draw.io and did the correct step to get a clean XML file (click on menu Extra > edit diagram). I have an error when I try to import in the "Source content" case my XML : invalid xml definition.

I tested my file in another environment(Grafana 7.4.2 and Flowcharting 0.9.1 with no Internet access) and it works, I don't have any error and the graph loads in the panel. But in my actual environment (Grafana 9.0.6 and Flowcharting 0.9.1 with no Internet access), neither my graph or the default one can load.

Waiting for a reply, I'm going to try with these versions in my integration to see how it goes.

Did anyone here encounter the same issue ? Is there any solution or something I missed ?
Thanks

linuxwind commented

+1

I have the same issue.

Grafana version: v9.2.0
Flowcharting Plugin version: 1.0.0d

image

  • 👍1
hsiaotingg commented

+1
grafana version : 9.2.4
flowcharting plugin : 0.9.1

I have the same problem!
Interesting, this XML is from demo site, it couldn't work, but it seems good at demo site
image

RDoejode commented

Did any of you that had the problem found a resolution to the problem? I am having a similar issue. Thanks

mlclark-resideo commented

I ran into this same error. For some reason, the fix for me ended up being turning off unified alerting, which was causing errors in Grafana. Once the errors were gone, I no longer got "Invalid Xml definition" for the Flowcharting demo XML.

Diagnosis

To see if this could be your problem, run the following:

sudo cat /var/log/grafana/grafana.log | grep level=error

If you see "Running maintenance failed" messages from the alertmanager, you might have the same problem as me, and the following fix should work.

Solution

Turn off unified alerting and restart Grafana. To do this, edit grafana.ini:

force_migration = true

[unified_alerting]
enabled = false

(The force_migration flag is needed because otherwise Grafana will throw errors on restart about deleting unified alerting data, even if you don't have any unified alerting rules.)

After editing the config file, restart Grafana (e.g. sudo systemctl restart grafana-server).