You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.
Currently, the keptn configure monitoring prometheus CLI command creates scrape jobs only for services that are running on the same cluster as the Prometheus installation.
There is currently no way to define the HOST or ENDPOINT of the services I want to configure Prometheus for.
Currently, services are located via svc.cluster.local:
Desired features:
It should be possible to also use keptn configure monitoring prometheus for services that are not running on the same cluster as Prometheus.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, the
keptn configure monitoring prometheus
CLI command creates scrape jobs only for services that are running on the same cluster as the Prometheus installation.There is currently no way to define the HOST or ENDPOINT of the services I want to configure Prometheus for.
Currently, services are located via svc.cluster.local:
Desired features:
It should be possible to also use
keptn configure monitoring prometheus
for services that are not running on the same cluster as Prometheus.The text was updated successfully, but these errors were encountered: