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

[receiver/k8scluster] Add more debug logging to the receiver #32236

Closed
atoulme opened this issue Apr 9, 2024 · 8 comments
Closed

[receiver/k8scluster] Add more debug logging to the receiver #32236

atoulme opened this issue Apr 9, 2024 · 8 comments

Comments

@atoulme
Copy link
Contributor

atoulme commented Apr 9, 2024

Component(s)

receiver/k8scluster

Is your feature request related to a problem? Please describe.

Right now, there’s no information about the behavior of the receiver explicitly logged. We didn't see anything additionally logged at the debug level when trying to debug a situation where we didn't know if the cluster receiver would send metadata updates.

Describe the solution you'd like

Add more debug logs to the k8sclusterreceiver to make sure we can see when it starts to send dimension updates, or when it doesn’t have any to sync, such as no exporter is detected.

Describe alternatives you've considered

No response

Additional context

No response

@atoulme atoulme added enhancement New feature or request needs triage New item requiring triage labels Apr 9, 2024
Copy link
Contributor

github-actions bot commented Apr 9, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@povilasv
Copy link
Contributor

povilasv commented Apr 9, 2024

We can add more debug level logs. Can you share your config?

@crobert-1
Copy link
Member

Sounds good to me, and a code owner has responded with approval as well. Removing needs triage.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label Apr 9, 2024
@TylerHelmuth
Copy link
Member

Good with me

@atoulme
Copy link
Contributor Author

atoulme commented Apr 11, 2024

Copy link
Contributor

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jun 11, 2024
@crobert-1 crobert-1 removed the Stale label Jun 11, 2024
Copy link
Contributor

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Aug 12, 2024
Copy link
Contributor

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 Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants