-
Notifications
You must be signed in to change notification settings - Fork 814
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
[kubernetes] add replicaset pods to kubernetes.pods.running metric #2444
Milestone
Comments
crunchie84
changed the title
[kubernetes] add kubernetes.pods.running metric
[kubernetes] add replicaset pods to kubernetes.pods.running metric
Apr 26, 2016
I have created a PR for the proposed change. |
remh
pushed a commit
that referenced
this issue
May 17, 2016
remh
pushed a commit
that referenced
this issue
May 17, 2016
remh
pushed a commit
that referenced
this issue
May 17, 2016
- Enable kubelet check by default - Remove master check for now as they are flaky, hard to enable and not used - Adapt to new format of labels set by kube1.2 fix #2388 #2494 - Allow to blacklist labels - Support replica sets fix #2444 #2446 - Handle case where no pods are running. Fix #2263 - Add tests for kube 1.2
remh
pushed a commit
that referenced
this issue
May 17, 2016
- Enable kubelet check by default - Remove master check for now as they are flaky, hard to enable and not used - Adapt to new format of labels set by kube1.2 fix #2388 #2494 - Allow to blacklist labels - Support replica sets fix #2444 #2446 - Handle case where no pods are running. Fix #2263 - Add tests for kube 1.2
remh
pushed a commit
that referenced
this issue
May 17, 2016
- Enable kubelet check by default - Remove master check for now as they are flaky, hard to enable and not used - Adapt to new format of labels set by kube1.2 fix #2388 #2494 - Allow to blacklist labels - Support replica sets fix #2444 #2446 - Handle case where no pods are running. Fix #2263 - Add tests for kube 1.2
remh
pushed a commit
that referenced
this issue
May 18, 2016
- Enable kubelet check by default - Remove master check for now as they are flaky, hard to enable and not used - Adapt to new format of labels set by kube1.2 fix #2388 #2494 - Allow to blacklist labels - Support replica sets fix #2444 #2446 - Handle case where no pods are running. Fix #2263 - Add tests for kube 1.2
Is this included in current Datadog? Using |
I don't see this, either. Running the latest :kubernetes image. Ideally, the agent should talk to the API server and figure the desired number of replicas for a ReplicaSet or Deployment, so that you can alert if they aren't 100% running for e.g. over 5 minutes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In PR #2277 @masci created the basics for the pod counts based on ReplicaControllers 🏆 . Since the release of Kubernetes (k8s) 1.2 this is no longer enough. The developers introduced
Deployments
in k8s 1.2 which work in combination withReplicaSets
instead ofReplicaControllers
thus having pods be annotated as created-byReplicaSet
.Proposed change
The pods are grouped by creator name in
/checks.d/kubernetes.py
. Proposed change is to have this grouping also include pods grouped by ReplicaSet. As far as i can see the naming of ReplicationControllers/ReplicaSets is unique so no overlap should be possible.Example annotation output with new ReplicaSets:
This ticket has been created while using Kubernetes version 1.2.2
The text was updated successfully, but these errors were encountered: