New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More metrics from Kubernetes State API #3045
Labels
Comments
+1 |
therc
pushed a commit
to therc/dd-agent
that referenced
this issue
Dec 9, 2016
Fixes part of DataDog#3045 * Add mem/cpu requests and limits * Add container restarts * Add pod phase: Pending|Running|Succeeded|Failed|Unknown Tests might fail because the prometheus protobuf.bin blob lacks the resource limits added in kubernetes/kube-state-metrics#49
therc
pushed a commit
to therc/dd-agent
that referenced
this issue
Dec 21, 2016
Fixes part of DataDog#3045 * Add container mem/cpu requests (not limits, they'll be in state-metrics 0.4) * Add container restarts * Add pod phase check: Pending|Running|Succeeded|Failed|Unknown Metrics that are not supported yet or not covered by the test protobuf.bin are commented out.
Is the plan to keep this as the meta issue for improvements? |
I think #3305 dupes this. |
this should be fixed now, we're also working on supporting kube-state-metrics v0.5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5.10 introduced new metrics from the kubernetes-state-metrics API.
There are still some in the API that haven't made it to DataDog, e.g.:
kube_pod_container_status_ready{container="dd-agent",namespace="kube-system",pod="dd-agent-0fv0y"} 1
kube_pod_container_status_restarts{container="dd-agent",namespace="kube-system",pod="dd-agent-0fv0y"} 0
kube_pod_container_status_running{container="dd-agent",namespace="kube-system",pod="dd-agent-0fv0y"} 1
kube_pod_container_status_terminated{container="dd-agent",namespace="kube-system",pod="dd-agent-0fv0y"} 0
kube_pod_container_status_waiting{container="dd-agent",namespace="kube-system",pod="dd-agent-0fv0y"} 0
kube_pod_container_requested_cpu_cores{container="kubedns",namespace="kube-system",node="10.X.Y.Z",pod="kube-dns-v20-juul3"} 0.1
kube_pod_container_requested_memory_bytes{container="kubedns",namespace="kube-system",node="ip-10.X.Y.Z",pod="kube-dns-v20-juul3"} 1.048576e+08
At least the restarts and the requested resources (as opposed to limits) are very interesting to us.
I guess one question is how to map the pod and container names into DataDog: separate tags or combined into one?
The text was updated successfully, but these errors were encountered: