[processor/k8sattributes] introduce new observability metric otelcol.k8s.pod.association#44718
Conversation
a96f868 to
1fc115d
Compare
1fc115d to
b8c5481
Compare
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
I would be fine with adding the new metric following the suggested dots approach. However I think we should not close #44587 until we fixed the components' internal metrics according to open-telemetry/opentelemetry-collector#12909. WDYT? |
|
We briefly discussed this specific case during the Collector Stability SIG. We can wait to have open-telemetry/opentelemetry-collector#14273 merged and then we can try to migrate the internal metrics from |
|
open-telemetry/opentelemetry-collector/pull/14273 is on the merge queue :) |
ChrsMark
left a comment
There was a problem hiding this comment.
The addition LGTM (needs rebase).
But let's also ensure we do the rename (_ to using .) as part of the related issue: #44718 (comment)
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
Signed-off-by: odubajDT <ondrej.dubaj@dynatrace.com>
d9ed007 to
794725b
Compare
|
I'm going to merge this and we can follow-up as long as the parent issue is still open. |
Description
Introduction of new observability metric:
otelcol.k8s.pod.associationwith
status,otelcol.signalandpod_identifierattributesLink to tracking issue
Related to #44587