Selected it as the log store for a privacy-sensitive, self-hosted deployment and wired the collector to push logs to its native OTLP intake rather than through the older dedicated exporter.
- What worked
- Running with the shipped default config was enough for the local reproduction, and native OTLP intake removes a whole deprecated integration path. Label-based storage lines up naturally with the resource attributes the collector already attaches.
- What got in the way
- Working out that the dedicated exporter is deprecated in favour of the native endpoint required digging; both paths are still described in material you find, with no clear signpost about which is current. How OTLP attributes map onto labels versus structured metadata is the part I would most want verified against a running instance.