IIS Application Pool metrics

[syron]

Component(s)

receiver/iis

Is your feature request related to a problem? Please describe.

An application pool can be stopped or started. Sometimes, due to password changes and server restarts, the application pools can not be started and is therefore stopped.

Describe the solution you'd like

It would be great to get a list of all available application pools while also scraping the performance counters and for each and every one of them, the state (whether they are running or not).

An application pool can have the following states:

State	Id	Description
Started	1	The Site, ApplicationPool, or WorkerProcess object has started.
Starting	0	The object is in the process of starting.
Stopped	3	The object has stopped.
Stopping	2	The object is in the process of stopping.
Unknown	4	The object is in an unknown state.

(Source: https://learn.microsoft.com/en-us/dotnet/api/microsoft.web.administration.objectstate?view=iis-dotnet)

Describe alternatives you've considered

Developing a windows exporter in dotnet that runs as a Windows service providing the data to the otel collector.

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/iis: @Mrod1598 @pjanotti

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[pjanotti]

This is effectively a proposal to add a metric mapping the APP_POOL_WAS(*)\Current Application Pool State performance counter.

[pjanotti]

/label os:windows

[crobert-1]

Removing needs triage based on code owner response that this is a valid enhancement request.

[syron]

Would it be possible for me to start to work on this? I don't know the procedure here, but as I have read I am supposed to comment the ticket so it could potentially be assigned to me?

[crobert-1]

Hello @syron, thanks for being willing to help out here! It doesn't look like anyone else has picked up this work yet, so you're welcome to work on it 👍

[syron]

Sorry for the late response. Awesome, thanks @crobert-1 I will start working on it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/iis: @Mrod1598 @pjanotti

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[pjanotti]

Hi @syron, are you still planning to work on this issue?

[syron]

Hi @syron, are you still planning to work on this issue?

Hi @pjanotti! Yes, I am planning to work on this. I had to repriotize unfortunately, but now I am back on track.

[syron]

I have added a pull request for this. However, I need to go through some of the formalia. #38183

[syron]

One question that came to my mind. The metrics that have been merged are marked as enabled = false and one of the comments by @atoulme was to create a new PR with enabled = true and mark it as breaking change. In order for this issue to be closed, should a new PR be created for this or should a new issue be raised and this one closed?

[atoulme]

Start with a new PR.