Query response and Map Source

[cailurus]

Hey guys, I'm very eager to try this awesome plugin, but I was confused about the matching between query response and Map Souce in this plugin.

Per my understanding, this plugin will render the links/endpoints by using the JSON data in Map Souce, as you guys provide in README. So every time I need to copy the response from my query and paste them into the MapSource by the editor manually?

[daldoyle]

Hi there, One of our goals of this visualization is to show a fixed topology. For example if we have a circuit going from A to B and it stops collecting data it should not disappear but instead render as a grey line or something like that. In order to accomplish it, the topology is independently defined from the query result. This also means that we don't need to have all the topology information sitting in the same measurement database. If you are trying to dynamically visualize a topology based on an arbitrary query result, ie some fields representing the A and Z lat/lon, then it does not support that unfortunately. There are other visualizations in Grafana that do, though I think they only visualize a single point on the map and not a line between two points. Dan Doyle Network Data Collection and Analysis 1-812-856-3892 ***@***.***

…

On May 10, 2021, at 10:44 PM, More Zhou ***@***.***> wrote: Hey guys, I'm very eager to try this awesome plugin, but I was confused about the matching between query response and Map Souce in this plugin. Per my understanding, this plugin will render the links/endpoints by using the JSON data in Map Souce, as you guys provide in README. So every time I need to copy the response from my query and paste them into the MapSource by the editor manually? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#123>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXF7JDNBOPYKCNYJDKZY73TNCKXPANCNFSM44T5XYAQ>.

[cailurus]

Hi Dan,

Thanks for your quick reply. A fixed topology is good for me too. The thing I want to clarify is the matching process between query response and the MapSource JSON.

For example, I get the query response from my source (SQL/InfluxDB or any DB), and then how I can let this plugin render it? This plugin will read and render the data in every Layers' MapSource. So the only way for me is to copy the query response, double click the 'MapSouce,' and paste it via JSON Editor?

[daldoyle]

There are some examples of how this lines up: https://github.com/GlobalNOC/globalnoc-networkmap-panel#datalist-object-returned-by-the-tsds-datasource The example in this case is given using one of the drivers for an in-house timeseries database but that's not important. We have successfully used this map to viz data out of elasticsearch and others just fine. The important part is lining up the "target" names from your datasource to the endpoint names in your topology. That's how the plugin will know how to associate which datapoints from the response get visualized where on the map. Anything in the topology without a corresponding target in the data gets left as the default coloration. Dan Doyle Network Data Collection and Analysis 1-812-856-3892 ***@***.***

…

On May 12, 2021, at 9:37 PM, More Z. ***@***.***> wrote: Hi Dan, Thanks for your quick reply. A fixed topology is good for me too. The thing I want to clarify is the matching process between query response and the MapSource JSON. For example, I get the query response from my source (SQL/InfluxDB or any DB), and then how I can let this plugin render it? This plugin will read and render the data in every Layers' MapSource. So the only way for me is to copy the query response, double click the 'MapSouce,' and paste it via JSON Editor? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXF7JARZCDOEM4USSNQXFTTNMUMHANCNFSM44T5XYAQ>.