Update Existing Pipelines

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Overview

For existing pipelines in Observability Pipelines, you can update and deploy changes for source settings, destination settings, and processors in the Observability Pipelines UI. But if you want to update source and destination environment variables, you need to manually update the Worker with the new values.

Update an existing pipeline

  1. Navigate to Observability Pipelines.
  2. Select the pipeline you want to update.
  3. Click Edit Pipeline in the top right corner.
  4. Make changes to the pipeline.
    • If you are updating the source or destination settings shown in the tiles, or updating and adding processors, make the changes and then click Deploy Changes.
    • To update source or destination environment variables, click Go to Worker Installation Steps and see Update source or destination variables for instructions.

Update source or destination variables

On the the Worker installation page:

  1. Select your platform in the Choose your installation platform dropdown menu.
  2. If you want to update source environment variables, update the information for your log source.
      • Datadog Agent address:
        • The Observability Pipelines Worker listens to this socket address to receive logs from the Datadog Agent.
        • Stored in the environment variableDD_OP_SOURCE_DATADOG_AGENT_ADDRESS.
      • Fluent socket address and port:
        • The Observability Pipelines Worker listens on this address for incoming log messages.
        • Stored in the environment variable DD_OP_SOURCE_FLUENT_ADDRESS.

      There are no environment variables for the Google Pub/Sub source.

      • HTTP/s endpoint URL:
        • The Observability Pipelines Worker collects log events from this endpoint. For example, https://127.0.0.8/logs.
        • Stored as the environment variable: DD_OP_SOURCE_HTTP_CLIENT_ENDPOINT_URL.
      • If you are using basic authentication:
        • HTTP/S endpoint authentication username and password.
        • Stored as the environment variables: DD_OP_SOURCE_HTTP_CLIENT_USERNAME and DD_OP_SOURCE_HTTP_CLIENT_PASSWORD.
      • If you are using bearer authentication:
        • HTTP/S endpoint bearer token.
        • Stored as the environment variable: DD_OP_SOURCE_HTTP_CLIENT_BEARER_TOKEN.
      • HTTP/S server address:
        • The Observability Pipelines Worker listens to this socket address, such as 0.0.0.0:9997, for your HTTP client logs.
        • Stored in the environment variable: DD_OP_SOURCE_HTTP_SERVER_ADDRESS.
      • Logstash address and port:
        • The Observability Pipelines Worker listens on this address, such as 0.0.0.0:9997, for incoming log messages.
        • Stored in the environment variable as: DD_OP_SOURCE_LOGSTASH_ADDRESS
      • Splunk HEC address:
        • The bind address that your Observability Pipelines Worker listens on to receive logs originally intended for the Splunk indexer. For example, 0.0.0.0:8088
          Note: /services/collector/event is automatically appended to the endpoint.
        • Stored in the environment variable DD_OP_SOURCE_SPLUNK_HEC_ADDRESS.
      • Splunk TCP address:
        • The Observability Pipelines Worker listens to this socket address to receive logs from the Splunk Forwarder. For example, 0.0.0.0:9997.
        • Stored in the environment variable DD_OP_SOURCE_SPLUNK_TCP_ADDRESS.
      • Sumo Logic address:
        • The bind address that your Observability Pipelines Worker listens on to receive logs originally intended for the Sumo Logic HTTP Source. For example, 0.0.0.0:80.
          Note: /receiver/v1/http/ path is automatically appended to the endpoint.
        • Stored in the environment variable DD_OP_SOURCE_SUMO_LOGIC_ADDRESS.
      • rsyslog or syslog-ng address:
        • The Observability Pipelines Worker listens on this bind address to receive logs from the Syslog forwarder. For example, 0.0.0.0:9997.
        • Stored in the environment variable DD_OP_SOURCE_SYSLOG_ADDRESS.
    • If you want to update destination environment variables, update the information for your log destination.

        Amazon S3

        • AWS access key ID of your S3 archive:

          • Stored in the environment variable: DD_OP_DESTINATION_DATADOG_ARCHIVES_AWS_ACCESS_KEY_ID

        • AWS secret access key ID of your S3 archive:

          • The AWS secret access key ID for the S3 archive bucket.
          • Stored in the environment variable DD_OP_DESTINATION_DATADOG_ARCHIVES_AWS_SECRET_KEY.

        Google Cloud Storage

        There are no environment variables to configure.

        Azure Storage

        • Azure connections string to give the Worker access to your Azure Storage bucket.
          • Stored in the environment variable: DD_OP_DESTINATION_DATADOG_ARCHIVES_AZURE_BLOB_CONNECTION_STRING.

        No environment variables required.

        • Splunk HEC token:
          • The Splunk HEC token for the Splunk indexer.
          • Stored in the environment variable DD_OP_DESTINATION_SPLUNK_HEC_TOKEN.
        • Base URL of the Splunk instance:
          • The Splunk HTTP Event Collector endpoint your Observability Pipelines Worker sends processed logs to. For example, https://hec.splunkcloud.com:8088.
            Note: /services/collector/event path is automatically appended to the endpoint.
          • Stored in the environment variable DD_OP_DESTINATION_SPLUNK_HEC_ENDPOINT_URL.
        • Unique URL generated for the HTTP Logs and Metrics Source to receive log data.
          • The Sumo Logic HTTP Source endpoint. The Observability Pipelines Worker sends processed logs to this endpoint. For example, https://<ENDPOINT>.collection.sumologic.com/receiver/v1/http/<UNIQUE_HTTP_COLLECTOR_CODE>, where:
            • <ENDPOINT> is your Sumo collection endpoint.
            • <UNIQUE_HTTP_COLLECTOR_CODE> is the string that follows the last forward slash (/) in the upload URL for the HTTP source.
          • Stored in the environment variable DD_OP_DESTINATION_SUMO_LOGIC_HTTP_COLLECTOR_URL.
        • The rsyslog or syslog-ng endpoint URL. For example, 127.0.0.1:9997.
          • The Observability Pipelines Worker sends logs to this address and port.
          • Stored as the environment variable: DD_OP_DESTINATION_SYSLOG_ENDPOINT_URL.
        • Google Chronicle endpoint URL:
          • Stored in the environment variable: DD_OP_DESTINATION_GOOGLE_CHRONICLE_UNSTRUCTURED_ENDPOINT_URL.
        • Elasticsearch authentication username:
          • Stored in the environment variable: DD_OP_DESTINATION_ELASTICSEARCH_USERNAME.
        • Elasticsearch authentication password:
          • Stored in the environment variable: DD_OP_DESTINATION_ELASTICSEARCH_PASSWORD.
        • Elasticsearch endpoint URL:
          • Stored in the environment variable: DD_OP_DESTINATION_ELASTICSEARCH_ENDPOINT_URL.
        • OpenSearch authentication username:
          • Stored in the environment variable: DD_OP_DESTINATION_OPENSEARCH_USERNAME.
        • OpenSearch authentication password:
          • Stored in the environment variable: DD_OP_DESTINATION_OPENSEARCH_PASSWORD.
        • OpenSearch endpoint URL:
          • Stored in the environment variable: DD_OP_DESTINATION_OPENSEARCH_ENDPOINT_URL.
        • Amazon OpenSearch authentication username:
          • Stored in the environment variable: DD_OP_DESTINATION_AMAZON_OPENSEARCH_USERNAME.
        • Amazon OpenSearch authentication password:
          • Stored in the environment variable: DD_OP_DESTINATION_AMAZON_OPENSEARCH_PASSWORD.
        • Amazon OpenSearch endpoint URL:
          • Stored in the environment variable: DD_OP_DESTINATION_AMAZON_OPENSEARCH_ENDPOINT_URL.
        • New Relic account ID:
          • Stored in the environment variable: DD_OP_DESTINATION_NEW_RELIC_ACCOUNT_ID.
        • New Relic license:
          • Stored in the environment variable: DD_OP_DESTINATION_NEW_RELIC_LICENSE_KEY.
      • Follow the instructions for your environment to update the worker:
          1. Click Select API key to choose the Datadog API key you want to use.
          2. Run the command provided in the UI to install the Worker. The command is automatically populated with the environment variables you entered earlier.
            docker run -i -e DD_API_KEY=<DATADOG_API_KEY> \
    -e DD_OP_PIPELINE_ID=<PIPELINE_ID> \
    -e DD_SITE=<DATADOG_SITE> \
    -e <SOURCE_ENV_VARIABLE> \
    -e <DESINATION_ENV_VARIABLE> \
    -p 8088:8088 \
    datadog/observability-pipelines-worker run
            Note: By default, the docker run command exposes the same port the Worker is listening on. If you want to map the Worker’s container port to a different port on the Docker host, use the -p | --publish option:
            -p 8282:8088 datadog/observability-pipelines-worker run
          3. Click Navigate Back to go back to the Observability Pipelines edit pipeline page.
          4. Click Deploy Changes.
          1. Download the Helm chart values file.
          2. Click Select API key to choose the Datadog API key you want to use.
          3. Update the Datadog Helm chart to the latest version:
            helm repo update
          4. Run the command provided in the UI to install the Worker. The command is automatically populated with the environment variables you entered earlier.
            helm upgrade --install opw \
-f values.yaml \
--set datadog.apiKey=<DATADOG_API_KEY> \
--set datadog.pipelineId=<PIPELINE_ID> \
--set <SOURCE_ENV_VARIABLES> \
--set <DESTINATION_ENV_VARIABLES> \
--set service.ports[0].protocol=TCP,service.ports[0].port=<SERVICE_PORT>,service.ports[0].targetPort=<TARGET_PORT> \
datadog/observability-pipelines-worker
            Note: By default, the Kubernetes Service maps incoming port <SERVICE_PORT> to the port the Worker is listening on (<TARGET_PORT>). If you want to map the Worker’s pod port to a different incoming port of the Kubernetes Service, use the following service.ports[0].port and service.ports[0].targetPort values:
            --set service.ports[0].protocol=TCP,service.ports[0].port=8088,service.ports[0].targetPort=8282
          5. Click Navigate Back to go back to the Observability Pipelines edit pipeline page.
          6. Click Deploy Changes.

          1. Click Select API key to choose the Datadog API key you want to use.

          2. Run the one-step command provided in the UI to re-install the Worker.

            Note: The environment variables used by the Worker in /etc/default/observability-pipelines-worker are not updated on subsequent runs of the install script. If changes are needed, update the file manually and restart the Worker.

          If you prefer not to use the one-line installation script, follow these step-by-step instructions:

          1. Run the following commands to update your local apt repo and install the latest Worker version:
            sudo apt-get update
sudo apt-get install observability-pipelines-worker datadog-signing-keys
          2. Add your keys, site (for example datadoghq.com for US1), source, and destination environment variables to the Worker’s environment file:
            sudo cat &lt;<EOF > /etc/default/observability-pipelines-worker
DD_API_KEY=<DATADOG_API_KEY>
DD_OP_PIPELINE_ID=<PIPELINE_ID>
DD_SITE=<DATADOG_SITE>
<SOURCE_ENV_VARIABLES>
<DESTINATION_ENV_VARIABLES>
EOF
          3. Restart the worker:
            sudo systemctl restart observability-pipelines-worker
          4. Click Navigate Back to go back to the Observability Pipelines edit pipeline page.
          5. Click Deploy Changes.

          1. Click Select API key to choose the Datadog API key you want to use.

          2. Run the one-step command provided in the UI to re-install the Worker.

            Note: The environment variables used by the Worker in /etc/default/observability-pipelines-worker are not updated on subsequent runs of the install script. If changes are needed, update the file manually and restart the Worker.

          If you prefer not to use the one-line installation script, follow these step-by-step instructions:

          1. Update your packages and install the latest version of Worker:
            sudo yum makecache
sudo yum install observability-pipelines-worker
          2. Add your keys, site (for example datadoghq.com for US1), source, and destination updated environment variables to the Worker’s environment file:
            sudo cat &lt;&lt;-EOF > /etc/default/observability-pipelines-worker
DD_API_KEY=<API_KEY>
DD_OP_PIPELINE_ID=<PIPELINE_ID>
DD_SITE=<SITE>
<SOURCE_ENV_VARIABLES>
<DESTINATION_ENV_VARIABLES>
EOF
          3. Restart the worker:
            sudo systemctl restart observability-pipelines-worker
          4. Click Navigate Back to go back to the Observability Pipelines edit pipeline page.
          5. Click Deploy Changes.
          1. Select the expected log volume for the pipeline from the dropdown.
          2. Select the AWS region you want to use to install the Worker.
          3. Click Select API key to choose the Datadog API key you want to use.
          4. Click Launch CloudFormation Template to navigate to the AWS Console to review the stack configuration and then launch it. Make sure the CloudFormation parameters are set as expected.
          5. Select the VPC and subnet that you want to use to install the Worker.
          6. Review and check the necessary permissions checkboxes for IAM. Click Submit to create the stack. CloudFormation handles the installation at this point; the Worker instances are launched, the necessary software is downloaded, and the Worker starts automatically.
          7. Delete the previous CloudFormation stack and resources associated with it.
          8. Click Navigate Back to go back to the Observability Pipelines edit pipeline page.
          9. Click Deploy Changes.
        PREVIEWING: rtrieu/product-analytics-ui-changes