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
Is your feature request related to a problem? Please describe.
Metrics for certain pod/node status fields do not work well for filtering in backends. We'd like to introduce some of this information as metadata on pod and node entities.
Describe the solution you'd like
I'd like to add below additional attributes to the node and pod entity/metadata.
k8s.pod.phase - This is similar to the existing metric k8s.pod.phase. The values can be Pending, Running, Succeeded, Failed, Unknown.
k8s.pod.status_reason - Similar to k8s.pod.status_reason metric. A brief CamelCase message indicating details about why the pod is in this state. Example values - Evicted, NodeLost, UnexpectedAdmissionError
k8s.node.condition_{type} - similar to existing metrics enabled by the config node_conditions_to_report, e.g. k8s.node.condition_ready. Since additional custom node conditions can exist, I think sticking with the k8s native kubelet conditions would be better. Or we can use the node_conditions_to_report config here.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
receiver/k8scluster
Is your feature request related to a problem? Please describe.
Metrics for certain pod/node status fields do not work well for filtering in backends. We'd like to introduce some of this information as metadata on pod and node entities.
Describe the solution you'd like
I'd like to add below additional attributes to the node and pod entity/metadata.
k8s.pod.phase
- This is similar to the existing metrick8s.pod.phase
. The values can bePending
,Running
,Succeeded
,Failed
,Unknown
.k8s.pod.status_reason
- Similar tok8s.pod.status_reason
metric. A brief CamelCase message indicating details about why the pod is in this state. Example values -Evicted
,NodeLost
,UnexpectedAdmissionError
k8s.node.condition_{type}
- similar to existing metrics enabled by the confignode_conditions_to_report
, e.g.k8s.node.condition_ready
. Since additional custom node conditions can exist, I think sticking with the k8s native kubelet conditions would be better. Or we can use thenode_conditions_to_report
config here.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: