From 307ad6d5264f5b639438421c7f943053783e6f0a Mon Sep 17 00:00:00 2001 From: Julie Stickler Date: Mon, 16 Dec 2024 09:52:58 -0500 Subject: [PATCH] review comments --- docs/sources/get-started/labels/_index.md | 3 +-- docs/sources/get-started/labels/cardinality.md | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/sources/get-started/labels/_index.md b/docs/sources/get-started/labels/_index.md index 4a07feae12b31..a9f11347448c1 100644 --- a/docs/sources/get-started/labels/_index.md +++ b/docs/sources/get-started/labels/_index.md @@ -25,7 +25,6 @@ A label is a key-value pair, for example all of the following are labels: - deployment_environment = development - host = server-1 -- pod_name = myapp-abcdef - cloud_region = us-west-1 - service_namespace = grafana-server @@ -99,7 +98,7 @@ Because Loki has a default limit of 15 index labels, we recommend storing only s For Grafana Cloud Logs, see the [current OpenTelemetry guidance](https://grafana.com/docs/grafana-cloud/send-data/otlp/otlp-format-considerations/#logs). {{< /admonition >}} -The default list of Resource Attributes to store as labels can be configured using `default_resource_attributes_as_index_labels` under the [distributor's otlp_config](https://grafana.com/docs/loki//configure/#distributor). If you are using Grafana Cloud, contact support to configure this setting. +The default list of Resource Attributes to store as labels can be configured using `default_resource_attributes_as_index_labels` under the [distributor's otlp_config](https://grafana.com/docs/loki//configure/#distributor). You can set global limits using [limits_config.otlp_config](/docs/loki//configure/#limits_config). If you are using Grafana Cloud, contact support to configure this setting. ## Labeling is iterative diff --git a/docs/sources/get-started/labels/cardinality.md b/docs/sources/get-started/labels/cardinality.md index 1b59fbdd07bfa..e3f2e56b1d98f 100644 --- a/docs/sources/get-started/labels/cardinality.md +++ b/docs/sources/get-started/labels/cardinality.md @@ -43,7 +43,7 @@ To avoid high cardinality in Loki, you should: - Avoid assigning labels with unbounded values, for example timestamp, trace ID, order ID. - Prefer static labels that describe the origin or context of the log message, for example, application, namespace, environment. -- Don't assign "dynamic" labels, which are values from the log message itself, unless it is low-cardinality, or a long-lived value +- Don't assign "dynamic" labels, which are values from the log message itself, unless it is low-cardinality, or a long-lived value. - Use structured metadata to store frequently-searched, high-cardinality metadata fields, such as customer IDs or transaction IDs, without impacting Loki's index. {{< admonition type="note" >}}