diff --git a/_includes/gdi/application-receiver-table-deprecated.rst b/_includes/gdi/application-receiver-table-deprecated.rst new file mode 100644 index 000000000..2de64e9af --- /dev/null +++ b/_includes/gdi/application-receiver-table-deprecated.rst @@ -0,0 +1,25 @@ +* :ref:`asp-dot-net` +* :ref:`amazon-ecs-metadata` +* :ref:`chrony` +* :ref:`collectd-df` +* :ref:`consul` +* :ref:`disk` +* :ref:`exec-input` +* :ref:`load` +* :ref:`interface` +* :ref:`java-monitor` +* :ref:`kong` +* :ref:`kubernetes-cluster` +* :ref:`kube-controller-manager` +* :ref:`kubelet-stats` +* :ref:`microsoft-dotnet` +* :ref:`mongodb` +* :ref:`mongodb-atlas` +* :ref:`mysql` +* :ref:`nagios` +* :ref:`postgresql` +* :ref:`redis` +* :ref:`signalfx-forwarder` +* :ref:`statsd` +* :ref:`telegraf-win-perf-counters` + diff --git a/_includes/gdi/application-receiver-table.rst b/_includes/gdi/application-receiver-table.rst index 549214a06..d19862c9d 100644 --- a/_includes/gdi/application-receiver-table.rst +++ b/_includes/gdi/application-receiver-table.rst @@ -8,10 +8,6 @@ - :strong:`Provides metrics` - :strong:`Provides traces` - * - :ref:`amazon-ecs-metadata` - - :strong:`X` - - - * - :ref:`activemq` - :strong:`X` - @@ -40,10 +36,6 @@ - :strong:`X` - - * - :ref:`asp-dot-net` - - :strong:`X` - - - * - :ref:`appmesh` - :strong:`X` - @@ -60,10 +52,6 @@ - :strong:`X` - - * - :ref:`chrony` - - :strong:`X` - - - * - :ref:`cloudfoundry-firehose-nozzle` - :strong:`X` - @@ -72,18 +60,10 @@ - :strong:`X` - - * - :ref:`collectd-df` - - :strong:`X` - - - * - :ref:`collectd-uptime` - :strong:`X` - - * - :ref:`consul` - - :strong:`X` - - - * - :ref:`conviva` - :strong:`X` - @@ -104,10 +84,6 @@ - :strong:`X` - - * - :ref:`disk` - - :strong:`X` - - - * - :ref:`dns` - :strong:`X` - @@ -124,14 +100,6 @@ - :strong:`X` - - * - :ref:`etcd` - - :strong:`X` - - - - * - :ref:`exec-input` - - :strong:`X` - - - * - :ref:`expvar` - :strong:`X` - @@ -160,10 +128,6 @@ - :strong:`X` - - * - :ref:`health-checker` - - :strong:`X` - - - * - :ref:`heroku` - :strong:`X` - @@ -180,18 +144,10 @@ - - - * - :ref:`load` - - :strong:`X` - - - * - :ref:`http` - :strong:`X` - - * - :ref:`interface` - - :strong:`X` - - :strong:`X` - * - :ref:`get-started-istio` - :strong:`X` - :strong:`X` @@ -200,10 +156,6 @@ - :strong:`X` - - * - :ref:`java-monitor` - - :strong:`X` - - - * - :ref:`jenkins` - :strong:`X` - @@ -220,30 +172,14 @@ - :strong:`X` - - * - :ref:`kong` - - :strong:`X` - - - * - :ref:`kubernetes-apiserver` - :strong:`X` - - * - :ref:`kubernetes-cluster` - - :strong:`X` - - - - * - :ref:`kube-controller-manager` - - :strong:`X` - - - * - :ref:`kubernetes-events` - :strong:`X` - - * - :ref:`kubelet-stats` - - :strong:`X` - - - * - :ref:`kubernetes-proxy` - :strong:`X` - @@ -272,10 +208,6 @@ - :strong:`X` - - * - :ref:`microsoft-dotnet` - - :strong:`X` - - - * - :ref:`get-started-dotnet-otel` - :strong:`X` - @@ -288,22 +220,6 @@ - :strong:`X` - - * - :ref:`mongodb` - - :strong:`X` - - - - * - :ref:`mongodb-atlas` - - :strong:`X` - - - - * - :ref:`mysql` - - :strong:`X` - - - - * - :ref:`nagios` - - :strong:`X` - - - * - :ref:`net-io` - :strong:`X` - @@ -340,10 +256,6 @@ - :strong:`X` - - * - :ref:`postgresql` - - :strong:`X` - - - * - :ref:`procstat` - :strong:`X` - @@ -380,18 +292,10 @@ - :strong:`X` - - * - :ref:`redis` - - :strong:`X` - - - * - :ref:`hana` - :strong:`X` - - * - :ref:`signalfx-forwarder` - - :strong:`X` - - :strong:`X` - * - :ref:`snmp` - :strong:`X` - @@ -404,10 +308,6 @@ - :strong:`X` - - * - :ref:`statsd` - - :strong:`X` - - - * - :ref:`supervisor` - :strong:`X` - @@ -428,10 +328,8 @@ - :strong:`X` - - * - :ref:`telegraf-win-perf-counters` + * - :ref:`telegraf-win-services` - :strong:`X` - - * - :ref:`telegraf-win-services` - - :strong:`X` - - \ No newline at end of file + diff --git a/_includes/gdi/otel-receivers-table.rst b/_includes/gdi/otel-receivers-table.rst index ccf8ad0c3..82acb7f9b 100644 --- a/_includes/gdi/otel-receivers-table.rst +++ b/_includes/gdi/otel-receivers-table.rst @@ -1,7 +1,9 @@ * :ref:`apache-receiver` * :ref:`apache-spark-receiver` +* :ref:`awsecscontainermetrics-receiver` * :ref:`azureeventhub-receiver` * :ref:`carbon-receiver` +* :ref:`chrony-receiver` * :ref:`cloudfoundry-receiver` * :ref:`collectd-receiver` * :ref:`discovery-receiver` diff --git a/_includes/gdi/processor-architecture-native.rst b/_includes/gdi/processor-architecture-native.rst index f0fb4a00e..b9b422074 100644 --- a/_includes/gdi/processor-architecture-native.rst +++ b/_includes/gdi/processor-architecture-native.rst @@ -220,11 +220,6 @@ - Yes - Yes - Yes - * - ``etcd`` - - Yes - - Yes - - Yes - - Yes * - ``gitlab`` - Yes - Yes diff --git a/_includes/gdi/processor-architecture-subprocess.rst b/_includes/gdi/processor-architecture-subprocess.rst index 8841854af..fc0446c94 100644 --- a/_includes/gdi/processor-architecture-subprocess.rst +++ b/_includes/gdi/processor-architecture-subprocess.rst @@ -134,11 +134,6 @@ - Yes - Experimental - No - * - ``collectd/etcd`` - - Yes - - Yes - - Experimental - - No * - ``collectd/hadoop`` - Yes - Yes diff --git a/gdi/databases.rst b/gdi/databases.rst index 73d064224..9346c22a4 100644 --- a/gdi/databases.rst +++ b/gdi/databases.rst @@ -15,7 +15,6 @@ Configure application receivers for databases monitors-databases/apache-spark monitors-databases/cassandra monitors-databases/consul - monitors-databases/etcd monitors-databases/exec-input monitors-databases/hadoop monitors-databases/hadoopjmx @@ -38,7 +37,6 @@ These application receivers gather metrics from their associated database-relate * :ref:`spark` * :ref:`cassandra` * :ref:`consul` -* :ref:`etcd` * :ref:`exec-input` * :ref:`hadoop` * :ref:`hadoopjmx` diff --git a/gdi/hosts-servers.rst b/gdi/hosts-servers.rst index c0e8e7056..b6236051d 100644 --- a/gdi/hosts-servers.rst +++ b/gdi/hosts-servers.rst @@ -29,7 +29,6 @@ Configure application receivers for hosts and servers monitors-hosts/elasticsearch-query monitors-hosts/filesystems monitors-hosts/haproxy - monitors-hosts/health-checker monitors-hosts/host-metadata opentelemetry/components/host-metrics-receiver monitors-hosts/host-processes @@ -72,7 +71,6 @@ These application receivers gather metrics from their associated host- and serve * :ref:`elasticsearch-query` * :ref:`filesystems` * :ref:`haproxy` -* :ref:`health-checker` * :ref:`host-metadata` * :ref:`host-metrics-receiver` * :ref:`processes` diff --git a/gdi/integrations-list.rst b/gdi/integrations-list.rst index 2a475cd3e..9c35227bb 100644 --- a/gdi/integrations-list.rst +++ b/gdi/integrations-list.rst @@ -107,24 +107,28 @@ For more information, see :ref:`get-started-rum`. .. raw:: html -

OpenTelemetry receivers

+

Applications and services

-Learn more at :ref:`OpenTelemetry receivers `. +.. raw:: html + + +

OpenTelemetry receivers

+ -These are the available OTel receivers: +You can monitor your applications and services with native OpenTelementry receivers. Learn more at :ref:`OpenTelemetry receivers `. + +These are the available OpenTelemetry receivers: .. include:: /_includes/gdi/otel-receivers-table.rst .. raw:: html -

Application and host integrations

+

Smart Agent integrations

-.. note:: The SignalFx Smart Agent has reached End of Support. While the agent can capture and export telemetry to Splunk Observability Cloud, Splunk no longer provides any support, feature updates, security, or bug fixes. Such requests are not bound by any SLAs. - -Smart Agent integrations and application receivers are available and supported through the Splunk Distribution of the OpenTelemetry Collector. For more information, see :ref:`migration-monitors`. +Smart Agent integrations are available and supported through the Splunk Distribution of the OpenTelemetry Collector. For more information, see :ref:`migration-monitors`. Browse available monitors by category: @@ -142,10 +146,20 @@ Browse available monitors by category: * :ref:`Applications: Orchestration ` * :ref:`Applications: Prometheus ` -These are the available Smart Agent monitors: +These are the available Smart Agent integrations: .. include:: /_includes/gdi/application-receiver-table.rst +.. raw:: html + + +

Deprecated integrations

+ + +These Smart Agent integrations are deprecated: + +.. include:: /_includes/gdi/application-receiver-table-deprecated.rst + .. raw:: html diff --git a/gdi/monitors-databases/consul.rst b/gdi/monitors-databases/consul.rst index 3ca721cda..36fade8a9 100644 --- a/gdi/monitors-databases/consul.rst +++ b/gdi/monitors-databases/consul.rst @@ -1,12 +1,18 @@ .. _consul: -Consul datastore -================ +Consul datastore (deprecated) +================================ .. meta:: :description: Use this Splunk Observability Cloud integration for the Consul datastore monitor. See benefits, install, configuration, and metrics -The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the +.. caution:: + + This integration is deprecated and will be removed in a future release. 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 forward Consul datastore metrics to Splunk Observability Cloud use the :ref:`statsd-receiver` or :ref:`prometheus-receiver` instead. + +The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the Consul datastore monitor type to monitor Consul datastores and collect metrics from the following endpoints: diff --git a/gdi/monitors-databases/etcd.rst b/gdi/monitors-databases/etcd.rst deleted file mode 100644 index c86242bb0..000000000 --- a/gdi/monitors-databases/etcd.rst +++ /dev/null @@ -1,180 +0,0 @@ -.. _etcd: - -etcd server -=========== - -.. meta:: - :description: Use this Splunk Observability Cloud integration for the etcd monitor. See benefits, install, configuration, and metrics - -The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the etcd monitor type to report etcd server metrics under the ``/metrics`` path on its client port. Optionally, you can edit the location using ``--listen-metrics-urls``. This integration only collects metrics from the Prometheus endpoint. - -Benefits --------- - -.. include:: /_includes/benefits.rst - -Installation ------------- - -.. include:: /_includes/collector-installation.rst - -Configuration -------------- - -.. include:: /_includes/configuration.rst - -Example -~~~~~~~ - -To activate this integration, add the following to your Collector -configuration: - -.. code-block:: yaml - - receivers: - smartagent/etcd: - type: etcd - ... # Additional config - -Next, add the monitor to the ``service.pipelines.metrics.receivers`` -section of your configuration file: - -.. code:: yaml - - service: - pipelines: - metrics: - receivers: [smartagent/etcd] - -Configuration settings -~~~~~~~~~~~~~~~~~~~~~~ - -The following table shows the configuration options for this monitor: - -.. list-table:: - :widths: 18 18 18 18 - :header-rows: 1 - - - - - - Option - - Required - - Type - - Description - - - - - ``httpTimeout`` - - no - - ``int64`` - - HTTP timeout duration for both read and writes. This should be a - duration string that is accepted by - https://golang.org/pkg/time/#ParseDuration (**default:** - ``10s``) - - - - - ``username`` - - no - - ``string`` - - Basic Auth username to use on each request, if any. - - - - - ``password`` - - no - - ``string`` - - Basic Auth password to use on each request, if any. - - - - - ``useHTTPS`` - - no - - ``bool`` - - If ``true``, the agent will connect to the server using HTTPS - instead of plain HTTP. (**default:** ``false``) - - - - - ``httpHeaders`` - - no - - ``map of strings`` - - A map of HTTP header names to values. Comma separated multiple - values for the same message-header is supported. - - - - - ``skipVerify`` - - no - - ``bool`` - - If useHTTPS is ``true`` and this option is also ``true``, the - exporter TLS cert will not be verified. (**default:** - ``false``) - - - - - ``caCertPath`` - - no - - ``string`` - - Path to the CA cert that has signed the TLS cert, unnecessary if - ``skipVerify`` is set to ``false``. - - - - - ``clientCertPath`` - - no - - ``string`` - - Path to the client TLS cert to use for TLS required connections - - - - - ``clientKeyPath`` - - no - - ``string`` - - Path to the client TLS key to use for TLS required connections - - - - - ``host`` - - **yes** - - ``string`` - - Host of the exporter - - - - - ``port`` - - **yes** - - ``integer`` - - Port of the exporter - - - - - ``useServiceAccount`` - - no - - ``bool`` - - Use pod service account to authenticate. (**default:** - ``false``) - - - - - ``metricPath`` - - no - - ``string`` - - Path to the metrics endpoint on the exporter server, usually - ``/metrics`` (the default). (**default:** ``/metrics``) - - - - - ``sendAllMetrics`` - - no - - ``bool`` - - Send all the metrics that come out of the Prometheus exporter - without any filtering. This option has no effect when using the - prometheus exporter monitor directly since there is no built-in - filtering, only when embedding it in other monitors. - (**default:** ``false``) - -Metrics -------- - -The following metrics are available for this integration: - -.. raw:: html - -
- -Notes -~~~~~ - -.. include:: /_includes/metric-defs.rst - -Troubleshooting ---------------- - -.. include:: /_includes/troubleshooting-components.rst diff --git a/gdi/monitors-hosts/amazon-ecs-metadata.rst b/gdi/monitors-hosts/amazon-ecs-metadata.rst index b2b1d9fcb..315f600bc 100644 --- a/gdi/monitors-hosts/amazon-ecs-metadata.rst +++ b/gdi/monitors-hosts/amazon-ecs-metadata.rst @@ -1,15 +1,14 @@ .. _amazon-ecs-metadata: -Amazon ECS Task Metadata endpoint -================================= +Amazon ECS Task Metadata endpoint (deprecated) +================================================================== .. meta:: :description: Use this Splunk Observability Cloud integration for the ECS metadata monitor. See benefits, install, configuration, and metrics -The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the -``ecs-metadata`` monitor type to read metadata and Docker stats from -Amazon ECS Task Metadata Endpoint version 2. This integration does not -currently support CPU share and quota metrics. +.. caution:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to monitor task metadata and docker stats from Amazon ECS use the native OpenTelemetry component :ref:`awsecscontainermetrics-receiver` instead. + +The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``ecs-metadata`` monitor type to read metadata and Docker stats from Amazon ECS Task Metadata Endpoint version 2. This integration does not currently support CPU share and quota metrics. This integration is only available on Kubernetes and Linux. diff --git a/gdi/monitors-hosts/chrony.rst b/gdi/monitors-hosts/chrony.rst index 8b3183ab3..38a3a2bee 100644 --- a/gdi/monitors-hosts/chrony.rst +++ b/gdi/monitors-hosts/chrony.rst @@ -1,12 +1,14 @@ .. _chrony: -Chrony NTP -========== +Chrony NTP (deprecated) +============================== .. meta:: :description: Use this Splunk Observability Cloud integration for the Chrony NTP monitor. See benefits, install, configuration, and metrics -The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the +.. caution:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to monitor Chrony use the native OpenTelemetry component :ref:`chrony-receiver` instead. + +The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the Chrony NTP monitor type to monitor NTP data from a chrony server, such as clock skew and per-peer stratum. To talk to chronyd, this integration mimics what the chronyc control program does on the wire. diff --git a/gdi/monitors-hosts/disk.rst b/gdi/monitors-hosts/disk.rst index cd382fbe0..b5d7c1758 100644 --- a/gdi/monitors-hosts/disk.rst +++ b/gdi/monitors-hosts/disk.rst @@ -6,7 +6,7 @@ Disk and partition (deprecated) .. meta:: :description: Use this Splunk Observability Cloud integration for the disks monitor. See benefits, install, configuration, and metrics -.. note:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to collect disk I/O metrics, use the native OTel component :ref:`host-metrics-receiver`. +.. caution:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to collect disk I/O metrics, use the native OTel component :ref:`host-metrics-receiver`. Configuration settings ---------------------- diff --git a/gdi/monitors-hosts/health-checker.rst b/gdi/monitors-hosts/health-checker.rst deleted file mode 100644 index f5b4e8cb2..000000000 --- a/gdi/monitors-hosts/health-checker.rst +++ /dev/null @@ -1,177 +0,0 @@ -.. _health-checker: - -Health Checker -============== - -.. meta:: - :description: Use this Splunk Observability Cloud integration for the Health Checker monitor. See benefits, install, configuration, and metrics - -The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the -Health Checker monitor type to check whether the configured JSON value -is returned in the response body. - -Benefits --------- - -.. include:: /_includes/benefits.rst - -Installation ------------- - -.. include:: /_includes/collector-installation.rst - -Configuration -------------- - -.. include:: /_includes/configuration.rst - -### Example - -To activate this integration, add the following to your Collector -configuration: - -.. code-block:: yaml - - receivers: - smartagent/health-checker: - type: collectd/health-checker - ... # Additional config - -Next, add the monitor to the ``service.pipelines.metrics.receivers`` -section of your configuration file: - -.. code-block:: yaml - - service: - pipelines: - metrics: - receivers: [smartagent/health-checker] - -Configuration settings -~~~~~~~~~~~~~~~~~~~~~~ - -The following table shows the configuration options for the Health -Checker monitor: - -.. list-table:: - :widths: 18 18 18 18 - :header-rows: 1 - - - - - - Option - - Required - - Type - - Description - - - - - ``pythonBinary`` - - no - - ``string`` - - Path to a python binary that should be used to execute the - Python code. If not set, a built-in runtime will be used. Can - include arguments to the binary as well. - - - - - ``host`` - - **yes** - - ``string`` - - - - - - - ``port`` - - **yes** - - ``integer`` - - - - - - - ``name`` - - no - - ``string`` - - - - - - - ``path`` - - no - - ``string`` - - The HTTP path that contains a JSON document to verify - (**default:** ``/``) - - - - - ``jsonKey`` - - no - - ``string`` - - If ``jsonKey`` and ``jsonVal`` are given, the given endpoint - will be interpreted as a JSON document and will be expected to - contain the given key and value for the service to be - considered healthy. - - - - - ``jsonVal`` - - no - - ``any`` - - This can be either a string or numeric type - - - - - ``useHTTPS`` - - no - - ``bool`` - - If ``true``, the endpoint will be connected to on HTTPS instead - of plain HTTP. It is invalid to specify this if ``tcpCheck`` is - ``true``. (**default:** ``false``) - - - - - ``skipSecurity`` - - no - - ``bool`` - - If ``true``, and ``useHTTPS`` is ``true``, the server's SSL/TLS - cert will not be verified. (**default:** ``false``) - - - - - ``tcpCheck`` - - no - - ``bool`` - - If ``true``, the plugin will verify that it can connect to the - given host/port value. JSON checking is not supported. - (**default:** ``false``) - -Metrics -------- - -The following metrics are available for this integration: - -.. list-table:: - :widths: 13 34 13 13 - :header-rows: 1 - - - - - - Name - - Description - - Sample value - - Category - - - - - ``gauge.service.health.status`` - - The HTTP response status code for the request made to the - application being monitored. A ``200`` value means an HTTP 200 - OK success status response was returned, so the application is - healthy. - - ``200`` - - Default - - - - - ``gauge.service.health.value`` - - ``0`` means an unhealthy state, and ``1`` means a healthy state. - - ``0`` or ``1`` - - Default - -Notes -~~~~~ - -.. include:: /_includes/metric-defs.rst - -Troubleshooting ---------------- - -.. include:: /_includes/troubleshooting-components.rst diff --git a/gdi/monitors-hosts/host-processload.rst b/gdi/monitors-hosts/host-processload.rst index 49c43cdc3..df45b4ab5 100644 --- a/gdi/monitors-hosts/host-processload.rst +++ b/gdi/monitors-hosts/host-processload.rst @@ -6,7 +6,7 @@ Host process load (deprecated) .. meta:: :description: Use this Splunk Observability Cloud integration for the load monitor. See benefits, install, configuration, and metrics -.. note:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to collect CPU load metrics, use the native OTel component :ref:`host-metrics-receiver`. +.. caution:: This integration is deprecated. If you're using the Splunk Distribution of the OpenTelemetry Collector and want to collect CPU load metrics use the native OTel component :ref:`host-metrics-receiver`. Configuration options --------------------- diff --git a/gdi/monitors-hosts/win-services.rst b/gdi/monitors-hosts/win-services.rst index 3938f1df5..8e7a10e30 100644 --- a/gdi/monitors-hosts/win-services.rst +++ b/gdi/monitors-hosts/win-services.rst @@ -1,7 +1,7 @@ .. _telegraf-win-services: -Windows Services -================ +Windows Services +================================ .. meta:: :description: Use this Splunk Observability Cloud integration for the Telegraf Win_services monitor. See benefits, install, configuration, and metrics diff --git a/gdi/monitors-languages/asp-dot-net.rst b/gdi/monitors-languages/asp-dot-net.rst index 5ccc4ccec..7157d7076 100644 --- a/gdi/monitors-languages/asp-dot-net.rst +++ b/gdi/monitors-languages/asp-dot-net.rst @@ -6,9 +6,13 @@ ASP.NET (deprecated) .. meta:: :description: Use this Splunk Observability Cloud integration for the ASP.NET app monitor. See benefits, install, configuration, and metrics -.. note:: This integration is deprecated and will be removed in February 2025. To forward data to Splunk Observability Cloud, use the Splunk Distribution of OpenTelemetry .NET. For a full list of collected metrics, refer to :ref:`dotnet-otel-metrics-attributes`. +.. caution:: + + This integration is deprecated and will reach End of Support in February 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. -The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the + To forward data from a .NET application to Splunk Observability Cloud use the :ref:`Splunk Distribution of OpenTelemetry .NET ` instead. + +The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``aspdotnet`` monitor type to retrieve metrics for requests, errors, sessions, and worker processes from ASP.NET applications. diff --git a/gdi/monitors-monitoring/win_perf_counters.rst b/gdi/monitors-monitoring/win_perf_counters.rst index 8434134c9..1699e2b9b 100644 --- a/gdi/monitors-monitoring/win_perf_counters.rst +++ b/gdi/monitors-monitoring/win_perf_counters.rst @@ -1,12 +1,16 @@ .. _telegraf-win-perf-counters: -Windows Performance Counters -============================ +Windows Performance Counters (deprecated) +======================================================== .. meta:: :description: Use this Splunk Observability Cloud integration for the Telegraf win_perf_counters monitor for Windows. See benefits, install, configuration, and metrics -.. note:: For information on the OpenTelemetry receiver based on the Windows Performance Counters input plugin, see :ref:`Windows Performance Counters receiver `. +.. caution:: + + This integration is deprecated and will reach End of Support in a future release. 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 forward metrics from Windows Performance Counters to Splunk Observability Cloud use the :ref:`windowsperfcounters-receiver` instead. The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``telegraf/win_perf_counters`` monitor type to receive metrics from Windows performance counters. diff --git a/gdi/monitors-network/statsd.rst b/gdi/monitors-network/statsd.rst index 4dbc6f052..c933a4972 100644 --- a/gdi/monitors-network/statsd.rst +++ b/gdi/monitors-network/statsd.rst @@ -1,11 +1,17 @@ .. _statsd: -Statsd -====== +Statsd (deprecated) +====================== .. meta:: :description: Use this Splunk Observability Cloud integration for the Statsd monitor. See benefits, install, configuration, and metrics +.. caution:: + + This integration is deprecated and will be removed in a future release. 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 forward statsd metrics to Splunk Observability Cloud use the :ref:`statsd-receiver` instead. + The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the ``statsd`` monitor type to collect statsd metrics. It listens on a configured address and port to receive the statsd metrics. This integration supports certain Stats types, which are dispatched as ``counter`` or ``gauges`` types in Splunk Observability Cloud, as displayed in the table. Statsd extensions such as tags are not supported. diff --git a/gdi/opentelemetry/collector-kubernetes/kubernetes-config-advanced.rst b/gdi/opentelemetry/collector-kubernetes/kubernetes-config-advanced.rst index 311195e10..ba14928b5 100644 --- a/gdi/opentelemetry/collector-kubernetes/kubernetes-config-advanced.rst +++ b/gdi/opentelemetry/collector-kubernetes/kubernetes-config-advanced.rst @@ -95,12 +95,12 @@ Availability The following components provide control plane metrics: -* :ref:`CoreDNS `. -* :ref:`etcd`. To retrieve etcd metrics, see :new-page:`Setting up etcd metrics `. -* :ref:`Kubernetes controller manager `. -* :ref:`Kubernetes API server `. -* :ref:`Kubernetes proxy `. -* :ref:`Kubernetes scheduler `. +* :ref:`CoreDNS ` +* :ref:`awsecscontainermetrics-receiver` +* :ref:`Kubernetes controller manager ` +* :ref:`Kubernetes API server ` +* :ref:`Kubernetes proxy ` +* :ref:`Kubernetes scheduler ` Use custom configurations for non-standard control plane components ----------------------------------------------------------------------------- diff --git a/gdi/opentelemetry/collector-kubernetes/metrics-ootb-k8s.rst b/gdi/opentelemetry/collector-kubernetes/metrics-ootb-k8s.rst index 0da0e30ad..a154fe129 100644 --- a/gdi/opentelemetry/collector-kubernetes/metrics-ootb-k8s.rst +++ b/gdi/opentelemetry/collector-kubernetes/metrics-ootb-k8s.rst @@ -553,7 +553,7 @@ Control plane metrics To see the control plane metrics the Collector provides, see: * :ref:`CoreDNS ` -* :ref:`etcd` +* :ref:`awsecscontainermetrics-receiver` * :ref:`Kubernetes controller manager ` * :ref:`Kubernetes API server ` * :ref:`Kubernetes proxy ` diff --git a/gdi/opentelemetry/components.rst b/gdi/opentelemetry/components.rst index ab85e7e6b..090ad0a75 100644 --- a/gdi/opentelemetry/components.rst +++ b/gdi/opentelemetry/components.rst @@ -55,12 +55,18 @@ The Splunk Distribution of the OpenTelemetry Collector includes and supports the * - :ref:`apache-spark-receiver` (``apachespark``) - Fetches metrics for an Apache Spark cluster through the Apache Spark REST API. - Metrics + * - :ref:`awsecscontainermetrics-receiver` (``awsecscontainermetrics``) + - Reads task metadata and docker stats from Amazon ECS and generates resource usage metrics. + - Metrics * - :ref:`azureeventhub-receiver` (``azureeventhub``) - Pulls logs from an Azure event hub. - Logs * - :ref:`carbon-receiver` (``carbon``) - Receives metrics in Carbon plaintext protocol. - Metrics + * - :ref:`chrony-receiver` (``chrony``) + - Go implementation of the ``chronyc`` command to track portability across systems and platforms. + - Metrics * - :ref:`cloudfoundry-receiver` (``cloudfoundry``) - Connects to the Reverse Log Proxy (RLP) gateway of Cloud Foundry to extract metrics. - Metrics diff --git a/gdi/opentelemetry/components/a-components-receivers.rst b/gdi/opentelemetry/components/a-components-receivers.rst index a91dd12c9..a6141772a 100644 --- a/gdi/opentelemetry/components/a-components-receivers.rst +++ b/gdi/opentelemetry/components/a-components-receivers.rst @@ -14,8 +14,10 @@ Collector components: Receivers apache-receiver apache-spark-receiver + awsecscontainermetrics-receiver azureeventhub-receiver carbon-receiver + chrony-receiver cloudfoundry-receiver collectd-receiver discovery-receiver diff --git a/gdi/opentelemetry/components/awsecscontainermetrics-receiver.rst b/gdi/opentelemetry/components/awsecscontainermetrics-receiver.rst new file mode 100644 index 000000000..eebdfa9f0 --- /dev/null +++ b/gdi/opentelemetry/components/awsecscontainermetrics-receiver.rst @@ -0,0 +1,14 @@ +.. _awsecscontainermetrics-receiver: + +************************************** +AWS ECS container metrics receiver +************************************** + +.. meta:: + :description: The AWS ECS Container Metrics Receiver (awsecscontainermetrics) reads task metadata and docker stats from Amazon ECS Task Metadata Endpoint, and generates resource usage metrics (such as CPU, memory, network, and disk) from them. + +The Splunk Distribution of the OpenTelemetry Collector supports the AWS ECS container metrics receiver. Documentation is planned for a future release. + +To find information about this component in the meantime, see :new-page:`AWS ECS container metrics receiver ` on GitHub. + + diff --git a/gdi/opentelemetry/components/chrony-receiver.rst b/gdi/opentelemetry/components/chrony-receiver.rst new file mode 100644 index 000000000..e61e86c09 --- /dev/null +++ b/gdi/opentelemetry/components/chrony-receiver.rst @@ -0,0 +1,12 @@ +.. _chrony-receiver: + +**************************** +Chrony receiver +**************************** + +.. meta:: + :description: Go implementation of the command chronyc tracking to allow for portability across systems and platforms. + +The Splunk Distribution of the OpenTelemetry Collector supports the Chrony receiver. Documentation is planned for a future release. + +To find information about this component in the meantime, see :new-page:`Chrony receiver ` on GitHub.