#GRAFANA DASHBOARD INSTALL#
#GRAFANA DASHBOARD UPGRADE#
#GRAFANA DASHBOARD SERIES#

Modify the deployment to include the modified dashboard Note that you will likely have multiple references to the datasource parameter in your dashboard.json file.

If the original datasource isn’t called Prometheus in Grafana (let’s say, it’s called dev-Prometheus) you need to find all the references for it in the.

This process is rather easy if you’re using an existing template. However, if you’re exporting a live dashboard from Grafana, there are a few “gotcha’s” that you should pay attention to: Note how we wrapped the start and end of our original json to make it a template json file and edit it with your text editor, turning it from this: Original dashboard. For the sake of learning, we will use Kubernetes cluster monitoring (via Prometheus) to play with.ĭownload the dashboard. It can be a fresh one created from scratch or one you took from the Grafana Dashboards page.

#GRAFANA DASHBOARD UPGRADE#

Upgrade your helm release and watch the magic happen.

Modify the Grafana deployment to include the modified dashboard.

Prepare your dashboard for importing (or “template” it).

So, if we’re using Kube-Prometheus to deploy Grafana, and we want to automatically import a custom dashboard to it, how do we go about it? Kubectl create ns monitoringgit clone repo add coreos dependency buildcdchartstar-zxvf grafana-0.0.37.tgzrmgrafana-0.0.37.tgzcd././.helm install-name prometheus-operator -namespace monitoring helm/prometheus-operator/helm install-name kube-prometheus -namespace monitoring helm/kube-prometheus/ Problem Statement

#GRAFANA DASHBOARD INSTALL#

Run the below commands against your k8s cluster to install Prometheus operator on it:

Prometheus Operator & Kube-Prometheus deployed in your cluster (If this is your first time doing this, I highly suggest you read the documentation on github).

A running k8s cluster with version 1.9 and up with helm installed.

If you want to see it all in action, here’s what you need: Our Architecture will look like this: Kubernetis cluster What do you need in order to play along?

Kube-Prometheus is a deployment of Prometheus that is using the Prometheus Operator to provide a running Prometheus instance together with various exporters and Grafana.

Prometheus Operator allows you to deploy Prometheus on top of k8s, “in a kubernetes-native” way.

Helm is package manager for k8s allowing you to deploy applications to a k8s cluster (think of yum or apt for Linux).

#GRAFANA DASHBOARD SERIES#

Since each of these 3 can be developed into a blog post (or series of…) on its own, I won’t go into too many details about them. We decided to deploy Prometheus Operator and Kube-Prometheus using helm. We are working in a Kubernetes (k8s) environment, then we proceeded to choose a monitoring solution. It will visualize your collected metrics and present them in a graphical way (line charts, histograms, gauges, tables, etc.) As an open-source application, you can deploy it in many ways (you can read about some of the options here)

Grafana is an “open platform for beautiful analytics and monitoring”. While you have the option to manually import a dashboard once Grafana is up and running, we wanted to automate the process so we can keep Grafana as stateless as possible and ease the administration overhead when we upgrade or deploy it across different environments.īefore we dive into the “how-to”, I want to take a minute to describe the environment we’re going to work on, since it’s crucial to our automation process. Once deployed, we wanted to automate the process of importing various Grafana dashboards into the application. We are running a Kubernetes cluster, so we decided to deploy Prometheus & Grafana as our monitoring solution. In a recent project I did for one of my customers, we wanted to gain insight on our application.