#New world map code#
#New world map series#
#New world map free#

an optional location name field (shown in the mouse over).This is used to calculate where the circle should be drawn. This is used to give the circle a value and determines how large the circle is. Similar to the Elasticsearch query above, 3 fields are expected (2 of them are mandatory) If a datasource can return Table Data then on the Metrics tab in Grafana choose the FORMAT AS Table option. Any database that can return data in Table Format.geo_point field that provides the geohash value.Location Name (optional - geohash value will be shown if not chosen).

#New world map free#

This is free text and should match the aggregation used (Count, Average, Sum, Unique Count etc.) Three fields need to be provided by the ElasticSearch query: The Geo Hash Grid has a precision option where 1 is the highest level and 7 is the lowest. Grafana has a new bucket aggregate for Elasticsearch queries - Geo Hash Grid that allows grouping of coordinates. The Geo-point data type with geohash indexing in Elasticsearch can also be used as a datasource for the worldmap panel. Using a JSONP endpoint (if you need to wrap the JSON to get around CORS problems):įor some details on troubleshooting JSON/JSONP check #47. If you have your own endpoint defined it must be reachable from the client side, as it is approached by client's browser. The endpoint used here is for the demo version of worldPing. Using a JSON endpoint to return a custom list of locations: Under the Worldmap tab, choose either the countries or states option.

#New world map code#

Use a Group By clause on the field containing the country code and a Then by clause with Date Histogram by (or corresponding date field). The Group By clause should be the country code and an alias is needed too. See the image below for an example of a graphite query.Įxample dashboard for Worldmap with Graphite queries on the Grafana play site. Use the aliasByNode function to point to the field containing the country code.

#New world map series#

Here are some examples of Time Series Queries Graphite Query if you have 3 countries with values 1, 2 and 3 or 100, 200 and 300 then you will get one small circle, one medium circle and one large circle. The size of the circle depends on the value of the matched metric. The current way to do that is via a JSON endpoint that returns a json file with location data (See Map Data Options) If you want to match to other data than countries or states, then you will have to provide custom location data. If a metric name matches a country in the list of countries then a circle will be drawn at that location. This works by matching country codes (like US or GB or FR) or US state codes (TX or NY) to a metric name.

A JSONP endpoint that returns a list of locations.

A JSON endpoint that returns a list of locations.

The following location files are included in the plugin:Īlternatively, you can provide your own location lists by using: So using these, the Worldmap panel will draw one circle in Colorado, USA with the value 75.654324173059. This query contains both data (the value 75.654324173059) and a location (the geohash 9wvfgzurfzb which is in Colorado). Here is an example of Table data from InfluxDB: 'series': [ Table data is tabular data with columns and rows. If the data is in the Table format then it should have a column that is a geohash or two columns that contain the latitude and longitude (together with the columns for the data). With this example data there will be two circles drawn on the map, one for Sweden and one for the United States with values 183224.

The Worldmap will then match the metric name (target in the example data) with a key field from the location data. Location data should be in the JSON format and should be an array of JSON objects with four properties: [ Here is some time series data from Graphite: [ In other words, a typical query for a time series database.

Time Series data contains a timestamp, a metric name and a numeric value.

json endpoints that return a list of locations and their coordinates.

json files with locations and their coordinates (the plugin includes list for countries and US states).

The list of locations can be provided in several ways: The list of locations can come from a file or an HTTP endpoint. That key is usually a country code or city name. If it is in the Time Series format then the metric name needs to match a key from a list of locations. It can be in the Time Series format or in the Table format. The data comes from a database query: Prometheus, InfluxDB, Graphite, Elasticsearch, MySQL etc. The Worldmap panel needs two sources of data: How The Worldmap Works (Theory and Examples) It can be used with time series metrics, with geohash data from Elasticsearch or data in the Table format. The Worldmap Panel is a tile map of the world that can be overlaid with circles representing data points from a query.