From 37b67a42b9b20c14494a6b13ac1a2a877d0e3984 Mon Sep 17 00:00:00 2001 From: Samiur Arif Date: Wed, 20 Nov 2024 13:50:49 -0800 Subject: [PATCH 1/8] adding telegraf installation steps --- gdi/monitoring.rst | 1 + gdi/monitors-monitoring/telegraf.rst | 83 ++++++++++++++++++++++++++++ 2 files changed, 84 insertions(+) create mode 100644 gdi/monitors-monitoring/telegraf.rst diff --git a/gdi/monitoring.rst b/gdi/monitoring.rst index b8483c842..e414c76bd 100644 --- a/gdi/monitoring.rst +++ b/gdi/monitoring.rst @@ -29,6 +29,7 @@ These application receivers gather metrics from their associated monitoring appl * :ref:`nagios` * :ref:`signalfx-forwarder` * :ref:`telegraf-win-perf-counters` +* :ref:`telegraf` These exporters determine where to send the received data. diff --git a/gdi/monitors-monitoring/telegraf.rst b/gdi/monitors-monitoring/telegraf.rst new file mode 100644 index 000000000..e40af2fdb --- /dev/null +++ b/gdi/monitors-monitoring/telegraf.rst @@ -0,0 +1,83 @@ +.. _telegraf: + +Telegraf +================== + +.. meta:: + :description: Use this Splunk Observability Cloud integration for the telegraf monitor. See benefits, install, configuration, and metrics + + +Instead of using The Splunk Distribution of the OpenTelemetry Collector's Smart Agent receiver with the +Telegraf monitor to scrape metrics, it is recommended to install Telegraf plugin independently, then push metrics to the Splunk Opentelemetry collector +via OTLP. + + + +.. note:: All the setup was carried out on a Linux Ubuntu OS based machine but should be replicable on any machines running Linux OS with Debian flavor. + +These instruction to install the telegraf plugin to scrape metrics on other OS (for e.g. MacOS/Windows) operating systems, have not been tested +out. + +Benefits +-------- + +.. include:: /_includes/benefits.rst + +Installation of Telegraf Plugin +---------------------------------- + +Run the following commands to install Telegraf from the InfluxData repository: + +.. code:: shell + + curl --silent --location -O \ https://repos.influxdata.com/influxdata-archive.key \ && echo "943666881a1b8d9b849b74caebf02d3465d6beb716510d86a39f6c8e8dac7515 influxdata-archive.key" \ + | sha256sum -c - && cat influxdata-archive.key \ + | gpg --dearmor \ + | sudo tee /etc/apt/trusted.gpg.d/influxdata-archive.gpg > /dev/null \ + && echo 'deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main' \ + | sudo tee /etc/apt/sources.list.d/influxdata.list + sudo apt-get update && sudo apt-get install telegraf + + +After successful installation of telegraf above, you can add the following to your telegraf configuration file (usually the config file resides on +./etc/telegraf/telegraf.d directory) + + + # Send OpenTelemetry metrics over gRPC + [[outputs.opentelemetry]] + +For detailed information on the Telegraf Opentelemetry output plugin configuration, check https://github.com/influxdata/telegraf/blob/master/plugins/outputs/opentelemetry/README.md + +Configuration +------------- + +To retrieve metrics from this telegraf installation running independently, the following Collector +configuration is sufficient: + +.. code:: yaml + + receivers: + otlp: + protocols: + http: + grpc: + signalfx: + exporters: + signalfx: + access_token: "SPLUNK_TOKEN" + realm: "us0" + service: + pipelines: + metrics: + receivers: [otlp] + exporters: [signalfx] + metrics/internal: + receivers: [signalfx] + processors: + exporters: [signalfx] + + +Troubleshooting +--------------- + +.. include:: /_includes/troubleshooting-components.rst From 02e55bf0320e5db4a32e66756e03d51ccaf391f6 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Fri, 22 Nov 2024 07:46:59 +0100 Subject: [PATCH 2/8] Update monitoring.rst --- gdi/monitoring.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdi/monitoring.rst b/gdi/monitoring.rst index e414c76bd..c5f0ec895 100644 --- a/gdi/monitoring.rst +++ b/gdi/monitoring.rst @@ -28,8 +28,8 @@ These application receivers gather metrics from their associated monitoring appl * :ref:`jaeger-grpc` * :ref:`nagios` * :ref:`signalfx-forwarder` -* :ref:`telegraf-win-perf-counters` * :ref:`telegraf` +* :ref:`telegraf-win-perf-counters` These exporters determine where to send the received data. From e83fcb0783059013c8940b25a5fd6d69d334b53d Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Fri, 22 Nov 2024 08:32:10 +0100 Subject: [PATCH 3/8] Update telegraf.rst Edits --- gdi/monitors-monitoring/telegraf.rst | 52 +++++++++++++++------------- 1 file changed, 28 insertions(+), 24 deletions(-) diff --git a/gdi/monitors-monitoring/telegraf.rst b/gdi/monitors-monitoring/telegraf.rst index e40af2fdb..e5f23c0b0 100644 --- a/gdi/monitors-monitoring/telegraf.rst +++ b/gdi/monitors-monitoring/telegraf.rst @@ -1,31 +1,33 @@ .. _telegraf: -Telegraf -================== +Telegraf Exec (OpenTelemetry) +============================== .. meta:: - :description: Use this Splunk Observability Cloud integration for the telegraf monitor. See benefits, install, configuration, and metrics + :description: Use this Splunk Observability Cloud integration for the Telegraf monitor. See benefits, install, configuration, and metrics. +To monitor your system with Telegraf Exec using native OpenTelemetry, install the Telegraf plugin independently, then push metrics to the Splunk Opentelemetry Collector +via OTLP. -Instead of using The Splunk Distribution of the OpenTelemetry Collector's Smart Agent receiver with the -Telegraf monitor to scrape metrics, it is recommended to install Telegraf plugin independently, then push metrics to the Splunk Opentelemetry collector -via OTLP. - - - -.. note:: All the setup was carried out on a Linux Ubuntu OS based machine but should be replicable on any machines running Linux OS with Debian flavor. - -These instruction to install the telegraf plugin to scrape metrics on other OS (for e.g. MacOS/Windows) operating systems, have not been tested -out. +.. note:: This setup is designed for a Linux Ubuntu OS but should be replicable on any machines running Linux OS with Debian flavor. These instructions might not work on other OS (MacOS/Windows). Benefits -------- .. include:: /_includes/benefits.rst -Installation of Telegraf Plugin +Configuration ---------------------------------- +Follow these steps to scrape Telegraf metrics with the OTel Collector: + +1. Install the Telegraf Exec Input plugin +2. Set up the OpenTelemetry Output plugin +3. Configure the OpenTelemetry Collector + +1. Install the Telegraf Exec Input Plugin plugin +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Run the following commands to install Telegraf from the InfluxData repository: .. code:: shell @@ -38,21 +40,24 @@ Run the following commands to install Telegraf from the InfluxData repository: | sudo tee /etc/apt/sources.list.d/influxdata.list sudo apt-get update && sudo apt-get install telegraf +2. Set up the OpenTelemetry Output plugin +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -After successful installation of telegraf above, you can add the following to your telegraf configuration file (usually the config file resides on -./etc/telegraf/telegraf.d directory) - +Next, add the OTel Output plugin to your Telegraf configuration file: +.. code:: + # Send OpenTelemetry metrics over gRPC [[outputs.opentelemetry]] - -For detailed information on the Telegraf Opentelemetry output plugin configuration, check https://github.com/influxdata/telegraf/blob/master/plugins/outputs/opentelemetry/README.md -Configuration -------------- +The config file usually resides on the ./etc/telegraf/telegraf.d directory. -To retrieve metrics from this telegraf installation running independently, the following Collector -configuration is sufficient: +For detailed information on the Telegraf Opentelemetry output plugin see the :new-page:`Exec Input Plugin ` documentation in GitHub. + +3. Configure the OpenTelemetry Collector +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Add the following configuration to the OTel Collector to retrieve metrics from the Telegraf installation: .. code:: yaml @@ -76,7 +81,6 @@ configuration is sufficient: processors: exporters: [signalfx] - Troubleshooting --------------- From 18edcd6c566ea1d76610cf7ce55209b65051ccc4 Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Fri, 22 Nov 2024 13:11:47 +0100 Subject: [PATCH 4/8] Update telegraf.rst More edits --- gdi/monitors-monitoring/telegraf.rst | 75 ++++++++++++++++++++-------- 1 file changed, 55 insertions(+), 20 deletions(-) diff --git a/gdi/monitors-monitoring/telegraf.rst b/gdi/monitors-monitoring/telegraf.rst index e5f23c0b0..2de5661d1 100644 --- a/gdi/monitors-monitoring/telegraf.rst +++ b/gdi/monitors-monitoring/telegraf.rst @@ -1,12 +1,12 @@ .. _telegraf: -Telegraf Exec (OpenTelemetry) -============================== +Monitor services with Telegraf and OpenTelemetry +======================================================== .. meta:: :description: Use this Splunk Observability Cloud integration for the Telegraf monitor. See benefits, install, configuration, and metrics. -To monitor your system with Telegraf Exec using native OpenTelemetry, install the Telegraf plugin independently, then push metrics to the Splunk Opentelemetry Collector +To monitor your service with Telegraf using native OpenTelemetry in Splunk Observability Cloud, install the service's Telegraf plugin then push metrics to the Splunk Opentelemetry Collector via OTLP. .. note:: This setup is designed for a Linux Ubuntu OS but should be replicable on any machines running Linux OS with Debian flavor. These instructions might not work on other OS (MacOS/Windows). @@ -21,11 +21,12 @@ Configuration Follow these steps to scrape Telegraf metrics with the OTel Collector: -1. Install the Telegraf Exec Input plugin -2. Set up the OpenTelemetry Output plugin -3. Configure the OpenTelemetry Collector +1. Install Telegraf +2. Set up your service's Telegraf Input plugin +3. Set up the Telegraf OpenTelemetry Output plugin +4. Configure the OpenTelemetry Collector -1. Install the Telegraf Exec Input Plugin plugin +1. Install Telegraf ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Run the following commands to install Telegraf from the InfluxData repository: @@ -40,7 +41,39 @@ Run the following commands to install Telegraf from the InfluxData repository: | sudo tee /etc/apt/sources.list.d/influxdata.list sudo apt-get update && sudo apt-get install telegraf -2. Set up the OpenTelemetry Output plugin +2. Set up your service's Telegraf Input plugin +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Next, install the Telegraf Input plugin for the service you want to monitor. Available plugins include Chrony, Consul, Docker, Elasticsearch, Fluentd, GitHub, Jenkins, RabbitMQ or SQL. Find a complete list of Input plugins at :new-page:`Telegraf Input plugins ` in GitHub. + +For example, if you want to monitor Exec, use a setup like: + +.. code:: + + # Read metrics from one or more commands that can output to stdout + [[inputs.exec]] + + ## Commands array + commands = ["sh /etc/otelcustom/mqmscripts/fileagemonitor.sh"] + timeout = "30s" + data_format = "influx" + + ## Environment variables + ## Array of "key=value" pairs to pass as environment variables + ## e.g. "KEY=value", "USERNAME=John Doe", + ## "LD_LIBRARY_PATH=/opt/custom/lib64:/usr/local/libs" + # environment = [] + + ## Measurement name suffix + ## Used for separating different commands + # name_suffix = "" + + ## Ignore Error Code + ## If set to true, a non-zero error code in not considered an error and the + ## plugin will continue to parse the output. + # ignore_error = false + +3. Set up the Telegraf OpenTelemetry Output plugin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Next, add the OTel Output plugin to your Telegraf configuration file: @@ -52,26 +85,28 @@ Next, add the OTel Output plugin to your Telegraf configuration file: The config file usually resides on the ./etc/telegraf/telegraf.d directory. -For detailed information on the Telegraf Opentelemetry output plugin see the :new-page:`Exec Input Plugin ` documentation in GitHub. +For detailed information see Telegraf's :new-page:`OpenTelemetry Output plugin ` documentation in GitHub. -3. Configure the OpenTelemetry Collector +4. Configure the OpenTelemetry Collector ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Add the following configuration to the OTel Collector to retrieve metrics from the Telegraf installation: .. code:: yaml - receivers: - otlp: + receivers: + otlp: protocols: - http: - grpc: - signalfx: - exporters: - signalfx: - access_token: "SPLUNK_TOKEN" - realm: "us0" - service: + http: + grpc: + signalfx: + + exporters: + signalfx: + access_token: "SPLUNK_TOKEN" + realm: "us0" + + service: pipelines: metrics: receivers: [otlp] From 1fbc88e78f51a4cad3567fb1864c4c8995c41c0a Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Tue, 26 Nov 2024 11:09:08 +0100 Subject: [PATCH 5/8] Update gdi/monitors-monitoring/telegraf.rst Co-authored-by: Aunsh Chaudhari --- gdi/monitors-monitoring/telegraf.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdi/monitors-monitoring/telegraf.rst b/gdi/monitors-monitoring/telegraf.rst index 2de5661d1..200f0b934 100644 --- a/gdi/monitors-monitoring/telegraf.rst +++ b/gdi/monitors-monitoring/telegraf.rst @@ -54,7 +54,7 @@ For example, if you want to monitor Exec, use a setup like: [[inputs.exec]] ## Commands array - commands = ["sh /etc/otelcustom/mqmscripts/fileagemonitor.sh"] + commands = ["sh /testfolder/testscript.sh"] timeout = "30s" data_format = "influx" From bba96dd38069b6856e1db385e4272d9410ea3e5d Mon Sep 17 00:00:00 2001 From: Anna U <104845867+aurbiztondo-splunk@users.noreply.github.com> Date: Tue, 26 Nov 2024 11:09:20 +0100 Subject: [PATCH 6/8] Update gdi/monitors-monitoring/telegraf.rst Co-authored-by: Aunsh Chaudhari --- gdi/monitors-monitoring/telegraf.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdi/monitors-monitoring/telegraf.rst b/gdi/monitors-monitoring/telegraf.rst index 200f0b934..f27a37aa5 100644 --- a/gdi/monitors-monitoring/telegraf.rst +++ b/gdi/monitors-monitoring/telegraf.rst @@ -46,7 +46,7 @@ Run the following commands to install Telegraf from the InfluxData repository: Next, install the Telegraf Input plugin for the service you want to monitor. Available plugins include Chrony, Consul, Docker, Elasticsearch, Fluentd, GitHub, Jenkins, RabbitMQ or SQL. Find a complete list of Input plugins at :new-page:`Telegraf Input plugins ` in GitHub. -For example, if you want to monitor Exec, use a setup like: +For example, if you want to monitor execute commands on every interval and parse metrics from their output with the exec input plugin, use a setup like: .. code:: From 93c673f4333dc998791be9c4ca6905b701099ebf Mon Sep 17 00:00:00 2001 From: Anna Urbiztondo Date: Tue, 26 Nov 2024 11:36:08 +0100 Subject: [PATCH 7/8] WIP --- gdi/integrations-list.rst | 4 +++- gdi/monitors-databases/exec-input.rst | 6 ++---- .../otel-other/otel-other-landing.rst | 21 +++++++++++++++++++ .../otel-other}/prometheus-generic.rst | 0 .../otel-other}/telegraf.rst | 1 + 5 files changed, 27 insertions(+), 5 deletions(-) create mode 100644 gdi/opentelemetry/otel-other/otel-other-landing.rst rename gdi/{monitors-prometheus => opentelemetry/otel-other}/prometheus-generic.rst (100%) rename gdi/{monitors-monitoring => opentelemetry/otel-other}/telegraf.rst (99%) diff --git a/gdi/integrations-list.rst b/gdi/integrations-list.rst index a89d4da75..a3f0e1560 100644 --- a/gdi/integrations-list.rst +++ b/gdi/integrations-list.rst @@ -19,7 +19,8 @@ Supported integrations in Splunk Observability Cloud Infrastructure monitoring APM instrumentation RUM instrumentation - OpenTelemetry receivers + OpenTelemetry: Receivers + OpenTelemetry: Other ingestion methods Applications: Caches and memory TOGGLE Applications: Cloud platforms TOGGLE Applications: Cloudfoundry @@ -130,6 +131,7 @@ You can monitor your applications and services with the Collector and the follow You can also send data to Splunk Observability Cloud with OpenTelemetry with the following options: * :ref:`prometheus-generic` +* :ref:`telegraf-generic` .. raw:: html diff --git a/gdi/monitors-databases/exec-input.rst b/gdi/monitors-databases/exec-input.rst index c0a40b07b..3bbd292d9 100644 --- a/gdi/monitors-databases/exec-input.rst +++ b/gdi/monitors-databases/exec-input.rst @@ -10,11 +10,9 @@ Exec Input (deprecated) The Exec Input monitor is now deprecated and will reach of End of Support on February 3, 2025. During this period only critical security and bug fixes are provided. When End of Support is reached, the monitor will be removed and no longer be supported, and you won't be able to use it to send data to Splunk Observability Cloud. - To monitor your system with Telegraf Exec you can use native OpenTelemetry instead. See more at :new-page:`OpenTelemetry Output Plugin ` in GitHub. + To monitor your system with Telegraf Exec you can use native OpenTelemetry instead. See :ref:`telegraf-generic` to learn how. -The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the -Exec Input monitor type, an embedded form of the Telegraf Exec plugin, -to receive metrics or logs from exec files. +The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the Exec Input monitor type, an embedded form of the Telegraf Exec plugin, to receive metrics or logs from exec files. Benefits -------- diff --git a/gdi/opentelemetry/otel-other/otel-other-landing.rst b/gdi/opentelemetry/otel-other/otel-other-landing.rst new file mode 100644 index 000000000..a3171fada --- /dev/null +++ b/gdi/opentelemetry/otel-other/otel-other-landing.rst @@ -0,0 +1,21 @@ +.. _otel-other-landing: + +****************************************** +Collector components: Receivers +****************************************** + +.. meta:: + :description: Learn about other options to send your data with OpenTelemetry to Splunk Observability Cloud OpenTelemetry Collector. + +.. toctree:: + :maxdepth: 4 + :titlesonly: + :hidden: + + prometheus-generic + telegraf-generic + +On top of the available native :ref:`OpenTelemetry receivers `, you can also send data to Splunk Observability Cloud with OpenTelemetry with the following options: + +* :ref:`prometheus-generic` +* :ref:`telegraf-generic` \ No newline at end of file diff --git a/gdi/monitors-prometheus/prometheus-generic.rst b/gdi/opentelemetry/otel-other/prometheus-generic.rst similarity index 100% rename from gdi/monitors-prometheus/prometheus-generic.rst rename to gdi/opentelemetry/otel-other/prometheus-generic.rst diff --git a/gdi/monitors-monitoring/telegraf.rst b/gdi/opentelemetry/otel-other/telegraf.rst similarity index 99% rename from gdi/monitors-monitoring/telegraf.rst rename to gdi/opentelemetry/otel-other/telegraf.rst index f27a37aa5..94fe139d3 100644 --- a/gdi/monitors-monitoring/telegraf.rst +++ b/gdi/opentelemetry/otel-other/telegraf.rst @@ -1,4 +1,5 @@ .. _telegraf: +.. _telegraf-generic: Monitor services with Telegraf and OpenTelemetry ======================================================== From 3cd9c451b87dba360077844d7e434d465678fa5a Mon Sep 17 00:00:00 2001 From: Anna Urbiztondo Date: Tue, 26 Nov 2024 12:08:27 +0100 Subject: [PATCH 8/8] Fixes --- gdi/integrations-list.rst | 2 +- gdi/monitoring.rst | 3 --- gdi/opentelemetry/otel-other/otel-other-landing.rst | 4 ++-- gdi/prometheus.rst | 13 +++++-------- 4 files changed, 8 insertions(+), 14 deletions(-) diff --git a/gdi/integrations-list.rst b/gdi/integrations-list.rst index a3f0e1560..13e2ac245 100644 --- a/gdi/integrations-list.rst +++ b/gdi/integrations-list.rst @@ -20,7 +20,7 @@ Supported integrations in Splunk Observability Cloud APM instrumentation RUM instrumentation OpenTelemetry: Receivers - OpenTelemetry: Other ingestion methods + OpenTelemetry: Other ingestion methods Applications: Caches and memory TOGGLE Applications: Cloud platforms TOGGLE Applications: Cloudfoundry diff --git a/gdi/monitoring.rst b/gdi/monitoring.rst index c5f0ec895..8b8ef6c02 100644 --- a/gdi/monitoring.rst +++ b/gdi/monitoring.rst @@ -13,11 +13,9 @@ Configure application exporters and receivers for monitoring monitors-monitoring/cadvisor monitors-monitoring/cgroups - Istio monitors-monitoring/jaeger-grpc monitors-monitoring/nagios monitors-monitoring/signalfx-forwarder - opentelemetry/components/splunk-apm-exporter monitors-monitoring/win_perf_counters These application receivers gather metrics from their associated monitoring applications and the hosts the applications are running on. @@ -28,7 +26,6 @@ These application receivers gather metrics from their associated monitoring appl * :ref:`jaeger-grpc` * :ref:`nagios` * :ref:`signalfx-forwarder` -* :ref:`telegraf` * :ref:`telegraf-win-perf-counters` These exporters determine where to send the received data. diff --git a/gdi/opentelemetry/otel-other/otel-other-landing.rst b/gdi/opentelemetry/otel-other/otel-other-landing.rst index a3171fada..0137a1661 100644 --- a/gdi/opentelemetry/otel-other/otel-other-landing.rst +++ b/gdi/opentelemetry/otel-other/otel-other-landing.rst @@ -1,7 +1,7 @@ .. _otel-other-landing: ****************************************** -Collector components: Receivers +Other OpenTelemetry ingestion methods ****************************************** .. meta:: @@ -13,7 +13,7 @@ Collector components: Receivers :hidden: prometheus-generic - telegraf-generic + telegraf On top of the available native :ref:`OpenTelemetry receivers `, you can also send data to Splunk Observability Cloud with OpenTelemetry with the following options: diff --git a/gdi/prometheus.rst b/gdi/prometheus.rst index 63d18d9be..3cba12379 100644 --- a/gdi/prometheus.rst +++ b/gdi/prometheus.rst @@ -11,8 +11,6 @@ Configure application receivers with Prometheus metrics :maxdepth: 4 :hidden: - monitors-prometheus/prometheus-generic - opentelemetry/components/prometheus-receiver monitors-prometheus/prometheus-exporter monitors-prometheus/prometheus-go monitors-prometheus/prometheus-nginx-ingress @@ -20,15 +18,14 @@ Configure application receivers with Prometheus metrics monitors-prometheus/prometheus-node monitors-prometheus/prometheus-velero -You can use the OpenTelementry native Prometheus receiver to gather metrics from any software, tool or service that exposes metrics in the Prometheus format, such as Ansible Tower (AWX), CockroachDB, Docker Daemon, Doorman, Etcd, Flink, Grafana, PATROL, Traefik, or Zipkin. See more at :ref:`prometheus-receiver`. +Splunk Observability Cloud offers the following OTel solutions to monitor applications and services that expose metrics in the Prometheus format: -Splunk Observability Cloud offers the following solutions: +* :ref:`prometheus-receiver`. You can use the OpenTelementry native Prometheus receiver to gather metrics from any software, tool or service that exposes metrics in the Prometheus format, such as Ansible Tower (AWX), CockroachDB, Docker Daemon, Doorman, Etcd, Flink, Grafana, PATROL, Traefik, or Zipkin. +* :ref:`prometheus-generic`. -* :ref:`prometheus-generic` -* :ref:`prometheus-receiver` -* See a complete list of third-party applications compatible with Prometheus in :new-page:`Prometheus' official documentation `. +You can find the complete list of third-party applications compatible with Prometheus in :new-page:`Prometheus' official documentation `. -See also: +The following Smart Agent monitors are also available: * :ref:`prometheus-exporter` * :ref:`prometheus-go`