-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
(WIP) Improve logging and OpenMetrics docs #21089
base: master
Are you sure you want to change the base?
Conversation
5d58530
to
3f80d5e
Compare
The slack channel recently swiftly educated me that for some metrics I need pull metrics from all nodes including workers and not just the coordinator, Prometheus supports k8s service discovery as standard and most implementations have a standard "prometheus-anotations" job configured, however in general that's unauthenticated. I created two copies of that, one for the coordinator and one for the workers because in my case:
@mattstep requested I share some Prometheus configuration required to sour Firstly in the helm for trino add the annotations
Then in the prometheus config
|
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua |
This looks good to me, and I think would benefit from the more complex example from @lozbrown , this gives a more realistic configuration for a production usecase. |
I have a whole bunch of further info and details from @lozbrown and others that I will add .. just have to get back to working on this. |
I think it would be good to include a list of the things you typically monitor in your dashboard as experts. Possibly including promql for these |
@mosabua can we move along some sort of first attempt here on the basis something is better than completely undocumented features |
Its on my backlog but I am flat out busy .. I will try to get a minimal PR merged first and expand later at this stage. |
Trino also includes a [](/connector/prometheus) that allows you to query | ||
Prometheus data using SQL. | ||
|
||
## Example use |
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.
i really think that running Prometheus server is out of scope for Trino Documentation
|
||
```shell | ||
curl -H X-Trino-User:foo localhost:8080/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.
Because this works for any cluster the localhost should not be necessary (most users will never run trino on their PC)
it's necessary to point out users need system-information read permission
Its necessary to point out for complete metrics all workers will need to be scraped.
Description
Additional context and related issues
Related to TCB 57
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.