You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: gdi/opentelemetry/collector-addon/collector-addon-install.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ Follow these steps to install the Splunk Add-on for OpenTelemetry Collector to a
45
45
46
46
#. In Splunk_TA_otel/local, create or open the access_token file, and replace the existing contents with the token value you copied from Splunk Observability Cloud. Save the updated file.
47
47
48
-
#. In :strong:`Splunk Observability Cloud`, select your name, then select the Organization tab to verify that the realm value in the realm and sapm-endpoint files in your local folder reflect the value shown in Splunk Observability Cloud. Save any changes you make in the local files.
48
+
#. In :strong:`Splunk Observability Cloud`, select your name, then select the Organization tab to verify that the realm value in the realm and ingest endpoints files in your local folder reflect the value shown in Splunk Observability Cloud. Save any changes you make in the local files.
49
49
50
50
#. Restart Splunkd. Your Add-on solution is now deployed.
51
51
@@ -75,7 +75,7 @@ Follow these steps to install the Splunk Add-on for the OpenTelemetry Collector
75
75
76
76
#. In Splunk_TA_otel/local, create or open the access_token file, and replace the existing contents with the token value you copied from Splunk Observability Cloud. Save the updated file.
77
77
78
-
#. In :strong:`Splunk Observability Cloud`, select your name, then select the Organization tab to verify that the realm value in the realm and sapm-endpoint files in your local folder match the value shown in Splunk Observability Cloud. Save any changes you make in the local files.
78
+
#. In :strong:`Splunk Observability Cloud`, select your name, then select the Organization tab to verify that the realm value in the realm and ingest endpoints files in your local folder match the value shown in Splunk Observability Cloud. Save any changes you make in the local files.
79
79
80
80
#. In :strong:`Splunk Web`, select :guilabel:`Settings > Forwarder Management` to access your deployment server.
Copy file name to clipboardExpand all lines: gdi/opentelemetry/collector-kubernetes/k8s-troubleshooting/troubleshoot-k8s-sizing.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,17 +50,17 @@ For example:
50
50
51
51
.. code-block::
52
52
53
-
2021-11-12T00:22:32.172Z info exporterhelper/queued_retry.go:325 Exporting failed. Will retry the request after interval. {"kind": "exporter", "name": "sapm", "error": "server responded with 429", "interval": "4.4850027s"}
54
-
2021-11-12T00:22:38.087Z error exporterhelper/queued_retry.go:190 Dropping data because sending_queue is full. Try increasing queue_size. {"kind": "exporter", "name": "sapm", "dropped_items": 1348}
53
+
2021-11-12T00:22:32.172Z info exporterhelper/queued_retry.go:325 Exporting failed. Will retry the request after interval. {"kind": "exporter", "name": "otlphttp", "error": "server responded with 429", "interval": "4.4850027s"}
54
+
2021-11-12T00:22:38.087Z error exporterhelper/queued_retry.go:190 Dropping data because sending_queue is full. Try increasing queue_size. {"kind": "exporter", "name": "otlphttp", "dropped_items": 1348}
55
55
56
-
If you can't fix throttling by bumping limits on the backend or reducing amount of data sent through the Collector, you can avoid OOMs by reducing the sending queue of the failing exporter. For example, you can reduce ``sending_queue`` for the ``sapm`` exporter:
56
+
If you can't fix throttling by bumping limits on the backend or reducing amount of data sent through the Collector, you can avoid OOMs by reducing the sending queue of the failing exporter. For example, you can reduce ``sending_queue`` for the ``otlphttp`` exporter:
Copy file name to clipboardExpand all lines: gdi/opentelemetry/components/otlphttp-exporter.rst
+43-59Lines changed: 43 additions & 59 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,24 +7,26 @@ OTLP/HTTP exporter
7
7
.. meta::
8
8
:description: The OTLP/HTTP exporter allows the OpenTelemetry Collector to send metrics, traces, and logs via HTTP using the OTLP format. Read on to learn how to configure the component.
9
9
10
-
The OTLP/HTTP exporter sends metrics, traces, and logs through HTTP using the OTLP format. The supported pipeline types are ``traces``, ``metrics``, and ``logs``. See :ref:`otel-data-processing` for more information.
11
-
12
-
You can also use the OTLP exporter for advanced options to send data using the OTLP format. See more at :ref:`otlp-exporter`.
10
+
.. note:: Use the OTLP/HTTP exporter as the default method to send traces to Splunk Observability Cloud.
13
11
14
-
If you need to bypass the Collector and send data in the OTLP format directly to Splunk Observability Cloud:
12
+
The OTLP/HTTP exporter sends metrics, traces, and logs through HTTP using the OTLP format. The supported pipeline types are ``traces``, ``metrics``, and ``logs``. See :ref:`otel-data-processing` for more information.
15
13
16
-
* To send metrics, use the otlp endpoint. Find out more in the dev portal at :new-page:`Sending data points <https://dev.splunk.com/observability/docs/datamodel/ingest>`. Note that this option only accepts protobuf payloads.
17
-
18
-
* To send traces, use the gRPC endpoint. For more information, see :ref:`grpc-data-ingest`.
14
+
You can also use the OTLP exporter for advanced options to send data using gRPC protocol. See more at :ref:`otlp-exporter`.
19
15
20
16
Read more about the OTLP format at the OTel repo :new-page:`OpenTelemetry Protocol Specification <https://github.com/open-telemetry/opentelemetry-proto/blob/main/docs/specification.md>`.
21
17
22
18
Get started
23
19
======================
24
20
21
+
.. note::
22
+
23
+
This component is included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector to send traces to Splunk Observability Cloud when deploying in host monitoring (agent) mode. See :ref:`otel-deployment-mode` for more information.
24
+
25
+
For details about the default configuration, see :ref:`otel-kubernetes-config`, :ref:`linux-config-ootb`, or :ref:`windows-config-ootb`. You can customize your configuration any time as explained in this document.
26
+
25
27
Follow these steps to configure and activate the component:
26
28
27
-
1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
29
+
1. Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
28
30
29
31
- :ref:`otel-install-linux`
30
32
- :ref:`otel-install-windows`
@@ -33,63 +35,54 @@ Follow these steps to configure and activate the component:
33
35
2. Configure the exporter as described in the next section.
34
36
3. Restart the Collector.
35
37
36
-
The OTLP/HTTP exporter is not included in the default configuration of the Splunk Distribution of the OpenTelemetry Collector. If you want to add it, the following settings are required:
38
+
Configuration options
39
+
--------------------------------
37
40
38
-
* ``endpoint``. The target base URL to send data to, for example ``https://example.com:4318``. No default value.
41
+
The following settings are required:
39
42
40
-
* Each type of signal is added to this base URL. For example, for traces, ``https://example.com:4318/v1/traces``.
43
+
* ``traces_endpoint``. The target URL to send trace data to. ``https://ingest.<realm>.signalfx.com/v2/trace/otlp`` for Splunk Observability Cloud.
41
44
42
-
The following settings are optional:
45
+
The following settings are optional and can be added to the configuration for more advanced use cases:
43
46
44
-
* ``logs_endpoint``. The target URL to send log data to.
45
-
46
-
* For example, ``https://example.com:4318/v1/logs``.
47
-
* If this setting is present, the endpoint setting is ignored for logs.
47
+
* ``logs_endpoint``. The target URL to send log data to. For example, ``https://example.com:4318/v1/logs``.
48
48
49
-
* ``metrics_endpoint``. The target URL to send metric data to.
50
-
51
-
* For example, ``https://example.com:4318/v1/metrics``.
52
-
* If this setting is present, the endpoint setting is ignored for metrics.
49
+
* ``metrics_endpoint``. The target URL to send metric data to. For example, ``"https://ingest.us0.signalfx.com/v2/trace/otlp"`` to send metrics to Splunk Observability Cloud.
53
50
54
-
* ``traces_endpoint``. The target URL to send trace data to.
55
-
56
-
* For example, ``https://example.com:4318/v1/traces``.
57
-
* If this setting is present, the endpoint setting is ignored for traces.
58
-
59
-
* ``tls``. See :ref:`TLS Configuration Settings <otlphttp-exporter-settings>` in this document for the full set of available options.
51
+
* ``tls``. See :ref:`TLS Configuration Settings <otlphttp-exporter-settings>` in this document for the full set of available options. Only applicable for sending data to a custom endpoint.
60
52
61
53
* ``timeout``. ``30s`` by default. HTTP request time limit. For details see :new-page:`https://golang.org/pkg/net/http/#Client`.
62
54
63
55
* ``read_buffer_size``. ``0`` by default. ReadBufferSize for HTTP client.
64
56
65
57
* ``write_buffer_size``. ``512 * 1024`` by default. WriteBufferSize for the HTTP client.
66
58
67
-
Sample configurations
59
+
Sample configuration
68
60
--------------------------------
69
61
70
62
To send traces and metrics to Splunk Observability Cloud using OTLP over HTTP, configure the ``metrics_endpoint`` and ``traces_endpoint`` settings to the REST API ingest endpoints. For example:
0 commit comments