feat: O11Y-576 / O11Y-544 - Added disk buffering to cache signals

[agrognetti]

Summary

A DiskBufferingCache was set on OtelRumConfig to cache signals (metrics, traces, logs) and avoid data loss when the Android client has no connection.

CustomSampler: The log sampling logic was fixed to avoid continuing to evaluate a log in search of a match when the config severityText or message are not null but the log severityText or message values are null.

How did you test this change?

Unit tests

Are there any deployment considerations?

No

---

Note

Enables disk buffering in Otel RUM config and updates log sampling to not match when message/severity are absent, with tests and e2e test harness support.

• Observability SDK (Android)
  • Enable disk buffering via OtelRumConfig.setDiskBufferingConfig(DiskBufferingConfig.create(...)), toggled by isAnySignalEnabled(options) and options.debug.
  • Add helper isAnySignalEnabled and minor formatting cleanup.
• Sampling
  • Tighten CustomSampler.matchesLogConfig to treat missing severityText/message as non-matches.
  • Update tests to cover non-match cases for null or mismatched message/severity and rename one test for clarity.
• E2E Test App
  • Add dependency io.opentelemetry.android:core and call SignalFromDiskExporter.resetForTesting() in TestApplication.onTerminate() to support disk buffering tests.

^{Written by Cursor Bugbot for commit ad1b187. This will update automatically on new commits. Configure here.}