-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What port? #63
Comments
I get this error when I hit the /metrics route.
|
This is due to |
What is the status of the breaking changes? Does prom-client now work with your package? |
My PR was merged and the package owner released version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am sorry if this is a dumb question, it feels like it. The documentation doesn't say if the metrics are exposed on a different port than the one the app.listen specifies. I have tried to curl that http://127.0.0.1:8080/metrics refuses to connect. I am assuming that once included in my application I can't use the metrics route for my own stuff as it is reserved (unless I change it via the options). So my assumptions are same ip/port as specified in the app.listen directive, just takes over the /metrics route. Just want to make sure this is correct..so I can trouble shoot further.
thanks
The text was updated successfully, but these errors were encountered: