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
[exporterhelper] Preserve client metadata in the persistent queue (#13220)
Preserve client metadata key values in persistent queue.
It allows request client metadata to propagate through the persistent
queue used by the exporters. The same way as it's done for the in-memory
queue. Currently, it is behind the exporter.PersistRequestContext
feature gate, which can be enabled by adding
`--feature-gates=exporter.PersistRequestContext` to the collector
command line. An exporter buffer stored by a previous version of the
collector (or by a collector with the feature gate disabled) can be read
by a newer collector with the feature enabled. However, the reverse is
not supported: a buffer stored by a newer collector with the feature
enabled cannot be read by an older collector (or by a collector with the
feature gate disabled).
Resolves#10110,
#11780
and
open-telemetry/opentelemetry-collector-contrib#38666
Follow-up work:
To fully propagate the client context, we also add support for
serializing remaining `client.Client` fields:
```
Addr net.Addr
Auth AuthData
```
Then, we probably want to make this configurable or rely on the
transform processor to be able to manipulate the context
0 commit comments