Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Revisit association of workloads and pods in k8s_cluster receiver #190

Closed
asuresh4 opened this issue Apr 24, 2020 · 2 comments
Closed

Revisit association of workloads and pods in k8s_cluster receiver #190

asuresh4 opened this issue Apr 24, 2020 · 2 comments
Labels
closed as inactive comp: receiver Receiver Stale
Milestone
Backlog

Comments

@asuresh4
Copy link
Member

Relates to #175

The k8s_receiver currently associates Pods with its workloads using k8s.workload.name and k8s.workload.kind. For example, if a Pod is spawned by a CronJob called foo, the created Pod will have labels like k8s.workload.kind:cronjob and k8s.workload.name:foo. This applies to workloads of other types as well.

The above mechanism of association should be revisited after we finalize on the new conventions for naming Kubernetes metadata.
@tigrannajaryan tigrannajaryan added this to the Backlog milestone Jul 30, 2020
@alolita alolita added the comp: receiver Receiver label Sep 30, 2021
ljmsc referenced this issue in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
@iredelmeier @rghetia
Propagate FollowsFrom span relationships in SDK (#190)
849cdc7 
[Closes #189]
@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2022

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 7, 2022
codeboten pushed a commit that referenced this issue Nov 23, 2022
@lzchen
Merge pull request #190 from lzchen/req
4b9422e
@github-actions
Copy link
Contributor

github-actions bot commented Mar 9, 2023

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 9, 2023
straussb pushed a commit to straussb/opentelemetry-collector-contrib that referenced this issue Apr 5, 2024
@sethAmazon
Add JMX Registry SSL Enabled Config (open-telemetry#190)
65efa22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed as inactive comp: receiver Receiver Stale
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@alolita @tigrannajaryan @asuresh4