-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
We can add more debug level logs. Can you share your config? |
Sounds good to me, and a code owner has responded with approval as well. Removing |
Good with me |
@povilasv our config is a bit complex, here is the helm template for it: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/helm-charts/splunk-otel-collector/templates/config/_otel-k8s-cluster-receiver-config.tpl |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
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
The text was updated successfully, but these errors were encountered: