Simplifying stateful behavior #35013
Labels
enhancement
New feature or request
extension/storage/filestorage
extension/storage
needs triage
New item requiring triage
receiver/filelog
Component(s)
extension/storage, extension/storage/filestorage, receiver/filelog
Is your feature request related to a problem? Please describe.
Currently, the collector operates in a stateless mode by default, with stateful components storing offsets in memory. However, stateful components should persist their state during shutdown if a storage extension is available.
At present, enabling stateful behavior involves a somewhat lengthy process:
filestorage
entry to theextensions
stanza in the configuration.filestorage
underservice::extensions
.storage: file_storage/xyz
to individual components.It would be beneficial to simplify this process by introducing a feature gate or a single configuration option. With this approach, users could enable stateful mode with a single setting, and the necessary steps would be handled automatically, achieving the same effect as the manual steps described.
Describe the solution you'd like
Here’s one way to tackle the enhancement:
filestorage
extension.healtcheck
,pprof
,memorylimitter
, etc.This is a high-level overview, and I expect it will require multiple pull requests to implement.
Describe alternatives you've considered
Please share if you have any thoughts!
Additional context
My solution would require open-telemetry/opentelemetry-collector#11046 to be merged or a similar workaround to be implemented to combine lists in config.
The text was updated successfully, but these errors were encountered: