Android: Distributed tracing for RN (cross-thread)

Open
#9 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, java, javascript, kotlin, react-native
Domain
mobile, observability

Research direction

Start with the linked context propagation specification and the referenced OpenTelemetry Java and JavaScript context APIs. Trace how this React Native Android project currently crosses the JS and native boundary, then define the integration points for automatic context sharing. Done means JS and native telemetry retain the correct context across threads, with verification added for the supported paths.

Written by the indexing model from the issue text.

Description

help wanted

Describe the feature

We want to provide an automatic way of context sharing between JS and Native. No matter where you collect your telemetry, it will be correctly marked for you.

Spec: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md

JS:
https://opentelemetry.io/docs/languages/js/propagation/
https://github.com/open-telemetry/opentelemetry-js/blob/main/api/src/context/types.ts#L49

Java:
https://opentelemetry.io/docs/languages/java/api/#context-api

https://github.com/open-telemetry/opentelemetry-java/blob/f17b8b0414eeaf3f6bf8558f1da0ef462997c99e/context/src/main/java/io/opentelemetry/context/Context.java#L88

https://github.com/open-telemetry/opentelemetry-java/blob/b468a2e9bf0f3e46b5c18c1fcf038f387ad5ed1b/context/src/main/java/io/opentelemetry/context/ContextStorage.java#L63

Motivation

Effortless context sharing between JS and Native contexts.

Related Issues

Dominant language
Kotlin
Stars
58
Forks
2
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstack/react-native-open-telemetry

All issues in callstack/react-native-open-telemetry

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.