# properties.deploy_env.description
The environment you are deploying, this can be useful for deployment tracking. The string can have any value that makes sense to you to identify the running environment.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.description
The places where you will send telemetry data. You can declare multiple exporters even when they are of the same type. For instance, when you have a self-hosted Grafana and would like to migrate to its cloud version and check the double reporting during the transition. There are two families of exporters: `otlp` or `prometheus`.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.description
The list of OTLP exporters you want to use. Set at least one object to push metrics and traces to an external collector using OTLP.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.custom_metric_reporting_period.description
Whether you want to override the global `metric_reporting_period` attribute set for all exporters or not. Value in seconds. A missing attribute, or set to `0` means using whatever value was used in `metric_reporting_period` at the global level.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.disable_metrics.description
Disable metrics in this exporter (leaving only traces if any). It won't report any metrics when the flag is `true`.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.disable_traces.description
Disable traces in this exporter (leaving only metrics if any). It won't report any metrics when the flag is `true`.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.host.description
The host where you want to push the data. It can be a sidecar or a remote collector.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.name.description
A unique name to identify this exporter.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.port.description
A custom port to send the data. The port defaults to 4317 for gRPC unless you enable `use_http`, which defaults to 4318.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.otlp.items.properties.use_http.description
Whether this exporter uses HTTP instead of gRPC.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.description
Set here at least the settings for one Prometheus exporter. Each exporter will start a local port that offers metrics to be pulled from KrakenD.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.items.properties.custom_metric_reporting_period.description
Whether you want to override the global `metric_reporting_period` attribute set for all exporters or not. Value in seconds. A missing attribute, or set to `0` means using whatever value was used in `metric_reporting_period` at the global level.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.items.properties.disable_metrics.description
Leave this exporter declared but disabled (useful in development). It won't report any metrics when the flag is `true`.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.items.properties.go_metrics.description
Whether you want fine-grained details of Go language metrics or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.items.properties.listen_ip.description
The IP address that KrakenD listens to in IPv4 or IPv6. You can, for instance, expose the Prometheus metrics only in a private IP address. An empty string, or no declaration means listening on all interfaces. The inclusion of `::` is intended for IPv6 format only (**this is not the port**). Examples of valid addresses are `192.0.2.1` (IPv4), `2001:db8::68` (IPv6). The values `::` and `0.0.0.0` listen to all addresses, which are valid for IPv4 and IPv6 simultaneously.

# properties.exporters.properties.prometheus.items.properties.name.description
A unique name to identify this exporter.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.items.properties.port.description
The port in KrakenD where Prometheus will connect to.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.exporters.properties.prometheus.items.properties.process_metrics.description
Whether this exporter shows detailed metrics about the running process like CPU or memory usage or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.histograms.description
Use an histogram bucket configuration different from the defaults to define the detail of histogram metrics (decrease or increase their size). You don't need to set this attribute unless you want full control of the histogram definition.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.histograms.properties.size_buckets.description
The size of the buckets in bytes you want to use for the histograms.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.histograms.properties.time_buckets.description
The duration of buckets in seconds you want to use for the histograms.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.description
A request and response flow passes through three different layers. This attribute lets you specify what data you want to export in each layer. All layers are enabled by default unless you declare this section.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.description
Reports the activity between KrakenD and each of your backend services. This is the more granular layer.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.detailed_connection.description
Whether you want to enable detailed metrics for the HTTP connection phase or not. Includes times to connect, DNS querying, and the TLS handshake.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.disable_stage.description
Whether to turn off the metrics or not. Setting this to `true` means stop reporting any data.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.read_payload.description
Whether you want to enable metrics for the response reading payload or not (HTTP connection not taken into account).

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.round_trip.description
Whether you want to enable metrics for the actual HTTP request for the backend or not (manipulation not taken into account). This is the time your backend needs to produce a result.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.static_attributes.description
A list of tags or labels you want to associate with these metrics.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.static_attributes.items.properties.key.description
The key, tag, or label name you want to use.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.metrics.properties.static_attributes.items.properties.value.description
The static value you want to assign to this key.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.detailed_connection.description
Whether you want to add detailed trace attributes for the HTTP connection phase or not. Includes times to connect, DNS querying, and the TLS handshake.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.disable_stage.description
Whether to turn off the traces or not. Setting this to `true` means stop reporting any data.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.read_payload.description
Whether you want to add trace attributes for the response reading payload or not (HTTP connection not taken into account).

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.report_headers.description
Whether you want to report the final headers that reached the backend.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.round_trip.description
Whether you want to add trace attributes for the actual HTTP request for the backend or not (manipulation not taken into account). This is the time your backend needs to produce a result.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.static_attributes.description
A list of tags or labels you want to associate to these traces.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.static_attributes.items.properties.key.description
The key, tag, or label name you want to use.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.backend.properties.traces.properties.static_attributes.items.properties.value.description
The static value you want to assign to this key.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.global.properties.disable_metrics.description
Whether you want to disable all metrics happening in the global layer or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.global.properties.disable_propagation.description
Whether you want to ignore previous propagation headers to KrakenD. When the flag is set to `true`, spans from a previous layer will never be linked to the KrakenD trace.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.global.properties.disable_traces.description
Whether you want to disable all traces happening in the global layer or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.global.properties.metrics_static_attributes.description
Static attributes you want to pass for metrics.

# properties.layers.properties.global.properties.metrics_static_attributes.items.properties.key.description
The key of the static attribute you want to send

# properties.layers.properties.global.properties.metrics_static_attributes.items.properties.value.description
The value of the static attribute you want to send

# properties.layers.properties.global.properties.report_headers.description
Whether you want to send all headers that the consumer passed in the request or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.global.properties.semantic_convention.description
The semantic convention naming you want to use. The default is an empty string which uses the original naming convention prior to 1.27. For the semantic convention of 1.27 and higher, use `1.27`

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.global.properties.traces_static_attributes.description
Static attributes you want to pass for traces.

# properties.layers.properties.global.properties.traces_static_attributes.items.properties.key.description
The key of the static attribute you want to send

# properties.layers.properties.global.properties.traces_static_attributes.items.properties.value.description
The value of the static attribute you want to send

# properties.layers.properties.proxy.description
Reports the activity at the beginning of the proxy layer, including spawning the required requests to multiple backends, merging, endpoint transformation and any other internals of the proxy between the request processing and the backend communication

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.proxy.properties.disable_metrics.description
Whether you want to disable all metrics happening in the proxy layer or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.proxy.properties.disable_traces.description
Whether you want to disable all traces happening in the proxy layer or not.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.proxy.properties.metrics_static_attributes.description
Static attributes you want to pass for metrics.

# properties.layers.properties.proxy.properties.metrics_static_attributes.items.properties.key.description
The key of the static attribute you want to send

# properties.layers.properties.proxy.properties.metrics_static_attributes.items.properties.value.description
The value of the static attribute you want to send

# properties.layers.properties.proxy.properties.report_headers.description
Whether you want to report all headers that passed from the request to the proxy layer (`input_headers` policy in the endpoint plus KrakenD's headers).

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.layers.properties.proxy.properties.traces_static_attributes.description
Static attributes you want to pass for traces.

# properties.layers.properties.proxy.properties.traces_static_attributes.items.properties.key.description
The key of the static attribute you want to send

# properties.layers.properties.proxy.properties.traces_static_attributes.items.properties.value.description
The value of the static attribute you want to send

# properties.metric_reporting_period.description
How often you want to report and flush the metrics in seconds. This setting is only used by `otlp` exporters.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.service_name.description
A friendly name identifying metrics reported by this installation. When unset, it uses the `name` attribute in the root level of the configuration.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.service_version.description
The version you are deploying, this can be useful for deployment tracking.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.skip_paths.description
The paths you don't want to report. Use the literal value used in the `endpoint` definition, including any `{placeholders}`. In the `global` layer, this attribute works only on metrics, because traces are initiated before there is an endpoint to match against. If you do not want any path skipped, just add an array with an empty string `[""]`.

See: https://www.krakend.io/docs/telemetry/opentelemetry/

# properties.trace_sample_rate.description
The sample rate for traces defines the percentage of reported traces. This option is key to reduce the amount of data generated (and resource usage), while you still can debug and troubleshoot issues. For instance, a number of `0.25` will report a 25% of the traces seen in the system.

See: https://www.krakend.io/docs/telemetry/opentelemetry/