-
Notifications
You must be signed in to change notification settings - Fork 710
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
Performancecounter: panic: reflect.StructOf: field 0 has invalid name #1821
Comments
thanks, Seems like I did not sanitize brackets. The fix in available here: https://github.com/prometheus-community/windows_exporter/actions/runs/12454122957/artifacts/2353309323 and in the next release. |
@jkroepke still panics - same config as before:
I get the panic with and this: what is the correct syntax? |
It seems like I deliver the wrong link to you. I guess I had a old tab open. Sorry for that. Here is the correct one: https://github.com/prometheus-community/windows_exporter/actions/runs/12520747861/artifacts/2366802477 the file name is I also provide a documentation how to access the builds by your own. https://github.com/prometheus-community/windows_exporter/wiki/Snapshot-Builds
Both variants are fine. The pipe is mandatory. The hypen declare that a pending newline is trimmed. https://yaml-multiline.info/ describe it well. YAML hass approx 63 different variation how multi line values can be declared. |
Current Behavior
Command:
C:\Users\Alexander\Desktop\windows_exporter-0.30.0-rc.4-amd64.exe --config.file=C:\Users\Alexander\Desktop\windows_exporter.yml --log.file=C:\Users\Alexander\Desktop\windows_exporter.log
config:
I tried with
Panic
objects: |-
Panic
objects: |
Running but not perfcounter results.
objects:
Discrepancy in readme:
https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.performancecounter.md
top of readme ( |- vs | )
bottom of readme
Error:
Expected Behavior
metrics, no panic,
Steps To Reproduce
Environment
10
windows_exporter logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: