Microsoft .NET 🔗
The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the dotnet
monitor type to report metrics for .NET applications.
This integration is only available on Windows.
This integration reports the instantaneous values for Windows Performance Counters. Most of these performance counters are gauges that represent rates per second and percentages. This means that in a collection interval, spikes might occur on the Performance Counters. The best way to mitigate this limitation is to increase the reporting interval on this monitor to collect more frequently.
The following is a list of the most critical .NET performance counters:
Exceptions
Logical threads
Physical threads
Heap bytes
Time in GC
Committed bytes
Pinned objects
Benefits 🔗
After you configure the integration, you can access these features:
View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.
Access the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.
Installation 🔗
Follow these steps to deploy this integration:
Deploy the Splunk Distribution of OpenTelemetry Collector to your host:
Configure the monitor, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.
Configuration 🔗
To use this integration of a Smart Agent monitor with the Collector:
Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.
Read more on how to Use Smart Agent monitors with the Collector.
See how to set up the Smart Agent receiver.
Learn about config options in Collector default configuration.
Example 🔗
To activate this integration, add the following to your Collector configuration:
receivers:
smartagent/dotnet:
type: dotnet
... # Additional config
Next, add the monitor to the service > pipelines > metrics > receivers
section of your configuration file:
service:
pipelines:
metrics:
receivers: [smartagent/dotnet]
Configuration settings 🔗
The following table shows the configuration options for this integration:
Option |
Required |
Type |
Description |
---|---|---|---|
|
no |
|
Number of seconds that wildcards in counter paths should be expanded and how often to refresh counters from configuration. (default: |
|
no |
|
Print out the configurations that match available performance counters. This option is used for debugging. (default: |
Metrics 🔗
This integration emits all metrics by default, but they are categorized as custom metrics. See the notes for more details.
Notes 🔗
Learn more about the available metric types in Observability Cloud.
Default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See more about metric categories.
To add additional metrics, see how to configure
extraMetrics
using the Collector.
Troubleshooting 🔗
If you are not able to see your data in Splunk Observability Cloud, try these tips:
Submit a case in the Splunk Support Portal
Available to Splunk Observability Cloud customers
-
Available to Splunk Observability Cloud customers
Ask a question and get answers through community support at Splunk Answers
Available to Splunk Observability Cloud customers and free trial users
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide
Available to Splunk Observability Cloud customers and free trial users
To learn how to join, see Get Started with Splunk Community - Chat groups
To learn about even more support options, see Splunk Customer Success.