Example of the module configuration

apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
  name: prometheus-pushgateway
  version: 1
  enabled: true
    - first
    - second
    - another

PushGateway address (from a container pod): http://first.kube-prometheus-pushgateway:9091.

Pushing a metric

An example of pushing a metric using curl:

echo "test_metric{env="dev"} 3.14" | curl --data-binary @- http://first.kube-prometheus-pushgateway:9091/metrics/job/myapp

The metrics will be available in Prometheus in 30 seconds (after the data are scraped). An example:

test_metric{container="prometheus-pushgateway", env="dev", exported_job="myapp", 
    instance="", job="prometheus-pushgateway", pushgateway="prometheus-pushgateway", tier="cluster"} 3.14

The job name (myapp in the example) will be available in Prometheus in the label exported_job, and not job (because the label job already exists in Prometheus and is renamed when receiving metrics from PushGateway).

You may need to get a list of all available job names to choose a unique name (in order not to spoil existing graphs and alerts). Use the following query to get a list of all existing jobs: count({__name__=~".+"}) by (job).

Deleting metrics

An example of deleting all metrics of a group {instance="",job="myapp"} using curl:

curl -X DELETE http://first.kube-prometheus-pushgateway:9091/metrics/job/myapp/instance/

Since PushGateway stores the scraped metrics in memory, all metrics will be lost when the Pod is restarted.