Skip to content

Instrumentation api change - option 2#1540

Draft
LikeTheSalad wants to merge 3 commits intoopen-telemetry:mainfrom
LikeTheSalad:inst-api-change-option2
Draft

Instrumentation api change - option 2#1540
LikeTheSalad wants to merge 3 commits intoopen-telemetry:mainfrom
LikeTheSalad:inst-api-change-option2

Conversation

@LikeTheSalad
Copy link
Copy Markdown
Contributor

@LikeTheSalad LikeTheSalad commented Jan 26, 2026

DO NOT MERGE

This is a proposal for this issue: #1541 - It's meant to highlight the key changes, without addressing potential compilation errors, if any. If chosen as the approach we'd like to go with, then I'll add the rest of the changes needed for the build to pass.

@LikeTheSalad LikeTheSalad force-pushed the inst-api-change-option2 branch from 4434e68 to 8e2b406 Compare January 26, 2026 15:39
Copy link
Copy Markdown
Member

@fractalwrench fractalwrench left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment on #1539 applies to this PR too: https://github.com/open-telemetry/opentelemetry-android/pull/1539/changes#r2730782298

Basically: does it make sense to expose this functionality for only the log record signals, or consider exposing a way to orderly shutdown the SDK as a whole?

I'd also suggest that we don't necessarily need to expose this as part of the public API, with a few internal changes. OpenTelemetryRum could set its own UncaughtExceptionHandler separate from the crash instrumentation and shutdown signal collection in an orderly manner, without needing to provide a public API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants