Switch to upstream windows_exporter

[jkroepke]

PR Description

This PR removes the outdated internal grafana/windows_exporter fork.

This PR is still in draft, since various upstream PR needs to be solved first. This PR based on personal forks of windows_exporter which are planned to be merged upstreamed. After that, the PR is ready to review.

I'm creating the PR right now to indicate that some is working on the windows_exporter.

It introduce a breaking change from prometheus-community/windows_exporter#1170 (not sure how to handle this). If Grafana Agent follows SemVer, the breaking change is fine.

Test on a windows 10 system with following config:

prometheus.exporter.windows "exporter1" {
  // Subset of overall collectors  
  enabled_collectors = "cpu,cs,logical_disk"
}

prometheus.exporter.windows "exporter2" {
  // Different subset of overall collectors  
  enabled_collectors = "net,os,service,system"
}

prometheus.scrape "example" {
  targets = concat(
    prometheus.exporter.windows.exporter1.targets,
    prometheus.exporter.windows.exporter2.targets,
  )

  forward_to = [...]
}

Prometheus UI:

Which issue(s) this PR fixes

• Fixes Update windows_exporter with latest #1631
• Fixes Update github.com/prometheus-community/windows_exporter to v0.22.0 #3364
• Fixes Get changes of windows_exporter merged upstream and remove replace in go.mod #3420
• Relates windows_exporter MSSQL collector panic #3122 (not sure, if the issues exists upstreams)

Notes to the Reviewer

PR Checklist

• CHANGELOG updated
• Documentation added
• Tests updated

[mattdurham]

Reviewing this and going to run it on my local VM to smoke test it a bit.

[mattdurham]

Not your issue but can we fix the doc, this should be default in the example

[jkroepke]

@mattdurham I hope I address all you issues!

[mattdurham]

I may tweak a few things here and there but this is solid.

[mattdurham]

Fantastic work, some small formatting things/deprecation notes but I will fix them post merge.

[mattdurham]

@jkroepke can you debug the windows_exporter, I noticed when debugging agent on windows and also windows_exporter directly I get a syscall error. Several others were able to recreate. Running without the debugger is fine.

[mattdurham]

Seems to be a specific line in perflib.go syscall.RegCloseKey(syscall.HKEY_PERFORMANCE_DATA), if debugger is attached it fails, if not then it succeeds

[mattdurham]

And to close this out found the issue leoluk/perflib_exporter#42, if you check the error while running on RegKeyClose it returns invalid handle which for whatever reason crashes when debugger is attached.

[kago-dk]

https://github.com/grafana/agent/blob/main/docs/sources/static/configuration/integrations/windows-exporter-config.md should be updated to cover the changes mentioned in the changelog.

And the changelog states iss instead of iis