-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[serving] OTel Metrics Documentation #6352
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
dprotaso
commented
Aug 28, 2025
- Updating collecting metrics steps
- remove collector installation steps and separate out shared metrics into a snippet
✅ Deploy Preview for knative ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2761f10 to
0690f72
Compare
|
/assign @Cali0707 @evankanderson Note for some of these docs to work now we need the dashboards PR to be merged - knative-extensions/monitoring#27 |
|
/cherry-pick release-1.19 |
|
@dprotaso: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
|
||
| **Instrument Type:** Int64Gauge | ||
|
|
||
| **Unit (UCUM):** {item} |
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.
What does UCUM stand for?
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.
Some unit standard that OTel uses
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.
{item} sorta means custom unit
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.
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 do wonder if our unit here should be {request}, since that's what the queue is full of.
Co-authored-by: Calum Murray <cmurray@redhat.com>
Cali0707
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cali0707, dprotaso The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@dprotaso: #6352 failed to apply on top of branch "release-1.19": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
evankanderson
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.
A few small comments, but this seems to fill in the gaps for the 1.19 release, thanks!
|
|
||
| **Instrument Type:** Int64Gauge | ||
|
|
||
| **Unit (UCUM):** {item} |
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.
|
|
||
| **Instrument Type:** Int64Gauge | ||
|
|
||
| **Unit (UCUM):** {item} |
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 do wonder if our unit here should be {request}, since that's what the queue is full of.
| ### `kn.revision.request.concurrency` | ||
|
|
||
| **Instrument Type:** Float64Gauge | ||
|
|
||
| **Unit (UCUM):** {request} | ||
|
|
||
| **Description:** Concurrent requests that are routed to the Activator | ||
|
|
||
| The following attributes are included with the metrics below | ||
|
|
||
| Name | Type | Description | ||
| -|-|- | ||
| `k8s.namespace.name` | string | Namespace of the Revision | ||
| `kn.service.name` | string | Knative Service name associated with this Revision | ||
| `kn.configuration.name` | string | Knative Configuration name associated with this Revision | ||
| `kn.revision.name` | string | The name of the Revision |
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 wasn't certain about this format vs the previous tabular format, but reviewing it on the site preview, it seems pretty reasonable. I sort of want a database of these, but I don't think I want to invest in that enough to make it happen.
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'm finding the navigation bar on the left and the sidebar on the right make it harder to read wide tables due to word wrapping.
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 don't think I want to invest in that enough to make it happen.
AI would make this work easier haha
|
|
||
| **Description:** Concurrent requests that are routed to the Activator | ||
|
|
||
| The following attributes are included with the metrics below |
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.
If this applies to all the autoscaler metrics, it feels like it should be after the ## Autoscaler header.
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.
It doesn't let me update
|
|
||
| **Instrument Type:** Int64Gauge | ||
|
|
||
| **Unit (UCUM):** {item} |
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.
Should this unit be {pod}?
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.
(and then document next to the other kn.revision.pods.* metrics)
|
|
||
| ```bash | ||
| kubectl port-forward -n default svc/prometheus-grafana 3000:80 | ||
| kubectl port-forward -n observability svc/knative-grafana 3000:80 |
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'm assuming the "load grafana dashboards" are currently an exercise for the user?
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.
It's in the serving/../collecting-metrics.md and It's in the eventing/../collecting-metrics.md
|
|
||
| Webhook metrics report useful info about operations. For example, if a large number of operations fail, this could indicate an issue with a user-created resource. | ||
|
|
||
| ### `http.server.request.duration` |
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.
Deliberate not to have ``Instrument Type:andUnit (UCUM):`?
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.
Since this is an OTel metric I link out to it which includes the details.