diff --git a/content/en/observability_pipelines/destinations/amazon_opensearch.md b/content/en/observability_pipelines/destinations/amazon_opensearch.md index 7ee74cef711..b0a466da83d 100644 --- a/content/en/observability_pipelines/destinations/amazon_opensearch.md +++ b/content/en/observability_pipelines/destinations/amazon_opensearch.md @@ -17,7 +17,7 @@ Use Observability Pipelines' Amazon OpenSearch destination to send logs to Amazo Configure the Amazon OpenSearch destination when you [set up a pipeline][6]. You can set up a pipeline in the [UI][1], using the [API][7], or with [Terraform][8]. The steps in this section are configured in the UI. -
Only enter the identifiers for the Amazon OpenSearch endpoint URL, and if applicable, username and password. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Amazon OpenSearch endpoint URL, and if applicable, username and password. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Amazon OpenSearch destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/amazon_security_lake.md b/content/en/observability_pipelines/destinations/amazon_security_lake.md index b3f7fc950ac..8330bdbab78 100644 --- a/content/en/observability_pipelines/destinations/amazon_security_lake.md +++ b/content/en/observability_pipelines/destinations/amazon_security_lake.md @@ -43,7 +43,7 @@ After you select the Amazon Security Lake destination in the pipeline UI: ##### Enable TLS -
Only enter the identifier for the TLS key pass. Do not enter the actual value.
+
For Secrets Management: Only enter the identifier for the TLS key pass. Do not enter the actual value.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
{{% observability_pipelines/tls_settings %}} diff --git a/content/en/observability_pipelines/destinations/crowdstrike_ng_siem.md b/content/en/observability_pipelines/destinations/crowdstrike_ng_siem.md index 10f5f55bba9..60a5b5aed45 100644 --- a/content/en/observability_pipelines/destinations/crowdstrike_ng_siem.md +++ b/content/en/observability_pipelines/destinations/crowdstrike_ng_siem.md @@ -21,7 +21,7 @@ To use the CrowdStrike NG-SIEM destination, you need to set up a CrowdStrike dat Configure the CrowdStrike NG-SIEM destination when you [set up a pipeline][4]. You can set up a pipeline in the [UI][1], using the [API][5], or with [Terraform][6]. The steps in this section are configured in the UI. -
Only enter the identifiers for the CrowdStrike NG-SIEM endpoint URL, token, and if applicable, the TLS pass key. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the CrowdStrike NG-SIEM endpoint URL, token, and if applicable, the TLS pass key. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the CrowdStrike NG-SIEM destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/databricks.md b/content/en/observability_pipelines/destinations/databricks.md index 1d947e48c3e..333773da820 100644 --- a/content/en/observability_pipelines/destinations/databricks.md +++ b/content/en/observability_pipelines/destinations/databricks.md @@ -101,7 +101,7 @@ After you select the Databricks (Zerobus) destination in the pipeline UI:
Databricks (Zerobus) doesn't convert timestamps in string format to Databricks' TIMESTAMP type. If your table uses a timestamp column, see Convert string timestamps to timestamp format for more information.
-
Only enter the identifier for the OAuth client secret. Do not enter the actual value.
+
For Secrets Management: Only enter the identifier for the OAuth client secret. Do not enter the actual value.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
1. Enter the **Ingestion Endpoint** for your Databricks workspace, such as `https://.zerobus..cloud.databricks.com`. The Worker sends logs to this endpoint. 1. Enter the **Table Name** in the format `catalog.schema.table`, such as `main.obs_pipelines.apache_common_logs`. diff --git a/content/en/observability_pipelines/destinations/elasticsearch.md b/content/en/observability_pipelines/destinations/elasticsearch.md index 4418202bf9d..4df38173b66 100644 --- a/content/en/observability_pipelines/destinations/elasticsearch.md +++ b/content/en/observability_pipelines/destinations/elasticsearch.md @@ -25,7 +25,7 @@ Use Observability Pipelines' Elasticsearch destination to send logs or metrics ( Configure the Elasticsearch destination when you [set up a pipeline][7]. You can set up a pipeline in the [UI][1], using the [API][8], or with [Terraform][9]. The steps in this section are configured in the UI. -
Only enter the identifiers for the Elasticsearch endpoint URL, username, and password. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Elasticsearch endpoint URL, username, and password. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Elasticsearch destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/http_client.md b/content/en/observability_pipelines/destinations/http_client.md index a9c7c3b6c7b..3d1df99d4ed 100644 --- a/content/en/observability_pipelines/destinations/http_client.md +++ b/content/en/observability_pipelines/destinations/http_client.md @@ -20,7 +20,7 @@ Use Observability Pipelines' HTTP Client destination to send logs to an HTTP cli Configure the HTTP Client destination when you [set up a pipeline][3]. You can set up a pipeline in the [UI][1], using the [API][4], or with [Terraform][5]. The steps in this section are configured in the UI. -
Only enter the identifiers for the HTTP Client URI and, if applicable, username and password for basic authorization and the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the HTTP Client URI and, if applicable, username and password for basic authorization and the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the HTTP Client destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/kafka.md b/content/en/observability_pipelines/destinations/kafka.md index acd0056c395..9dbe538c517 100644 --- a/content/en/observability_pipelines/destinations/kafka.md +++ b/content/en/observability_pipelines/destinations/kafka.md @@ -29,7 +29,7 @@ Common scenarios when you might use this destination: Configure the Kafka destination when you [set up a pipeline][10]. You can set up a pipeline in the [UI][5], using the [API][11], or with [Terraform][12]. The steps in this section are configured in the UI. -
Only enter the identifiers for the Kafka bootstrap servers and, if applicable, the SASL username and password and the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Kafka bootstrap servers and, if applicable, the SASL username and password and the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Kafka destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/microsoft_sentinel.md b/content/en/observability_pipelines/destinations/microsoft_sentinel.md index f3440b85470..3e5e612e256 100644 --- a/content/en/observability_pipelines/destinations/microsoft_sentinel.md +++ b/content/en/observability_pipelines/destinations/microsoft_sentinel.md @@ -158,7 +158,7 @@ The table below summarizes the Azure and Microsoft Sentinel information you need Set up the Microsoft Sentinel destination when you [set up a pipeline][10]. You can set up a pipeline in the [UI][1], using the [API][11], or with [Terraform][12]. The steps in this section are configured in the UI. -
Only enter the identifiers for the Microsoft Sentinel client secret and Data Collection Endpoint. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Microsoft Sentinel client secret and Data Collection Endpoint. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Microsoft Sentinel destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/new_relic.md b/content/en/observability_pipelines/destinations/new_relic.md index 763f6d39505..0a8616e831a 100644 --- a/content/en/observability_pipelines/destinations/new_relic.md +++ b/content/en/observability_pipelines/destinations/new_relic.md @@ -17,7 +17,7 @@ Use Observability Pipelines' New Relic destination to send logs to New Relic. Configure the New Relic destination when you [set up a pipeline][3]. You can set up a pipeline in the [UI][1], using the [API][4], or with [Terraform][5]. The steps in this section are configured in the UI. -
Only enter the identifiers for the account ID and license. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the account ID and license. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the New Relic destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/opensearch.md b/content/en/observability_pipelines/destinations/opensearch.md index 7b761606342..2471263d49f 100644 --- a/content/en/observability_pipelines/destinations/opensearch.md +++ b/content/en/observability_pipelines/destinations/opensearch.md @@ -17,7 +17,7 @@ Use Observability Pipelines' OpenSearch destination to send logs to OpenSearch. Configure the OpenSearch destination when you [set up a pipeline][6]. You can set up a pipeline in the [UI][1], using the [API][7], or with [Terraform][8]. The steps in this section are configured in the UI. -
Only enter the identifiers for the OpenSearch endpoint URL, username, and password. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the OpenSearch endpoint URL, username, and password. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the OpenSearch destination in the pipeline UI: diff --git a/content/en/observability_pipelines/destinations/sentinelone.md b/content/en/observability_pipelines/destinations/sentinelone.md index 08040f32a58..441c9d93375 100644 --- a/content/en/observability_pipelines/destinations/sentinelone.md +++ b/content/en/observability_pipelines/destinations/sentinelone.md @@ -23,7 +23,7 @@ Configure the SentinelOne destination when you [set up a pipeline][4]. You can s After you select the SentinelOne destination in the pipeline UI: -
Only enter the identifier for the token. Do not enter the actual value.
+
For Secrets Management: Only enter the identifier for the token. Do not enter the actual value.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
1. Enter the identifier for your token. If you leave it blank, the [default](#secret-defaults) is used. 1. Select your SentinelOne logs environment in the dropdown menu. diff --git a/content/en/observability_pipelines/destinations/socket.md b/content/en/observability_pipelines/destinations/socket.md index bff7612e332..96ffaa3cabc 100644 --- a/content/en/observability_pipelines/destinations/socket.md +++ b/content/en/observability_pipelines/destinations/socket.md @@ -19,7 +19,7 @@ Configure the Socket destination when you [set up a pipeline][2]. You can set up After you select the Socket destination in the pipeline UI: -
Only enter the identifier for the socket address and, if appliable, the key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifier for the socket address and, if appliable, the key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
1. Enter the identifier for your address. If you leave it blank, the [default](#secret-defaults) is used. 1. In the **Mode** dropdown menu, select the socket type to use. diff --git a/content/en/observability_pipelines/destinations/splunk_hec.md b/content/en/observability_pipelines/destinations/splunk_hec.md index 0b6dcc2063a..b7614cb32c0 100644 --- a/content/en/observability_pipelines/destinations/splunk_hec.md +++ b/content/en/observability_pipelines/destinations/splunk_hec.md @@ -17,7 +17,7 @@ Use Observability Pipelines' Splunk HTTP Event Collector (HEC) destination to se Configure the Splunk HEC destination when you [set up a pipeline][5]. You can set up a pipeline in the [UI][1], using the [API][6], or with [Terraform][7]. The steps in this section are configured in the UI. -
Observability Pipelines compresses logs with the gzip (level 6) algorithm.
Only enter the identifiers for the Splunk HEC token and endpoint. Do not enter the actual values.
+
For Secrets Management: Observability Pipelines compresses logs with the gzip (level 6) algorithm.
Only enter the identifiers for the Splunk HEC token and endpoint. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Splunk HEC destination in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/amazon_data_firehose.md b/content/en/observability_pipelines/sources/amazon_data_firehose.md index 817976c6fb0..d7ce4820fbd 100644 --- a/content/en/observability_pipelines/sources/amazon_data_firehose.md +++ b/content/en/observability_pipelines/sources/amazon_data_firehose.md @@ -21,7 +21,7 @@ Use Observability Pipelines' Amazon Data Firehose source to receive logs from Am Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][3], using the [API][4], or with [Terraform][5]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Amazon Data Firehose address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Amazon Data Firehose address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Amazon Data Firehose source in the pipeline UI, enter the identifier for your Amazon Data Firehose address. If you leave it blank, the [default](#secret-defaults) is used. diff --git a/content/en/observability_pipelines/sources/amazon_s3.md b/content/en/observability_pipelines/sources/amazon_s3.md index 6effacb7559..1bb00beb7b8 100644 --- a/content/en/observability_pipelines/sources/amazon_s3.md +++ b/content/en/observability_pipelines/sources/amazon_s3.md @@ -21,7 +21,7 @@ Use Observability Pipelines' Amazon S3 source to receive logs from Amazon S3. Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][3], using the [API][4], or with [Terraform][5]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Amazon S3 URL and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Amazon S3 URL and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Amazon S3 source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/datadog_agent.md b/content/en/observability_pipelines/sources/datadog_agent.md index f898480dfe9..045edc01b15 100644 --- a/content/en/observability_pipelines/sources/datadog_agent.md +++ b/content/en/observability_pipelines/sources/datadog_agent.md @@ -35,7 +35,7 @@ Use Observability Pipelines' Datadog Agent source to receive logs or metrics ({{ Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][6], using the [API][7], or with [Terraform][8]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifier for the Datadog Agent address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifier for the Datadog Agent address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Datadog Agent source in the pipeline UI, enter the identifier for your Datadog Agent address. If you leave it blank, the [default](#secret-defaults) is used. diff --git a/content/en/observability_pipelines/sources/fluent.md b/content/en/observability_pipelines/sources/fluent.md index f04a66259e5..de99fc77e1c 100644 --- a/content/en/observability_pipelines/sources/fluent.md +++ b/content/en/observability_pipelines/sources/fluent.md @@ -21,7 +21,7 @@ Use Observability Pipelines' Fluentd or Fluent Bit source to receive logs from t Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][3], using the [API][4], or with [Terraform][5]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Fluent address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Fluent address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Fluent source in the pipeline UI, enter the identifier for your Fluent address. If you leave it blank, the [default](#secret-defaults) is used. diff --git a/content/en/observability_pipelines/sources/http_client.md b/content/en/observability_pipelines/sources/http_client.md index ca19580389c..8f278a873ac 100644 --- a/content/en/observability_pipelines/sources/http_client.md +++ b/content/en/observability_pipelines/sources/http_client.md @@ -21,7 +21,7 @@ Use Observability Pipelines' HTTP/S Client source to pull logs from the upstream Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][3], using the [API][4], or with [Terraform][5]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the HTTP/S Client endpoint URL and, if applicable, your authorization strategy secrets and TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the HTTP/S Client endpoint URL and, if applicable, your authorization strategy secrets and TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the HTTP/S Client source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/http_server.md b/content/en/observability_pipelines/sources/http_server.md index e17c2d8ac90..f252e91ec7d 100644 --- a/content/en/observability_pipelines/sources/http_server.md +++ b/content/en/observability_pipelines/sources/http_server.md @@ -23,7 +23,7 @@ You can also [send AWS vended logs with Datadog Lambda Forwarder to Observabilit Set up this source when you [set up a pipeline][3]. You can set up a pipeline in the [UI][1], using the [API][4], or with [Terraform][5]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the HTTP/S Server address and, if applicable, the username and password for plain (also known as basic) authorization and the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the HTTP/S Server address and, if applicable, the username and password for plain (also known as basic) authorization and the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the HTTP/S Server source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/kafka.md b/content/en/observability_pipelines/sources/kafka.md index 521872591a3..f99d79274f5 100644 --- a/content/en/observability_pipelines/sources/kafka.md +++ b/content/en/observability_pipelines/sources/kafka.md @@ -23,7 +23,7 @@ You can also [send Azure Event Hub logs to Observability Pipelines using the Kaf Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][7], using the [API][8], or with [Terraform][9]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Kafka servers, username, password, and if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Kafka servers, username, password, and if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Kafka source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/logstash.md b/content/en/observability_pipelines/sources/logstash.md index b299b8fdebd..96853351e43 100644 --- a/content/en/observability_pipelines/sources/logstash.md +++ b/content/en/observability_pipelines/sources/logstash.md @@ -23,7 +23,7 @@ You can also use the Logstash source to [send logs to Observability Pipelines us Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][4], using the [API][5], or with [Terraform][6]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Logstash address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Logstash address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Logstash source in the pipeline UI, enter the identifier for your Logstash address. If you leave it blank, the [default](#secret-defaults) is used. diff --git a/content/en/observability_pipelines/sources/opentelemetry.md b/content/en/observability_pipelines/sources/opentelemetry.md index 3fe5874c0e7..e5bdac85678 100644 --- a/content/en/observability_pipelines/sources/opentelemetry.md +++ b/content/en/observability_pipelines/sources/opentelemetry.md @@ -45,7 +45,7 @@ If your forwarders are globally configured to enable SSL, you need the appropria Set up this source when you [set up a pipeline][6]. You can set up a pipeline in the [UI][10], using the [API][11], or with [Terraform][12]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the OpenTelemetry HTTP and gRPC listener addresses and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the OpenTelemetry HTTP and gRPC listener addresses and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the OpenTelemetry source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/socket.md b/content/en/observability_pipelines/sources/socket.md index 28ad9788871..af8acbb84f8 100644 --- a/content/en/observability_pipelines/sources/socket.md +++ b/content/en/observability_pipelines/sources/socket.md @@ -21,7 +21,7 @@ Use Observability Pipelines' Socket source to send logs to the Worker over a soc Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][3], using the [API][4], or with [Terraform][5]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the socket address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the socket address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Socket source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/splunk_hec.md b/content/en/observability_pipelines/sources/splunk_hec.md index 23ba0c68fe0..0a825c9e063 100644 --- a/content/en/observability_pipelines/sources/splunk_hec.md +++ b/content/en/observability_pipelines/sources/splunk_hec.md @@ -29,7 +29,7 @@ Use Observability Pipelines' Splunk HTTP Event Collector (HEC) source to receive Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][6], using the [API][7], or with [Terraform][8]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Splunk HEC address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Splunk HEC address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Splunk HEC source in the pipeline UI: diff --git a/content/en/observability_pipelines/sources/splunk_tcp.md b/content/en/observability_pipelines/sources/splunk_tcp.md index a815fddb7bc..701d9a66060 100644 --- a/content/en/observability_pipelines/sources/splunk_tcp.md +++ b/content/en/observability_pipelines/sources/splunk_tcp.md @@ -21,7 +21,7 @@ Use Observability Pipelines' Splunk Heavy and Universal Forwards (TCP) source to Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][2], using the [API][3], or with [Terraform][4]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the Splunk TCP address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the Splunk TCP address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Splunk TCP source in the pipeline UI, enter the identifier for your Splunk TCP address. If you leave it blank, the [default](#secret-defaults) is used. diff --git a/content/en/observability_pipelines/sources/syslog.md b/content/en/observability_pipelines/sources/syslog.md index e03cb8de29e..2bd5e2406b8 100644 --- a/content/en/observability_pipelines/sources/syslog.md +++ b/content/en/observability_pipelines/sources/syslog.md @@ -23,7 +23,7 @@ You can also [forward third-party log to syslog](#forward-third-party-logs-to-sy Set up this source when you [set up a pipeline][1]. You can set up a pipeline in the [UI][7], using the [API][8], or with [Terraform][9]. The instructions in this section are for setting up the source in the UI. -
Only enter the identifiers for the syslog address and, if applicable, the TLS key pass. Do not enter the actual values.
+
For Secrets Management: Only enter the identifiers for the syslog address and, if applicable, the TLS key pass. Do not enter the actual values.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.
After you select the Syslog source in the pipeline UI: diff --git a/layouts/shortcodes/observability_pipelines/set_secrets_intro.en.md b/layouts/shortcodes/observability_pipelines/set_secrets_intro.en.md index 5eac2af1d65..55d0a2ea890 100644 --- a/layouts/shortcodes/observability_pipelines/set_secrets_intro.en.md +++ b/layouts/shortcodes/observability_pipelines/set_secrets_intro.en.md @@ -1,3 +1 @@ -These are the defaults used for secret identifiers and environment variables. - -**Note**: If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with `DD_OP`. For example, if you entered `PASSWORD_1` for a password identifier, the environment variable for that password is `DD_OP_PASSWORD_1`. \ No newline at end of file +These are the defaults used for secret identifiers and environment variables. \ No newline at end of file