Skip to content

Commit

Permalink
chore: [release-2.9.x] docs: fix formatting in structured metadata to…
Browse files Browse the repository at this point in the history
…pic (#12383)

Co-authored-by: J Stickler <[email protected]>
  • Loading branch information
grafanabot and JStickler authored Mar 27, 2024
1 parent e4f2258 commit dc48977
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/sources/get-started/labels/structured-metadata.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ Structured metadata can also be used to query commonly needed metadata from log

You should only use structured metadata in the following situations:

If you are ingesting data in OpenTelemetry format, using the Grafana Agent or an OpenTelemetry Collector. Structured metadata was designed to support native ingestion of OpenTelemetry data.
If you have high cardinality metadata that should not be used as a label and does not exist in the log line. Some examples might include `process_id` or `thread_id` or Kubernetes pod names.
- If you are ingesting data in OpenTelemetry format, using the Grafana Agent or an OpenTelemetry Collector. Structured metadata was designed to support native ingestion of OpenTelemetry data.
- If you have high cardinality metadata that should not be used as a label and does not exist in the log line. Some examples might include `process_id` or `thread_id` or Kubernetes pod names.

It is an antipattern to extract information that already exists in your log lines and put it into structured metadata.

Expand Down

0 comments on commit dc48977

Please sign in to comment.