Skip to content

Conversation

@dprotaso
Copy link
Member

  • Updating collecting metrics steps
  • remove collector installation steps and separate out shared metrics into a snippet

@knative-prow knative-prow bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 28, 2025
@knative-prow knative-prow bot requested review from creydr and skonto August 28, 2025 17:01
@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 28, 2025
@netlify
Copy link

netlify bot commented Aug 28, 2025

Deploy Preview for knative ready!

Name Link
🔨 Latest commit dce1aea
🔍 Latest deploy log https://app.netlify.com/projects/knative/deploys/68b85ec1bc5155000856b4f8
😎 Deploy Preview https://deploy-preview-6352--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dprotaso dprotaso force-pushed the otel-metrics branch 8 times, most recently from 2761f10 to 0690f72 Compare August 28, 2025 18:50
@dprotaso dprotaso changed the title [wip] OTel Metrics Documentation OTel Metrics Documentation Sep 1, 2025
@knative-prow knative-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 1, 2025
@dprotaso dprotaso changed the title OTel Metrics Documentation [serving] OTel Metrics Documentation Sep 1, 2025
@dprotaso
Copy link
Member Author

dprotaso commented Sep 1, 2025

/assign @Cali0707 @evankanderson

Note for some of these docs to work now we need the dashboards PR to be merged - knative-extensions/monitoring#27

@dprotaso
Copy link
Member Author

dprotaso commented Sep 1, 2025

/cherry-pick release-1.19

@knative-prow-robot
Copy link
Contributor

@dprotaso: once the present PR merges, I will cherry-pick it on top of release-1.19 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.19

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}
Copy link
Member

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?

Copy link
Member Author

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

Copy link
Member Author

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

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>
Copy link
Member

@Cali0707 Cali0707 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2025
@knative-prow
Copy link

knative-prow bot commented Sep 3, 2025

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot merged commit b936c72 into knative:main Sep 3, 2025
19 checks passed
@knative-prow-robot
Copy link
Contributor

@dprotaso: #6352 failed to apply on top of branch "release-1.19":

Applying: Updating collecting metrics steps
.git/rebase-apply/patch:126: trailing whitespace.
    By default metrics are exporting is off. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	docs/eventing/observability/metrics/collecting-metrics.md
M	docs/serving/observability/metrics/collecting-metrics.md
Falling back to patching base and 3-way merge...
Auto-merging docs/serving/observability/metrics/collecting-metrics.md
Auto-merging docs/eventing/observability/metrics/collecting-metrics.md
Applying: remove collector installation steps and separate out shared metrics into a snippet
.git/rebase-apply/patch:477: trailing whitespace.
Knative implements the [semantic conventions for Go runtime metrics](https://opentelemetry.io/docs/specs/semconv/runtime/go-metrics/) using the OpenTelemetry [otel-go/instrumentation/runtime](https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation/runtime) package. 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	docs/eventing/observability/metrics/eventing-metrics.md
M	docs/serving/observability/metrics/serving-metrics.md
Falling back to patching base and 3-way merge...
Removing docs/serving/observability/metrics/system-diagram.svg
Auto-merging docs/serving/observability/metrics/serving-metrics.md
CONFLICT (content): Merge conflict in docs/serving/observability/metrics/serving-metrics.md
Removing docs/serving/observability/metrics/collector.yaml
Removing docs/eventing/observability/metrics/system-diagram.svg
Auto-merging docs/eventing/observability/metrics/eventing-metrics.md
CONFLICT (content): Merge conflict in docs/eventing/observability/metrics/eventing-metrics.md
Removing docs/eventing/observability/metrics/collector.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 remove collector installation steps and separate out shared metrics into a snippet

Details

In response to this:

/cherry-pick release-1.19

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.

Copy link
Member

@evankanderson evankanderson left a 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}
Copy link
Member

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}
Copy link
Member

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.

Comment on lines +42 to +57
### `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
Copy link
Member

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.

Copy link
Member Author

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.

Copy link
Member Author

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
Copy link
Member

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.

Copy link
Member Author

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}
Copy link
Member

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}?

Copy link
Member

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
Copy link
Member

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?

Copy link
Member Author

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`
Copy link
Member

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):`?

Copy link
Member Author

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.

@dprotaso dprotaso deleted the otel-metrics branch September 3, 2025 20:25
dprotaso added a commit to dprotaso/knative-docs that referenced this pull request Sep 3, 2025
knative-prow bot pushed a commit that referenced this pull request Sep 3, 2025
* Cherry-pick (#6352)

* OTel docs follow up (#6360)

* include UCUM link

* address Evan's OTel Docs feedback

* include autoscaler attributes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants