IIS receiver
Grabs metrics about an IIS instance using Windows Performance Counters.
The IIS receiver grabs metrics from an IIS instance using Windows Performance Counters. The supported pipeline type is metrics. See Process your data with pipelines for more information.
Deploy the collector
See Install the Collector for Windows with the installer script.
Configure the receiver
Edit your OpenTelemetry Collector configuration file as follows.
-
Add
issto thereceiverssection:YAMLreceivers: iis: collection_interval: 10s initial_delay: 1sThe IIS receiver has two optional settings:
collection_interval.10sby default. The interval at which the receiver emits metrics.initial_delay.1sby default. Defines how long this receiver waits before starting.
-
Add
isstoservice.pipelines.metrics:YAMLservice: pipelines: metrics: receivers: [iss]
Restart the collector
The restart command varies depending on what platform you deployed the collector on and what tool you used to deploy it. Here are general examples of the restart command:
- Linux
-
BASH
sudo systemctl restart splunk-otel-collector - Windows
-
Windows with installer script:
BASHstop-service splunk-otel-collector start-service splunk-otel-collector - Kubernetes
-
BASH
helm upgrade your-splunk-otel-collector splunk-otel-collector-chart/splunk-otel-collector -f your-override-values.yamlwhere
splunk-otel-collector-chartis the name you gave to the Helm chart in thehelm repo addcommand.
Settings reference
The following table shows the configuration options for the IIS receiver:
included
https://raw.githubusercontent.com/splunk/collector-config-tools/main/cfg-metadata/receiver/iis.yaml
Metrics reference
To see the available metrics, resource attributes, and attributes refer to IIS default metrics in GitHub.