HTTP Client Source

Ce produit n'est pas pris en charge par le site Datadog que vous avez sélectionné. ().
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.
Disponible pour:

Logs

Use Observability Pipelines’ HTTP/S Client source to pull logs from the upstream HTTP/S server. Select and set up this source when you set up a pipeline.

Prerequisites

To use Observability Pipelines’ HTTP/S Client source, you need the following information available:

  1. The full path of the HTTP Server endpoint that the Observability Pipelines Worker collects log events from. For example, https://127.0.0.8/logs.
  2. The HTTP authentication token or password.

The HTTP/S Client source pulls data from your upstream HTTP server. Your HTTP server must support GET requests for the HTTP Client endpoint URL that you set as an environment variable when you install the Worker.

Set up the source in the pipeline UI

Select and set up this source when you set up a pipeline. The information below is for the source settings in the pipeline UI.

To configure your HTTP/S Client source:

Only enter the identifiers for the HTTP Client endpoint URL and, if applicable, your authorization strategy secrets. Do not enter the actual values.
  1. Enter the identifier for your HTTP Client endpoint URL. If you leave it blank, the default is used.
  2. Select your authorization strategy. If you selected:
    • Basic:
      • Enter the identifier for your HTTP Client username. If you leave it blank, the default is used.
      • Enter the identifier for your HTTP Client password. If you leave it blank, the default is used.
    • Bearer: Enter the identifier for your bearer token. If you leave it blank, the default is used.
  3. Select the decoder you want to use on the HTTP messages. Logs pulled from the HTTP source must be in this format.

Optional settings

Enable TLS

Toggle the switch to Enable TLS. If you enable TLS, the following certificate and key files are required.
Note: All file paths are made relative to the configuration data directory, which is /var/lib/observability-pipelines-worker/config/ by default. See Advanced Worker Configurations for more information. The file must be owned by the observability-pipelines-worker group and observability-pipelines-worker user, or at least readable by the group or user.

  • Enter the identifier for your HTTP Client key pass. If you leave it blank, the default is used. - Note: Only enter the identifier for the key pass. Do not enter the actual key pass.
  • Server Certificate Path: The path to the certificate file that has been signed by your Certificate Authority (CA) root file in DER or PEM (X.509) format.
  • CA Certificate Path: The path to the certificate file that is your Certificate Authority (CA) root file in DER or PEM (X.509) format.
  • Private Key Path: The path to the .key private key file that belongs to your Server Certificate Path in DER or PEM (PKCS#8) format.

Scrape settings

  • Enter the interval between scrapes.
    • Your HTTP Server must be able to handle GET requests at this interval.
    • Since requests run concurrently, if a scrape takes longer than the interval given, a new scrape is started, which can consume extra resources. Set the timeout to a value lower than the scrape interval to prevent this from happening.
  • Enter the timeout for each scrape request.

Set secrets

These are the defaults used for secret identifiers and environment variables.

Note: If you enter identifiers for your secrets 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.

    • HTTP Client endpoint URL identifier:
      • References the endpoint from which the Observability Pipelines Worker collects log events.
      • The default identifier is SOURCE_HTTP_CLIENT_ENDPOINT_URL.
    • HTTP Client TLS passphrase identifier (when TLS is enabled):
      • The default identifier is SOURCE_HTTP_CLIENT_KEY_PASS.
    • If you are using basic authentication:
      • HTTP Client username identifier:
        • The default identifier is SOURCE_HTTP_CLIENT_USERNAME.
      • HTTP Client password identifier:
        • The default identifier is SOURCE_HTTP_CLIENT_PASSWORD.
    • If you are using bearer authentication:
      • HTTP Client bearer token identifier:
        • The default identifier is SOURCE_HTTP_CLIENT_BEARER_TOKEN.
    • HTTP/s endpoint URL:
      • The Observability Pipelines Worker collects log events from this endpoint. For example, https://127.0.0.8/logs.
      • The default environment variable is DD_OP_SOURCE_HTTP_CLIENT_ENDPOINT_URL.
    • HTTP/S Client TLS passphrase (when enabled):
      • The default environment variable is DD_OP_SOURCE_HTTP_CLIENT_KEY_PASS.
    • If you are using basic authentication:
      • HTTP/S endpoint authentication username and password.
      • The default environment variable is DD_OP_SOURCE_HTTP_CLIENT_USERNAME and DD_OP_SOURCE_HTTP_CLIENT_PASSWORD.
    • If you are using bearer authentication:
      • HTTP/S endpoint bearer token.
      • The default environment variable is DD_OP_SOURCE_HTTP_CLIENT_BEARER_TOKEN.