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

New component: IIS Metric Receiver #8370

Closed
Mrod1598 opened this issue Mar 10, 2022 · 2 comments
Closed

New component: IIS Metric Receiver #8370

Mrod1598 opened this issue Mar 10, 2022 · 2 comments
Labels
Accepted Component New component has been sponsored

Comments

@Mrod1598
Copy link
Contributor

The purpose and use-cases of the new component

The IIS Metric Receiver would pull KPI stats from windows performance counters using the windowsperfcountersreceiver as a base to build off of.

Targeted versions would be IIS 8+ because IIS 7- are EOL

Example configuration for the component

collection_interval (default = 10s): This receiver collects metrics on an interval. Valid time units are ns, us (or µs), ms, s, m, h.

receivers:
  iis:
    collection_interval: 10s

Telemetry data types supported

Metrics

@mx-psi mx-psi added the Sponsor Needed New component seeking sponsor label Mar 10, 2022
@djaglowski
Copy link
Member

I would like to sponsor this.

@open-telemetry/collector-contrib-maintainer, any reservations about adding a component that depends on another like this? Technically, the collector already supports the ability to collect whatever metrics this one would, but having them predefined in a turnkey solution is a huge value to users. My understanding is that the collector is designed to support this.

@codeboten
Copy link
Contributor

I would like to sponsor this.

@open-telemetry/collector-contrib-maintainer, any reservations about adding a component that depends on another like this? Technically, the collector already supports the ability to collect whatever metrics this one would, but having them predefined in a turnkey solution is a huge value to users. My understanding is that the collector is designed to support this.

I think there's already precedent for this in the collector, for example the simpleprometheusreceiver exposes a subset of the prometheusreceiver. I think this component would be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Component New component has been sponsored
Projects
None yet
Development

No branches or pull requests

4 participants