HTTP Configuration Settings

HTTP exposes a variety of settings. Several of these settings are available for configuration within individual receivers or exporters.

Client Configuration

Exporters leverage client configuration.

Note that client configuration supports TLS configuration, however configuration parameters are not defined under tls_settings like server configuration. For more information, see configtls README.

• endpoint: address:port
• headers: name/value pairs added to the HTTP request headers
• read_buffer_size
• timeout
• write_buffer_size

Example:

exporter:
  otlp:
    endpoint: otelcol2:55690
    headers:
      test1: "value1"
      "test 2": "value 2"

Server Configuration

Receivers leverage server configuration.

• cors_allowed_origins: An empty list means that CORS is not enabled at all. A wildcard can be used to match any origin or one or more characters of an origin.
• cors_allowed_headers: When CORS is enabled, can be used to specify an optional list of allowed headers. By default, it includes Accept, Content-Type, X-Requested-With. Origin is also always added to the list. A wildcard (*) can be used to match any header.
• endpoint: Valid value syntax available here
• tls_settings

Example:

receivers:
  otlp:
    cors_allowed_origins:
    - https://foo.bar.com
    - https://*.test.com
    cors_allowed_headers:
    - ExampleHeader
    endpoint: 0.0.0.0:55690
    protocols:
      http: