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.

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

[Telemetry Operator] Concept on how to enable kubelet logs as input #560

Open
Tracked by #13142
a-thaler opened this issue Jul 22, 2022 · 1 comment
Open
Tracked by #13142
Labels
area/logs LogPipeline kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@a-thaler
Copy link
Collaborator

a-thaler commented Jul 22, 2022

Description
With having a dedicated log gateway as part of this epic, a next natural step is to include k8s events as one input for logs. The otel-collector already ships a dedicated receiver for that: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/k8seventsreceiver

Goal: Build up understanding and try out the receiver to come up with a concrete action plan

Criterias

  • Understand the receiver and evaluate its maturity
  • Check if all relevant features are covered
  • Verify the attached resource attributes
  • Verify the actual log attributes and see if they match semantic conventions
  • Verify potential problems with scalability
@github-actions
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 21, 2022
@a-thaler a-thaler added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 21, 2022
@a-thaler a-thaler transferred this issue from kyma-project/kyma Nov 20, 2023
@a-thaler a-thaler added kind/feature Categorizes issue or PR as related to a new feature. area/logs LogPipeline and removed area/logging labels Nov 20, 2023
@a-thaler a-thaler mentioned this issue Feb 26, 2024
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logs LogPipeline kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

1 participant