You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having countries as datasource and making a time series query on mysql that get the country name
What I would like to success and which does not display any points:
Having JSON endpoint with custom locations as datasource and make a time series mysql query that get the corresponding key from the json endpoint as location
=> The mysql query is working, it's the same as the one to get the country but getting the key instead of the country
=> The json endpoint is formatted as your example with a name, a key, a latitude and a longitude.
Do i miss a special configuration or something ?
The text was updated successfully, but these errors were encountered:
Hi
In my case I have been able to construct SQL query as this
SELECT
UNIX_TIMESTAMP(time) as time_sec,
data as value,
location as metric
FROM worldmap
WHERE $__timeFilter(time)
GROUP BY metric ORDER BY time DESC
And then use a JSON or JSONP as a Map Datasource. Works as described.
Be aware, that
URL must be provided so client can access it. If you put JSON URL to your browser it must be displayed. In my case I use SSH port forwarding, so Grafana URL is http://127.0.0.1:53000, but the JSON endpoint is http://10.60.1.28/mappoints.json
Do you serve Grafana from the same source as JSON? In not be aware, CORS might be the problem.
Check what that is and how to verify, eg. CORS on Mozzila page
If you switch to JSONP, be aware, that JSONP is different from JSON. #47 - for howto on JSONP
Hi,
What I succeed to do:
What I would like to success and which does not display any points:
=> The mysql query is working, it's the same as the one to get the country but getting the key instead of the country
=> The json endpoint is formatted as your example with a name, a key, a latitude and a longitude.
Do i miss a special configuration or something ?
The text was updated successfully, but these errors were encountered: