Feature: IIS metrics about windows_exporter HOT 7 CLOSED

I'm working on this via the Win32_PerfRawData_W3SVC_WebService class. There are a lot of different sources for IIS in perfmon however, so maybe there are other classes which are better suited?

from windows_exporter.

Very nice! I was thinking earlier today about other Windows metrics, in particular SQL Server stuff (which I will need to investigate sooner or later anyway), and if they are exposed in WMI, would they fit this collector, or as separate project.

Assuming they are available as WMI, I guess they can fit in this project.

In any case I think it would make sense for the user to be able to configure the exported collectors, since in this case IIS might not be useful as enabled by default for all users.

from windows_exporter.

Yup, I'm thinking we should just copy the structure used in node_exporter, with a flag for enabled-collectors

from windows_exporter.

Agreed. Perhaps the "perf" and "os" ones should be exported by default.

from windows_exporter.

IIS is a network service, so should have its own exporter (unless you're going to go down the JMX exporter route).

from windows_exporter.

From the discussions in #5:

What I'd see happening for IIS/SQL is that you'd run the WMI exporter but with different flags just pulling in IIS/SQL metrics.

@brian-brazil With users running multiple exporters for servers with multiple databases/webapps, much like for other exporters, I assume? We'll need to test that at larger scales, I think. I've seen non-negligible performance impact from running many WMI queries (the current approach would just be one query for all say 20 sites, rather than 20 queries for one site each).

from windows_exporter.

This is related to #12

from windows_exporter.