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

Additional kubelet_volume_stats_*_bytes metrics not forwarded #3500

Closed
acabrele opened this issue Jan 15, 2024 · 1 comment · Fixed by #3528
Closed

Additional kubelet_volume_stats_*_bytes metrics not forwarded #3500

acabrele opened this issue Jan 15, 2024 · 1 comment · Fixed by #3528
Labels
question Further information is requested

Comments

@acabrele
Copy link

acabrele commented Jan 15, 2024

Prior to v4 (prometheus based) we used to modify the regex in kube-prometheus-stack.kubelet.serviceMonitor.metricRelabelings and kube-prometheus-stack.prometheus.prometheusSpec.remoteWrite so that sumologic would receive kubelet_volume_stats_*_bytes metrics.

In v4 we can do the same by reverting to v3 config as documented here.

However it would be nice to get the same volume metrics working without having to do this. In the guidance here I believe this falls under category 1 which suggests that "You can safely delete the added remote write definition. No further action is required.". But we do not see the added metrics.

Category 2 suggests a filter processor may be needed, but I have had no luck in getting one to work.

I also note that the docs/scraped_metrics.m suggests a whole host of kubelet stats will be forwarded but there are actually only 4 available now.

What is the new trick to make this work?

@acabrele acabrele added the question Further information is requested label Jan 15, 2024
@acabrele acabrele reopened this Jan 17, 2024
@swiatekm-sumo
Copy link
Contributor

The source of this problem is that kubelet and cAdvisor metrics are no longer configured via a ServiceMonitor with otel. This ServiceMonitor only works with prometheus-operator present, and in its absence we use a custom scrape config, which until now was only customizable by overriding the otel configuration directly. #3528 will make that much more convenient.

You're right that this should be made explicit in the migration guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants