Cannot put traceid & spanid like loki labes

[RaulGF92]

Component(s)

exporter/loki

Describe the issue you're reporting

Previous PR related:

• [exporter/loki] Use record attributes as log labels #7569
• How do I pass the trace ID collected from OTLP to Loki? #29079

Really I don't know if is a error or really that is solved and we can put traceid like labels but sure documentation is not well explained and a refactor of this could be beneficial.

Explanation of my stack:

I have a full open-telemetry stack

When I tried to send my logs that works but I want to put traceid & spanid in my loki.labels for work in a raw format and put the labels I want to search without fight with json format.

That is my configuration otel-configuration (I remove all aditional configuration for free space):

receivers:
  otlp:
    protocols:
      grpc:
      http:

exporters:
  loki:
    endpoint: http://loki:3100/loki/api/v1/push
    tls:
      insecure: true
    default_labels_enabled:
      exporter: false
      job: true

processors:
  attributes:
    actions:
      - action: insert
        key: loki.format
        value: json
      - action: insert
        key: loki.attribute.labels
        value: traceid
  resource:
    attributes:
      - action: insert
        key: loki.resource.labels
        value: record.traceid


service:
  pipelines:
    logs:
      receivers:  [ otlp ]
      processors: [ attributes, resource]
      exporters:  [ loki ]

That error happen in all formats (json, raw, logfmt) when you tried to put traceid like a label that don't let you also loki don't see this like a label:

[github-actions]

Pinging code owners:

• exporter/loki: @gramidt @gouthamve @jpkrohling @mar4uk

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

Loki labels are indexed and should be kept to low-cardinality attributes. Trace ID and Span ID aren't a good fit for this, which is why they are placed in the body instead. This means that you can still query for them after parsing the body (with json or logfmt parsers), but you'd need to reduce the amount of data being queries by first using a low-cardinality value from a label, like service name.