grafana-flowcharting
grafana-flowcharting copied to clipboard
algenty
BETA 1.0.0d published : many bugs fixed and many optimizations
https://algenty.github.io/flowcharting-repository/archives/agenty-flowcharting-panel-1.0.0d.220606199-SNAPSHOT.zip
Main changes :
Known issues
- Shared cross on grafana 8.x (minor)
- Flow animation on arrows (minor)
- External image from diagrams.net not displayed (minor)
Added
- Convert sync method to async : render graph before update states (x2 faster)
- clean dirty code
- Support last version of grafana (8.5.x)
- New initialization engine for drawio libs
- New draw.io libs (17.x 2022-04-23)
Hi Arnaud, Great work, just installed your new snapshot.
I found an issue with the regular expression match for metric names in the rules, it sometimes finds too much and sometimes finds not enough matches. In the first figure it finds only one match for active (P) and re-active power (Q) with regular expressions /F\d:P_L[123]-active/ and /F\d:P_L[123]-reactive/, while the following metrics are available:
Office-F0:L1 | Office-F0:L2 | Office-F0:L3 | Office-F0:P_L1-active | Office-F0:P_L1-reactive | Office-F0:P_L2-active | Office-F0:P_L2-reactive | Office-F0:P_L3-active | Office-F0:P_L3-reactive | Office-F0:Psum-active | Office-F0:Psum-reactive | Office-F0:Isum | Office-VT:L1 | Office-VT:L2 | Office-VT:L3 | Office-VT:Vsum
The rule for P is as follows to match active power metrics and color and append matched metrics with newline:
Somewhat later it looks like this, i.e. there are 4 P values (while there should only be L1, L2 and L3), but not only one value for Q (should be three):
I also added the CSV download, so you can see what metrics and values are available: Feeder Office-F0-data-as-seriestocolumns-2022-06-07 12 28 10.csv
Kind regards, Dennis
Another weird and probably associated thing, when I select a VT datasource that is not available (VT), duplicated values are shown from the CT datasource (current, active+reactive power).
working with selected VT2 (here it is supposed to show 4 currents: L1, L2, L3 and L4/Neutral):
weirdnes with selected unavailable VT:
Hi @bijwaard Thanks for your feedback, i'll try to reproduce it Have you notice best perf ?
Didn't focus so much on performance yet, but dashboard seems to load quite fast now. Tooltips were not working by default, had to disable/enable them in flowcharting settings to get them working again.
The loading and tooltips have become quite slow in a more complicated diagram, and CPU for this tab is constantly over 100%. I have to wait seconds until tooltip shows. First a straight line shows, and then the actual graph is displayed some seconds later.
80% of time seems to be spent in the yarn cache
And some time later I got an exception while tyring to retrieve a tooltip:
Trace during loading of dashboard taking over 42seconds:
Hello, we are seeing the same problem when working with dashboards, when adding a large number of mapping rules (from a hundred rules), dashboards are rendered for a very long time from thirty to two minutes. For faster rendering of dashboards, I divide it into small logical parts and write the most accurate queries without using /.*/, I will also attach a screenshot of the performance tab in the DevTools.
Hi @algenty, do you have any idea of an official release soon? Is version 1.0.0 snapshot ready to use in production?
Not yet just need Time sorry
Le ven. 7 oct. 2022 à 09:35, meshkov @.***> a écrit :
project is dead again
— Reply to this email directly, view it on GitHub https://github.com/algenty/grafana-flowcharting/issues/355#issuecomment-1271223882, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALGVW5LEELARMAOJ5B7IRXDWB7HELANCNFSM5X63NNPA . You are receiving this because you were mentioned.Message ID: @.***>
Thanks to keep up. Do you consider it ready to use in production? As I don't see any major issues..
Not at the moment, I have changed job and maybe I found a sponsor I hope to fix the issues on November
Le mar. 11 oct. 2022 à 10:31, Thomas Casteleyn @.***> a écrit :
Thanks to keep up. Do you consider it ready to use in production? As I don't see any major issues..
— Reply to this email directly, view it on GitHub https://github.com/algenty/grafana-flowcharting/issues/355#issuecomment-1274306055, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALGVW5P6I7KSDKWWNK6XZQDWCUQVZANCNFSM5X63NNPA . You are receiving this because you were mentioned.Message ID: @.***>
-- Arnaud GENTY Tel : (+33)6.23.08.30.14 Email : @.***
happy user of 1.0.0d. thank you @algenty I can't wait for the next version.
hi!, howto install this snapshot? i try to copy files but grafana disabled it because checksum and signed are not valid.
I normally just move the old flowcharting folder in the plugin directory away and unzip the snapshot in the plugin directory. Then restart grafana.
My plugin folder looks as follows (you may have to correct user, group and permission after the copy: chgrp -R grafana:grafana /var/lib/grafana/plugins):
$ sudo ls -lsa /var/lib/grafana/plugins/
total 36
4 drwxr-x--- 9 grafana grafana 4096 Sep 5 10:48 .
4 drwxr-xr-x 8 grafana grafana 4096 Feb 14 13:47 ..
4 drwxr-xr-x 4 grafana grafana 4096 Feb 16 2022 ae3e-plotly-panel
4 drwxr-xr-x 4 grafana grafana 4096 Feb 16 2022 agenty-flowcharting-panel
4 drwxrwxr-x 9 grafana grafana 4096 Jul 15 2021 alexandra-trackmap-panel
4 drwxr-xr-x 3 grafana grafana 4096 Sep 5 10:48 golioth-websocket-datasource
4 drwxr-xr-x 5 grafana grafana 4096 Feb 16 2022 marcuscalidus-svg-panel
4 drwxr-xr-x 5 grafana grafana 4096 Feb 16 2022 natel-plotly-panel
4 drwxr-xr-x 3 grafana grafana 4096 Feb 16 2022 simpod-json-datasource
Btw. I'm still using 1.0.0b on this machine:
Kind regards, Dennis
This might be a stupid question, but I am wondering what 'Shared cross' means? I googled but found no clue. Thanks in advance.
Hi jshpng,
I think Arnaud refers to the shared graph crosshair that you can activate with MOD-key + o, see help (h key) for all grafana keyboard shortcuts. With the shared crosshair, you get dashed vertical line in each graph, in FlowCharting panel you'll see the value's change accordingly when moving the line in a graph.
You pay have to set the shared crosshair in dashboard settings as well:
Kind regards, Dennis