-
Notifications
You must be signed in to change notification settings - Fork 152
Add prometheus to playground #3752
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
Conversation
| ports: | ||
| - 8080:80 | ||
| - 8080:80 # API | ||
| - 9586:9586 # metrics |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the port need to be exposed? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the orderbook and autopilot expose the metrics on a separate port. In the driver and baseline solver we use the one port that also handles the regular API requests. 😅
jmg-duarte
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
Description
Currently the playground's
grafanacontainer is only there to supporttempobut you can't actually test any new metrics or queries with it. This PR makes it so thatgrafanaactually gets access to all the metrics.Changes
metricsports on containers where it's necessaryprometheuscontainer that scrapes all the services podsprometheusas the default data source ingrafanaHow to test
I manually checked that
grafanagets access to metrics from all the different pods and I built a new dashboard with it.As a follow up we could consider somehow replicating our actual dashboards but that goes beyond the scope of the PR (and probably isn't that helpful anyway because the metrics reported by a locally running instance are very far from what our actual deployments would look like).