-
Notifications
You must be signed in to change notification settings - Fork 700
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
Process collector serves different results on two near-identical servers #1074
Comments
latere-a-latere
changed the title
Process collector serves different results on two servers
Process collector serves different results on two near-identical servers
Oct 7, 2022
latere-a-latere
added a commit
to latere-a-latere/windows_exporter
that referenced
this issue
Oct 18, 2022
Documented IIS worker process apppool matching. Discovered this feature at [process.go:221](https://github.com/prometheus-community/windows_exporter/blob/eb73859393991318a6ae08da53f863cee4a9d2a1/collector/process.go#L221). This also solves issue prometheus-community#1074. Signed-off-by: MarNicGit <[email protected]>
latere-a-latere
added a commit
to latere-a-latere/windows_exporter
that referenced
this issue
Oct 18, 2022
Documented IIS worker process apppool matching. Discovered this feature at [process.go:221](https://github.com/prometheus-community/windows_exporter/blob/eb73859393991318a6ae08da53f863cee4a9d2a1/collector/process.go#L221). This also solves issue prometheus-community#1074. Signed-off-by: MarNicGit <[email protected]>
Spent a bit of digging and turns out that this happens when the IIS Management Scripts and Tools are installed. I've created PR #1077 which documents this feature. |
mansikulkarni96
pushed a commit
to mansikulkarni96/prometheus-community-windows_exporter
that referenced
this issue
Mar 9, 2023
Documented IIS worker process apppool matching. Discovered this feature at [process.go:221](https://github.com/prometheus-community/windows_exporter/blob/eb73859393991318a6ae08da53f863cee4a9d2a1/collector/process.go#L221). This also solves issue prometheus-community#1074. Signed-off-by: MarNicGit <[email protected]>
anubhavg-icpl
pushed a commit
to anubhavg-icpl/windows_exporter
that referenced
this issue
Sep 22, 2024
Documented IIS worker process apppool matching. Discovered this feature at [process.go:221](https://github.com/prometheus-community/windows_exporter/blob/eb73859393991318a6ae08da53f863cee4a9d2a1/collector/process.go#L221). This also solves issue prometheus-community#1074. Signed-off-by: MarNicGit <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have two servers:
Both servers run the same IIS version and have windows_exporter 0.20 installed. I use the following config file on both installations:
On server A, my metrics look like this:
On server B, they look like this:
Server B for some reason also tells me the user (appPool name) that is running the w3wp.exe process, which is great and preferable, because it allows me to distinguish the process in Grafana. Why does server A completely omit this? Am I missing a setting somewhere?
The text was updated successfully, but these errors were encountered: