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.

Sign up for GitHub

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

Jump to bottom

Update collector.process.md #1077

Merged
merged 2 commits into from
Oct 22, 2022
Merged

Update collector.process.md #1077

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3477599
Update collector.process.md
latere-a-latere Oct 18, 2022
8f8369a
Fixed spelling error
latere-a-latere Oct 18, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 17 additions & 2 deletions docs/collector.process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# process collector
# Process collector

The process collector exposes metrics about processes
The process collector exposes metrics about processes.

|||
-|-
Expand Down Expand Up @@ -37,6 +37,21 @@ To specify multiple names, use the pipe `|` character:
```
This will match all processes named `firefox`, `FIREFOX` or `chrome` .

## IIS Worker processes

The process collector also queries the `root\\WebAdministration` WMI namespace to check for running IIS workers. If it successfully retrieves a list from this namespace, it will append the name of the worker's application pool to the corresponding process. Whitelist/blacklist matching occurs before this name is appended, so you don't have to take this name in consideration when writing your expression.

Note that this specific feature **only works** if the [IIS Management Scripts and Tools](https://learn.microsoft.com/en-us/iis/manage/scripting/managing-sites-with-the-iis-wmi-provider) are installed. If they are not installed then all worker processes return as just `w3wp`.

### Example

Given an IIS server with two websites called "Prometheus.io" and "Example.com" running under the application pools "Public website" and "Test", the process names returned will look as follows:

```
w3wp_Public website
w3wp_Test
```

## Metrics

Name | Description | Type | Labels
Expand Down