[DOCS-14571] Update Metrics on Config doc#37620
Conversation
Preview links (active after the
|
Co-authored-by: ArunPiduguDD <arun.pidugu@datadoghq.com>
| The `counter` metric type is the only `incremental` metric. `gauge`, `distribution`, and `histogram` metric types are `absolute` metrics. | ||
| Whether a received metric is `incremental` or `absolute` depends on the source. For example, metrics from [OpenTelemetry][4] can either be incremental or absolute based on their temporality. The following table is an example of an OTel counter metric sent with delta versus cumulative temporality. | ||
|
|
||
| | Metric Type | Incremental | Absolute | |
There was a problem hiding this comment.
| | Metric Type | Incremental | Absolute | | |
| | Metric Type | Delta | Cumulative | |
Also wondering if these should use the same terminology as above?
There was a problem hiding this comment.
Actually, they are different things. Metric kinds are incremental or absolute and for OTel that is determined by temporality (deltas or cumulative sum).
There was a problem hiding this comment.
Oh, gotcha, thanks for clarifying! I wonder if users will make the same mistake; might be worth clarifying if you think they might?
There was a problem hiding this comment.
We do mention:
OpenTelemetry can either be incremental or absolute based on their [temporality][4].
There was a problem hiding this comment.
Yeah, that's true, I think I'm just not familiar with the product area so I got confused 😅 If you think readers will get it then let's leave it!
Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
* update metrics config * Apply suggestion from @ArunPiduguDD Co-authored-by: ArunPiduguDD <arun.pidugu@datadoghq.com> * fix columns * fix link * Apply suggestion from @janine-c Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com> --------- Co-authored-by: ArunPiduguDD <arun.pidugu@datadoghq.com> Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>
What does this PR do? What is the motivation?
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes