Tempo Bundle
- By Canonical Observability | bundle
| Channel | Revision | Published |
|---|---|---|
| latest/edge | 1 | 30 Jul 2024 |
juju deploy tempo-bundle --channel edge
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
-
always_enable_jaeger_grpc | boolean
Force-enable the receiver for the 'jaeger_grpc' protocol in Tempo, even if there is no integration currently requesting it.
-
always_enable_jaeger_thrift_http | boolean
Force-enable the receiver for the 'jaeger_thrift_http' protocol in Tempo, even if there is no integration currently requesting it.
-
always_enable_otlp_grpc | boolean
Force-enable the receiver for the 'otlp_grpc' protocol in Tempo, even if there is no integration currently requesting it.
-
always_enable_otlp_http | boolean
Force-enable the receiver for the 'otlp_http' protocol in Tempo, even if there is no integration currently requesting it.
-
always_enable_zipkin | boolean
Force-enable the receiver for the 'zipkin' protocol in Tempo, even if there is no integration currently requesting it.
-
cpu_limit | string
K8s cpu resource limit, e.g. "1" or "500m". Default is unset (no limit). This value is used for the "limits" portion of the resource requirements. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
-
memory_limit | string
K8s memory resource limit, e.g. "1Gi". Default is unset (no limit). This value is used for the "limits" portion of the resource requirements. See https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
-
retention-period | int
Default: 720
Maximum trace retention period, in hours. This will be used to configure the compactor to clean up trace data after this time. Defaults to 720 hours, which is equivalent to 30 days. Per-stream retention limits are currently not supported.