-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Eventing metrics #1792
Copy link
Copy link
Closed
Labels
kind/eventinglifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/hightriage/needs-eng-inputEngineering input is requestedEngineering input is requested
Milestone
Metadata
Metadata
Assignees
Labels
kind/eventinglifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/hightriage/needs-eng-inputEngineering input is requestedEngineering input is requested
What is changing? (Please include as many details as possible.)
The current eventing metrics have changed, and we need to properly document them in knative/docs.
We also need to add instructions on how to configure the different metrics backends.
How will this impact our users?
Users will be able to use metrics to better understand what is going on in their clusters.
In what release will this take happen (to the best of your knowledge)?
v0.9
Context
Link to associated PRs or issues from other repos here.