Skip to content
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

Closed
latere-a-latere opened this issue Oct 7, 2022 · 1 comment · Fixed by #1077
Closed

Process collector serves different results on two near-identical servers #1074

latere-a-latere opened this issue Oct 7, 2022 · 1 comment · Fixed by #1077

Comments

@latere-a-latere
Copy link
Contributor

I have two servers:

  • Server A: Windows Server 2016, OS Build 14393.5291
  • Server B: Windows Server 2016, OS Build 14393.5192

Both servers run the same IIS version and have windows_exporter 0.20 installed. I use the following config file on both installations:

collectors:
  enabled: cpu,os,cs,process,system,net,time,iis,memory,mssql
collector:
  process:
    whitelist: (w3wp|sqlservr).*
log:
  level: warn

On server A, my metrics look like this:

...
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="16340"} 1.665100801756524e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="17080"} 1.665133994863656e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="1756"} 1.6651348187074437e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="17732"} 1.6651008015363705e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="19004"} 1.6651008015409024e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="20696"} 1.6651340591289651e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="21120"} 1.6651008016711247e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="23896"} 1.6651008016025145e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="26168"} 1.6651236574035077e+09
windows_process_start_time{creating_process_id="2196",process="w3wp",process_id="27448"} 1.6651008016065788e+09
windows_process_start_time{creating_process_id="616",process="sqlservr",process_id="3140"} 1.6606089232324252e+09
...

On server B, they look like this:

...
windows_process_start_time{creating_process_id="2408",process="w3wp_Azure DevOps Server Application Pool",process_id="3316"} 1.66375170106868e+09
windows_process_start_time{creating_process_id="2408",process="w3wp_Grafana (rewrite)",process_id="14936"} 1.6651420802270162e+09
windows_process_start_time{creating_process_id="2408",process="w3wp_Prometheus (rewrite)",process_id="7236"} 1.6651423666179688e+09
windows_process_start_time{creating_process_id="712",process="sqlservr",process_id="3552"} 1.6577795374893532e+09
...

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?

@latere-a-latere 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]>
@latere-a-latere
Copy link
Contributor Author

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.

@breed808 breed808 linked a pull request Oct 22, 2022 that will close this issue
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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants