Prometheus Exporter

100Days Resources

Learning Resources

Example Notes

Install Prometheus Helm Chart with Operators etc.

First off, we are going to follow the commands provided in the previous day — Day 28 — on Prometheus to have our Helm Chart with all the Prometheus related resources installed.

Day 28: What is Prometheus

Have a look at the Prometheus Resources to understand those better

Prometheus uses ServiceMonitors to discover endpoints. You can get a list of all the ServiceMonitors through:

kubectl get servicemonitor

Now have a look at one of those ServiceMonitors:

kubectl get servicemonitor prometheus-kube-prometheus-grafana -o yaml

This will display the ServiceMonitor definition in pure YAML inside our terminal. Look through the YAML file and you will find a label called:

"release: prometheus"

This label defines the ServiceMonitors that Prometheus is supposed to scrape.

Like mentioned in the Previous video, operators, such as the Prometheus Operator rely on CRD. Have a look at the CRDs that Prometheus uses through:

kubectl get crd

You can take a look at a specific one as follows.

kubectl get -o yalm

Set-up MongoDB

Now, we want to install a MongoDB image on our cluster and tell Prometheus to monitor it's endpoint. However, MongoDB is one of those images that relies on an exporter for its service to be visible to Prometheus. Think about it this way, Prometheus needs the help of and Exporter to know where MongoDB is in our cluster — like a pointer.

You can learn more about those concepts in my previous videos

  1. Prometheus on Kubernetes: Day 28 of #100DaysOfKubernetes
  2. Kubernetes Operators: Day 29 of #100DaysOfKubernetes

First off, we are going to install the MongoDB deployment and the MongoDB service; here is the YAML needed for this:


apiVersion: apps/v1
kind: Deployment
  name: mongodb-deployment
    app: mongodb
  replicas: 2
      app: mongodb
        app: mongodb
      - name: mongodb
        image: mongo
        - containerPort: 27017


apiVersion: v1
kind: Service
  name: mongodb-service
    app: mongodb
  - protocol: TCP
    port: 27017
    targetPort: 27017

Use the follow to apply both to your cluster

kubectl apply -f deployment.yaml
kubectl apply -f service.yaml

You can check that both are up and running through

kubectl get all 
# or

kubectl get service
kubectl get pods

Now we want to tell Prometheus to monitor that endpoint — for this, we are going to use the following Helm Chart

You can find a list of Prometheus exporters and integrations here:

Next, we are going to add the Helm Mongo DB exporter

helm repo add prometheus-community
helm show values rometheus-community/prometheus-mongodb-exporter > values.yaml

We need to mondify the values provided in the values.yaml file as follows:

  uri: "mongodb://mongodb-service:27017"

    release: prometheus

Basically, replace the values.yaml file created in the helm show command above with this file. In this case, we are going to tell the helm chart the mongodb endpoint and then the additional label for the ServiceMonitor.

Next, let's install the Helm Chart and pass in the values.yaml

helm install mongodb-exporter prometheus-community/prometheus-mongodb-exporter -f values.yaml

You can see whether the chart got installed correctly through

helm ls

Now have a look at the pods and the services again to see whether everything is running correctly:

kubectl get all 
# or

kubectl get service
kubectl get pods

Lastly make sure that we have the new ServiceMonitor in our list:

kubectl get servicemonitor

Have a look at the prometheus label within the ServiceMonitor

kubectl get servicemonitor mongodb-exporter-prometheus-mongodb-exporter -o yaml

Now access the service of the mongodb-exporter to see whether it scrapes the metrics of our MongoDB properly:

kubectl port-forward service/mongodb-exporter-prometheus-mongodb-exporter 9216

and open the Prometheus service:

kubectl port-forward service/prometheus-kube-prometheus-prometheus 9090

On localhost:9090, go to Status - Targets and you can see all of our endpoints that Prometheus currently knows about.