Giving the Grafana Worldmap Panel some love

Dear Grafana Worldmap users,


We recently had the chance to dedicate some time to the Grafana Worldmap Panel. After adding some options here and there, some of them coming from the community already [1-4] (specifically we aimed at the drill-down feature here, thanks!), the code has been refactored a bit and finally the user interface has been cleaned up and restructured. We hope you like it and will be happy to hear about any thoughts you might have.


You will get a decent overview about the changes by having a look at the walkthrough (mostly screenshots) at:

TLDR; More of a text-only changelog is available from CHANGELOG to reduce reading time if you prefer a quick overview.

Testing & Feedback

We are confident this is now in a good shape so we will be happy about testing and feedback from the community. Please be aware that we primarily use InfluxDB, so we would be especially happy to hear if this still works for people using different data sources.


The most recent version can always be installed side-by-side of the canonical Worldmap Panel like

# Install most recent version side by side
grafana-cli \
  --pluginUrl \
  plugins install grafana-worldmap-panel-ng

# Restart Grafana to activate plugin
systemctl restart grafana-server


We have been able to integrate these fine contributions from the community. Thanks, @ryft, @fabienpomerol, @dtheb and @leonhardhaas!



Bottom line

We haven’t made a pull request yet to let things settle a bit and to test this more intensive on staging, maybe a few more things will get added over the course of this journey. However, we would like to ask @daniellee, @bergquist, @ryantxu, @prokopd and @torkel if you would want to take this in general and what it would take to bring this into mainline.

Thanks already and with kind regards,

As a preview, here are some screenshots of the editor panel, which has been slightly improved and carries a few more options.

Editor screens


Thanks for putting all this work into the panel. We developed this panel for the WorldPing app and have not prioritized adding new features (over working on core Grafana) so great to see the community chipping in.

All those features look like good additions so I’ll review your changes. And when you feel ready then we can try and get them all into mainline Worldmap.

1 Like

Hi there,

Others have tried 0.3.0-dev as well and have been running into the same issue with Prometheus data in timeseries format, so we are tracking this at

Thanks, Per!

Left: Timeseries format. Right: Table format. Both InfluxDB.


Hi there.

We have been able to resolve the issue referenced above. The revamped Worldmap Panel should also accept data in timeseries format appropriately again.

The current release is 0.3.0-dev9 and can be installed by invoking

grafana-cli --pluginUrl plugins install grafana-worldmap-panel

Left: Timeseries format. Right: Table format. Both InfluxDB.

Thanks again for reporting this, testing the overhauled Worldmap with the most popular TSDBs out there is important to us, but as we are usually only running InfluxDB, we need the support of the community here.

Edit: Per confirmed at that 0.3.0-dev9 now works like a charm with data coming from Prometheus in timeseries format.

With kind regards,

Hi ,
How to login this page, please mention the credentials.

Hi Vishnu,

thanks for your interest. We haven’t migrated to Grafana6 yet (it’s just a development instance), so the canonical entrypoint where you can actually see data is

However, we don’t offer public logins on that page.



Thanks for your reply , please give me a guide for How to signup the web site. 2

Dear Vishnu,

We don’t offer logins on that instance of Grafana.

However, we recognized that public anonymous access for viewing the dashboards there was broken and now got restored after we recognized that. Thank you so much for having us look into this.

With kind regards,

Dear community,

we just wanted to let you know that we have been able to mitigate some rendering woes with Worldmap which seem to be more likely happening on Grafana > 6.x. We experienced the same thing occasionally when working on the codebase and now recognize that the issue also hit others.