Windows exporter module - Metrics

[Imshelledin21]

There are still a few outstanding items that I haven't managed to get working

• [textfile_directory] argument. When trying to specify a custom path (i.e. C:\Prometheus\Files): escaping slashes threw an error with Alloy, and the service wouldn't start on Windows. I'm probably just missing something stupid here.
• [timeout] attribute on prometheus.windows.exporter threw an error when specified in config.

I'll dig further into those, but the module works as-is currently, and supports the Windows Integration Dashboards in Grafana Cloud (Metric Queries Only).

I have a few other ideas for expanding this module out some more, but I'll get to those later.

• scrape existing windows exporter service and remote write metrics. From my sampling of customers at least, they have historically used the agent windows exporter integration, rather than using the vanilla windows exporter, hence the direction I took this one initially.
• additional_collectors argument. Provide the ability to add collectors on top of the default one, without having to specify the whole default list again
• expansion for additional collector config blocks

[CLAassistant]

All committers have signed the CLA.

[timo1707]

Hi @Imshelledin21 :
when adding the text_file block to prometheus.exporter.windows "local" it should work.

I have a smartstatus.prom in this path, and its working fine. but i am not using the argument yet in my case.

text_file {
    text_file_directory = "C:\\ProgramData\\GrafanaLabs\\Alloy"
  }