Custom Prometheus

My Prometheus server is in a different location
If your Prometheus server is not in the default location for the selected Ingress controller, you need to create a Secret called prometheus-connection in the application Namespace.
Step 1
Create the application Namespace. You can do this with the create namespace command. For example:
1
kubectl create namespace my-application
Copied!
Step 2
Create the Secret. You can do this with the create secret generic command.
For example, if your Prometheus server is exposed by a Service named prometheus and is in a Namespace named monitoring:
1
kubectl create secret generic prometheus-connection \
2
  --namespace=my-application \
3
  --from-literal=url=http://prometheus.monitoring:9090
Copied!
My Prometheus server is running in a different cluster
The Vamp Release Agent makes real-time decisions about the validity of your microservices.
Using a Prometheus server in a different cluster introduces network latency. In extreme cases, these delays may cause the Release Agent to roll back a version because the required metrics are not available quickly enough.
Step 1
Create the application Namespace. You can do this with the create namespace command, for example:
1
kubectl create namespace my-application
Copied!
Step 2
Create the Secret. You can do this with the create secret generic command.
For example, if the URL of your Prometheus server is https://prometheus.example.com:
1
kubectl create secret generic prometheus-connection \
2
  --namespace=my-application \
3
  --from-literal=url=https://prometheus.example.com
Copied!
My Prometheus server requires a password
If your Prometheus server uses basic authentication, that is, it requires a username and password,  you can add them to the URL.
Step 1
Create the application Namespace. You can do this with the create namespace command. For example:
1
kubectl create namespace my-application
Copied!
Step 2
Create the Secret. You can do this with the create secret generic command.
For example, if the URL of your Prometheus server is https://prometheus.example.com:
1
kubectl create secret generic prometheus-connection \
2
  --namespace=my-application \
3
  --from-literal=url=https://username:[email protected]
Copied!
I have metrics in more than one Prometheus server
The Vamp Release Agent can only connect to one Prometheus server.

Troubleshooting Guide

NGINX

Last modified 3mo ago

Copy link

Contents

My Prometheus server is in a different location

My Prometheus server is running in a different cluster

My Prometheus server requires a password

I have metrics in more than one Prometheus server