Closed ebini closed 1 year ago
Metrics are in port 9090, are you checking this port? I cannot reproduce the error.
Is there a way to revert to the old behavior? The helm chart does not have a port for metrics and I'm running with Rancher's fork of prom2teams included in rancher-alerting-drivers so even if resolved here, it will take long time to get pulled into their repo. I already had to manually add the ServiceMonitor resource and switch to using their dev branch.
https://github.com/idealista/prom2teams/blob/340d47d30d4263d7a5608206c5e884553c2dc0e2/prom2teams/app/configuration.py#L133 I think setting the ENV config parameter would revert the old behavior, but I'm not sure how to achieve that.
I rolled back to version 4.0.0
for now
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description
setting the Environment Variable PROM2TEAMS_PROMETHEUS_METRICS=true (like in the README.md is not working (anymore)
Steps to Reproduce
set PROM2TEAMS_PROMETHEUS_METRICS=true connecting to /metrics returns still 404
Expected behavior: metrics data
Actual behavior: 404
Reproduces how often: always
Environment
deployed in k8s cluster verified setting by "shelling" into the container
Additional Information
worked in older versions (but this was long time ago)