Add dedicated buffering module

[cforce]

Component(s)

No response

Is your feature request related to a problem? Please describe.

Currently, OpenTelemetry (Android) does not have a dedicated buffering module. This feature would be highly useful in scenarios where telemetry data cannot be immediately exported (e.g., due to network outages, app backgrounding, or battery optimization).

A buffering module (similar to what exists in opentelemetry-disk-buffering)

io.opentelemetry.contrib opentelemetry-disk-buffering 1.36.0-alpha runtime

would allow telemetry data to be persisted temporarily (e.g., on disk or in memory) and exported later once the system conditions allow it.

Motivation / Use Cases:

• Ensure telemetry data is not lost during intermittent connectivity.
• Improve reliability in mobile environments where background restrictions frequently interrupt telemetry export.
• Enable developers to configure buffer size, flush intervals, and persistence strategy (disk vs. memory).

Describe the solution you'd like

• Introduce a disk-buffering a option / module which can be used in opentelemetry-android.

• Reuse concepts and implementation patterns from existing buffering modules.

• Allow configurable storage backends (eg in-memory, file-based, SQLite).

• Related discussion: [open-telemetry/opentelemetry-android#1103](Support multiple independent rum instances opentelemetry-android#1103)

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[breedx-splk]

Wait, @cforce I think I might have misunderstood your question in open-telemetry/opentelemetry-android#1103 (comment). How does the thing you're asking for here actually differ from the disk-buffering module in this repo? I think what you're asking for is basically the same thing that exists already (with a few features like storage backend choice not fully implemented).

Or maybe you'd like to see disk-buffering just renamed to data-buffering or something?

[github-actions]

This has been automatically marked as stale because it has been marked as needing author feedback and has not had any activity for 7 days. It will be closed automatically if there is no response from the author within 7 additional days from this comment.

[cforce]

Can you contribute some test/example how to use it in android with any storage backend? There are none -are there?

[breedx-splk]

Can you contribute some test/example how to use it in android with any storage backend? There are none -are there?

No, because this is a work in progress. Please have a look at #2183 and the SignalStorage interface.

Once this work is done, it should be possible to plug in alternative (non-file-based) storage mechanisms...which I think is what you're after. Maybe a database or something else? Unclear.