-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
osrm-routed monitoring in the prometheus format #6147
Conversation
Please take a look at the changes in CHANGELOG - it looks weird |
@hoerup my formatter is configured to format on save, undone the change |
@mjbell could you take a look ? |
I've looked over this briefly.
If we want to go down the route of having built-in observability, it's probably also worth discussing the options for a more robust server alternative for |
@mjjbell can you suggest any alternatives to export osrm metrics externally. Are we planning to add built-in observability in a future release version with the suggested improvements ? |
I don't think anyone is planning anything for future releases at this point 🙂 , it's up to the community. I agree that native observability would be beneficial, but I have reservations specifically about this PR's structure and about investing a lot of time in Depending on your exact needs, you might get some immediate benefit from running a proxy like Envoy or Nginx in front of |
closing stale PR. Reopen if still relevant. |
#5180
Endpoint to check OSRM status with monitoring solutions based on prometheus format.
This is a proof of concept implementation that has only several simple options. Additional metrics can be added with ongoing PRs.
Metrics endpoint is a separate thread that listens its own port and doesn't bother worker threads.
#5509 Fixing conflicts