You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
@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.
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.Telemetry data types supported
Metrics
The text was updated successfully, but these errors were encountered: