.. _envoy_v3_api_file_envoy/extensions/access_loggers/open_telemetry/v3alpha/logs_service.proto: OpenTelemetry (gRPC) Access Log =============================== .. warning:: This API is work-in-progress and is subject to breaking changes. .. _envoy_v3_api_msg_extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig: extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig ----------------------------------------------------------------------------- :repo:`[extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig proto] ` Configuration for the built-in *envoy.access_loggers.open_telemetry* :ref:`AccessLog `. This configuration will populate `opentelemetry.proto.collector.v1.logs.ExportLogsServiceRequest.resource_logs `_. OpenTelemetry `Resource `_ attributes are filled with Envoy node info. In addition, the request start time is set in the dedicated field. .. _extension_envoy.access_loggers.open_telemetry: This extension may be referenced by the qualified name ``envoy.access_loggers.open_telemetry`` .. note:: This extension is intended to be robust against untrusted downstream traffic. It assumes that the upstream is trusted. .. tip:: This extension extends and can be used with the following extension category: - :ref:`envoy.access_loggers ` .. code-block:: json { "common_config": "{...}", "body": "{...}", "attributes": "{...}" } .. _envoy_v3_api_field_extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig.common_config: common_config (:ref:`extensions.access_loggers.grpc.v3.CommonGrpcAccessLogConfig `, *REQUIRED*) .. _envoy_v3_api_field_extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig.body: body (.opentelemetry.proto.common.v1.AnyValue) OpenTelemetry `LogResource `_ fields, following `Envoy access logging formatting `_. See 'body' in the LogResource proto for more details. Example: ``body { string_value: "%PROTOCOL%" }``. .. _envoy_v3_api_field_extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig.attributes: attributes (.opentelemetry.proto.common.v1.KeyValueList) See 'attributes' in the LogResource proto for more details. Example: ``attributes { values { key: "user_agent" value { string_value: "%REQ(USER-AGENT)%" } } }``.