Supervisor π
Description π
The Splunk Distribution of OpenTelemetry Collector provides this integration as the supervisor
monitor type for the Smart Agent Receiver.
Use this integration to retrieve the state of processes running by the Supervisor.
This integration is available for Kubernetes, Windows, and Linux.
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 or container platform:
Configure the monitor, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.
Configuration π
To use this Smart Agent monitor with the Collector, include the smartagent
receiver and service pipeline in your configuration file. The Smart Agent receiver is fully supported only on x86_64/amd64 platforms.
Read more in Use Smart Agent monitors with the Collector.
Learn about config options in Collector default configuration.
See the examples below for more details.
Note
Provide a Supervisor monitor entry in your Collector or Smart Agent (deprecated) configuration. Use the appropriate form for your agent type.
Splunk Distribution of OpenTelemetry Collector π
To activate this monitor in the Splunk Distribution of OpenTelemetry Collector, add the following to your agent configuration:
receivers:
smartagent/supervisor:
type: supervisor
... # Additional config
To complete the monitor activation, you must also include the smartagent/supervisor
receiver item in a metrics
pipeline. To do this, add the receiver item to the service
> pipelines
> metrics
> receivers
section of your configuration file. For example:
service:
pipelines:
metrics:
receivers: [smartagent/supervisor]
Smart Agent π
To activate this monitor in the Smart Agent, add the following to your agent configuration:
monitors: # All monitor config goes under this key
- type: supervisor
... # Additional config
See Install and configure the SignalFx Smart Agent for an autogenerated example of a YAML configuration file, with default values where applicable.
Configuration settings π
The following table shows the configuration options for this monitor:
Option |
Required |
Type |
Description |
---|---|---|---|
|
No |
|
The host/IP address of the Supervisor XML-RPC API. Used to build the |
|
No |
|
The port of the Supervisor XML-RPC API. Used to build the |
|
No |
|
If true, the monitor connects to the Supervisor using the HTTPS protocol instead of the HTTP protocol. The default value is |
|
No |
|
The URL path to use for the scrape URL for Supervisor. The default value is |
|
No |
|
URL on which to scrape Supervisor XML-RPC API. If this is not provided, itβs derived from the |
Metrics π
The following metrics are available for this integration:
Get help π
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.