Token-Based Authentication for Secure HTTP (Collection)

We're excited to introduce secure token-based authentication for HTTP sources. This new capability allows you to authenticate using a unique token in the request header, maintaining the existing HTTPS endpoint behavior while adding token validation per source.

Obtain the token to use in an auth header when you configure an HTTP source or regenerate the URL. To learn more, see:

• Configure an HTTP Logs and Metrics Source
• Create an OTLP/HTTP Source
• Generate a New URL for an HTTP Source

note

Token-based authentication in the request header is supported for the following HTTP sources:

• HTTP Logs and Metrics
• HTTP Traces Source
• RUM HTTP Traces Source
• OTLP/HTTP Source
• Zoom HTTP Source

Token-based authentication in the request header is not supported for:

• AWS Kinesis Firehose for Logs Source
• AWS Kinesis Firehose for Metrics Source
• Google Cloud Platform Source