You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the SignalFx/Splunk OpenTelemetry (OTel) Collector and I am unable to see the metric k8s.pod.status_reason.
I have installed the splunk-otel-collector-agent and integrated it with my Splunk instance. I can see all other metrics such as k8s.pod.phase, k8s.pod.cpu.utilization, etc., but k8s.pod.status_reason is missing.
Steps to Reproduce
Install the splunk-otel-collector-agent.
Integrate the collector with Splunk.
Monitor Kubernetes pod metrics.
Expected Result
The metric k8s.pod.status_reason should be visible along with other Kubernetes pod metrics.
Actual Result
The metric k8s.pod.status_reason is not visible, while other metrics like k8s.pod.phase and k8s.pod.cpu.utilization are visible.
Collector version
0.111.0
Environment information
Environment
OS: Azure Linux
Kubernetes: AKS (Azure Kubernetes Service) 1.28
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
exporter/signalfx
What happened?
Description
I am using the SignalFx/Splunk OpenTelemetry (OTel) Collector and I am unable to see the metric
k8s.pod.status_reason
.I have installed the
splunk-otel-collector-agent
and integrated it with my Splunk instance. I can see all other metrics such ask8s.pod.phase
,k8s.pod.cpu.utilization
, etc., butk8s.pod.status_reason
is missing.Steps to Reproduce
splunk-otel-collector-agent
.Expected Result
The metric
k8s.pod.status_reason
should be visible along with other Kubernetes pod metrics.Actual Result
The metric
k8s.pod.status_reason
is not visible, while other metrics likek8s.pod.phase
andk8s.pod.cpu.utilization
are visible.Collector version
0.111.0
Environment information
Environment
OS: Azure Linux
Kubernetes: AKS (Azure Kubernetes Service) 1.28
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: