/metrics server not working

[mogoman]

#71 # Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

-m or --enablemetrics or PROM2TEAMS_PROMETHEUS_METRICS=true all appear to have no effect

Steps to Reproduce

v2.5.7
1.

docker run -it -d --rm --name prom2teams -e PROM2TEAMS_LOGLEVEL=DEBUG -e PROM2TEAMS_GROUP_ALERTS_BY="summary" -e PROM2TEAMS_CONNECTOR="https://foo.bar" -e PROM2TEAMS_PROMETHEUS_METRICS=true -p 8089:8089 idealista/prom2teams:2.5.7

curl localhost:8089/metrics

<title>404 Not Found</title>

same for 2.5.6, 2.5.5 and 2.4.0

Expected behavior: [What you expect to happen]

curl to /metrics should produce some data and not 404

Actual behavior: [What actually happens]

receive 404

Reproduces how often: [What percentage of the time does it reproduce?]

100%

Versions

2.5.7, 2.5.6, 2.5.5, 2.4.0 were tested

Additional Information

none

[rdoering]

This a problem for me, too.

@mogoman Dit you found a working version?

[mogoman]

No solution yet. Looking at the code it should work, I'll try and track down the problem.

[rdoering]

I tried to debug the problem, too. But it is very bad to use pdb with just little knowledge of python.

[vicsufer]

Hey there @rdoering @mogoman, can you try setting the environment variable DEBUG_METRICS=true ?

It seems to be a problem with an imported library when running flask on debug mode. However this seems to happen in prom2teams even in production mode, I'll have a look into this, but this workaround should work for now.

In your example it should be something like this:

docker run -it -d --rm --name prom2teams -e PROM2TEAMS_LOGLEVEL=DEBUG -e PROM2TEAMS_GROUP_ALERTS_BY="summary" -e PROM2TEAMS_CONNECTOR="https://foo.bar" -e PROM2TEAMS_PROMETHEUS_METRICS=true -e DEBUG_METRICS=true -p 8089:8089 idealista/prom2teams:2.5.7

[rdoering]

@vicfran Thanks for your workaround, it is working with the env DEBUG_METRICS=true.