-
Notifications
You must be signed in to change notification settings - Fork 207
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
Report kubernetes system metadata #741
Conversation
@bmorelli25, I don't sure do we need to add it into documentation? I found nothing in other agents related to it. |
We document Kubernetes metadata centrally, in APM Server: https://www.elastic.co/guide/en/apm/server/master/metadata-api.html. I don't think anything is needed in this PR 👍 |
@gregkalapos, I'll very much appreciate it if you can review the PR. |
Hey @vhatsura - sorry for the delay, currently we are fighting with some CI issues; hopefully we can get back to normal soon. Once master is green again I'll make sure PRs gets reviewed and merged. |
@gregkalapos, just a kindly reminder. Would be nice to have such feature in the next release |
Bump |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
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.
Thanks @vhatsura - looks good to me.
Some of these can be also collected by parsing /proc/self/cgroup
- this is a super useful comment on that. Here is some more info on that.
The Go PR has some sample /proc/self/cgroup
that we could also steal for testing.
This is already good progress and I think it's ok to merge - if you feel you can follow up with parsing /proc/self/cgroup
later.
|
||
return new Api.System | ||
{ | ||
Container = containerInfo, DetectedHostName = hostName, Kubernetes = ParseKubernetesInfo(containerInfo, hostName) |
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.
I'd have either called all 3 methods here directly or also stored the result of ParseKubernetesInfo(containerInfo, hostName)
in a variable and assigned that to Kubernetes
similar to the two other properties.
But that's just a cosmetic thing - this is totally fine this way too.
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.
Yeap, it makes sense. Fixed
closes #181
TBD: