-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat(kubernetes): Add kubernetes input plugin #1847
Conversation
2375690
to
75bedbf
Compare
75bedbf
to
8caed26
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jchauncey thanks for the PR!
A couple requests:
- example yaml file for configuring telegraf to run as daemon set
- example output / line protocol
"namespace": pod.PodRef.Namespace, | ||
"name": container.Name, | ||
"pod": pod.PodRef.Name, | ||
"uid": pod.PodRef.UID, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this and the other uid
tags have very high or unlimited cardinality?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. everytime a pod dies and comes back it would have a new uuid. Same thing with pod name
bfa0203
to
1b1bf56
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
"namespace": pod.PodRef.Namespace, | ||
"name": container.Name, | ||
"pod": pod.PodRef.Name, | ||
"uid": pod.PodRef.UID, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. everytime a pod dies and comes back it would have a new uuid. Same thing with pod name
1b1bf56
to
0c30800
Compare
@jchauncey I'm concerned this plugin will generate stats with very high cardinality, it appears that you are storing a UUID as a tag for every:
In a typical kubernetes setup, how frequently would you expect new UUIDs of each of these to get generated? how frequently in a high-volume kubernetes setup? |
It largely depends. We could remove the uuid but we will still have high cardinality with the pod name because it has a unique identifier which changes every time the pod dies. Im guess over a month there may be a few hundred pod uuids created on a moderately sized cluster. |
I can tell you we churn around 3-5k pods a day. I would like to see options to limit the amount of churn for specific pods. |
What I could do is have a flag that allows you to exclude pod name from the On Oct 14, 2016 6:19 PM, "Shane Starcher" notifications@github.com wrote:
|
@jchauncey AFAICT simply excluding the pod name & uuid will only lead to duplicate metrics overwriting each other. If flags are added they will need to completely disable to per-pod and per-container metrics from being gathered. Does kubernetes not provide any sort of aggregated metrics? From what I can see in this PR the metrics are all very high cardinality. |
No that's the point of this plugin is to get detailed pod metrics. On Oct 14, 2016 6:58 PM, "Cameron Sparr" notifications@github.com wrote:
|
0c30800
to
be9a046
Compare
be9a046
to
79dfca7
Compare
79dfca7
to
a12bd87
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 lgtm - @jchauncey thank you for contributing this plugin and all the quick code review updates!
Yeay!! This is a great plugin!!! 👍 |
Required for all PRs:
closes #1774