Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

WIP: Pipeline monitoring metrics #249

Closed
wants to merge 21 commits into from
Prev Previous commit
Next Next commit
wip2
  • Loading branch information
jmacd committed Dec 20, 2023
commit 3ce051090e2b3b0500c85d98e841e79dd7f7d7fe
5 changes: 2 additions & 3 deletions text/metrics/0238-pipeline-monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -209,14 +209,13 @@ of these timeseries. The specified counter names:
way than `otel.success`, with recommended values specified below.
- `otel.signal` (string): This is the name of the signal (e.g., "logs",
"metrics", "traces")
- `otel.name` (string): Name of the component
- `otel.pipeline` (string):
- `otel.name` (string): Name of the component in a pipeline.
- `otel.pipeline` (string): Name of the pipeline in a collector.

#### Collector

TODO: Why we count only drops for pipeline segments, but not SDKs.


## Metrics SDK special considerations

We expect that Metrics SDKs will be used to generate
Expand Down