You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Index labels: Resource attributes map well to index labels in Loki, since both usually identify the source of the logs. Because Loki has a limit of 30 index labels, we have selected the following resource attributes to be stored as index labels, while the remaining attributes are stored as [Structured Metadata]({{< relref "../../get-started/labels/structured-metadata" >}}) with each log entry:
- cloud.availability_zone
- cloud.region
- container.name
- deployment.environment
- k8s.cluster.name
- k8s.container.name
- k8s.cronjob.name
- k8s.daemonset.name
- k8s.deployment.name
- k8s.job.name
- k8s.namespace.name
- k8s.pod.name
- k8s.replicaset.name
- k8s.statefulset.name
- service.instance.id
- service.name
- service.namespace
To Reproduce
Steps to reproduce the behavior:
Read the docs
Expected behavior
The count of attributes and labels match.
- Index labels: Resource attributes map well to index labels in Loki, since both usually identify the source of the logs. Because Loki has a limit of 30 index labels, we have selected the following resource attributes to be stored as index labels, while the remaining attributes are stored as [Structured Metadata]({{< relref "../../get-started/labels/structured-metadata" >}}) with each log entry:
Describe the bug
The count of OTel attributes to index (17) and the default label limit (15) do not match:
loki/docs/sources/shared/configuration.md
Lines 2008 to 2011 in 19fef93
loki/docs/sources/shared/configuration.md
Lines 2896 to 2898 in 19fef93
The 17 OTel resource attributes are also listed in the docs, which mentions the old default limit (
max_label_names_per_series: 30
):loki/docs/sources/send-data/otel/_index.md
Lines 75 to 92 in 19fef93
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The count of attributes and labels match.
Environment:
Screenshots, Promtail config, or terminal output
Comment
I would have created a PR to fix the docs, but I suspect this might lead to a default config change?
The text was updated successfully, but these errors were encountered: