-
Notifications
You must be signed in to change notification settings - Fork 672
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
Connector os cs and service are timing out #1413
Comments
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
The services collector is really slow, maybe we have an solution for it: #1497 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have multiple Windows instances in our company, but some of them are behaving weirdly. For a while, we haven't received any more metrics for some specific collector, more specifically, os, cs, and service.
Looking at the logs, it seems that they are timing out. I tried to increase the timeout with
--scrape.timeout-margin=-20
, but it didn't change. Here is an example of the outputI tried then to upgrade to the latest version of Windows Exporter,but the issue seems to be remaining, even though the only collector that is still failing is the service
The text was updated successfully, but these errors were encountered: