Publish Dashboards at Grafana

1

Hey guys,

It’d be great if you published the Microgateway Dashboards directly at Grafana. Grafana dashboards | Grafana Labs yields no results today…

Motivation: with the dashboards at Grafana we could get the new versions probably with our IaC / GitOps approach.

Let me know what you think about this. This is a “nice-to-have” for us…

Thanks!

2 Likes
2

Hi Markus

Thank you for reporting this idea. We already discussed this feature request but it’s not planned because we see the following disadvantages:

  • We provide not only one dashboard, but many. This makes it difficult for our customers to oversee which dashboards are available for a certain Microgateway release and install them (customers could miss new dashboards).
  • We improve our dashboards over time. It could happen that newer dashboards rely on the existence of a certain metric or log format which is only available in a specific Microgateway version. Therefore, a dashboard version is tested only with the corresponding Microgateway version (and should be used with this version).

Nevertheless, we improved the customer experience with Microgateway 4.6 and publish the dashboards on the GitHub release page. Please find below the manual about the dashboards (this description will be published in the Microgateway 4.7 documentation):

===

  1. Go to the Airlock Microgateway GitHub Releases page.

  2. Select the latest maintenance release matching your Airlock Microgateway version.

    • For example, if you are using Airlock Microgateway 4.6, choose the latest 4.6.x release (e.g., 4.6.1). Avoid selecting a newer version as it may not be compatible with your current system setup.

  4. At the bottom of the release notes, download the file named dashboards-<version>.zip that contains the JSON files representing the Grafana dashboards.

  5. Unzip the archive to a local folder.

  6. unzip dashboards-<version>.zip -d dashboards

  7. The Grafana dashboards can be imported either manually or via the CLI of the corresponding deployment platform (e.g., Azure).

===

Does this make your IaC/GitOps life easier? Does this approach help you to automate your environment?

Cheers

Stefan

3

Sorry for the late answer.

It helps to make the deployment easier, thanks! We haven’t really looked into automate it in much detail…

1 Like