feat(instrumentation-react-native-navigation): Adding new instrumentation library to track navigation changes for React Native apps

[facostaembrace]

Which problem is this PR solving?

A couple of months ago, my team (Embrace) and I were looking for an instrumentation library that creates telemetry data for React Native applications. However, we noticed there was nothing available that adhered to open source standards. We also noticed people in Stack Overflow was asking about something similar.
This instrumentation library exposes two components that can be implemented at the root of React Native applications to create telemetry data that tracks navigation changes for the most popular navigation approaches in this environment.
Instrumentation request here.

#1089

Short description of the changes

• Introduce a new instrumentation library to kick off a React Native ecosystem.
• Exposes two components: <NativeNavigationTracker /> that creates spans and track navigation changes for wix/react-native-navigation library, and <NavigationTracker /> that is meant to be used when the application handles the navigation using @react-navigation/native or expo-router.
• Both components have the ability of adding a minimum set of configurations.
• Both components receives a custom provider, but if it is not passed it can also create telemetry data using the global one.
• Configuration for both allows to add static attributes for spans.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: facostaembrace / name: Florencia Acosta (36d0e1d, f6a696e, 4c06c41, 197db51, 907a0d5, 0586cc0, f3ae613, 8ce7abb, eea8205, d22d280, 0a6b4a0, a7265bf, 9227be9, c47c8c1, 7042067, fa5aae4, 883296f, ab87452, 8716b2a, d75cb7f, fc36c13, 54b1463, 0beb3a3, 989db3e, 560152a, 4f0c944, 4104534, da4d57f, 20cc353, 1d3d287, d8830b3, 201d182, f081191, 559eae1, a671951, 51ad05f, e50ee23, 44918a6, 787a10b, fc7e131, be802f6, 6847592, 59334fc, b06128d, 2bc96b9, 02a52fa, 55cce59, b6e3cf8, 7938a24)

[facostaembrace]

Fyi: still pending to submit the Instrumentation request that introduces this initiative.
Update: done (request here)

[facostaembrace]

So @facostaembrace - do you need another maintainer here to get this reviewed? If so I volunteer to help maintain this with you.

Hi @kndri ! I think I already have maintainers for this new package but all help is well received!
What I need now is an admin approving the workflows for running once again and then hitting the merge button.
But for sure you can take a look and provide feedback if you want!

Thanks for the interest!!

[JamieDanielson]

We'd like to help keep this moving forward, and want to give you more leeway especially as this is 0.1.0 and it will be valuable to get feedback on how this works. This is the top requested feature in js-contrib.

@facostaembrace @jpmunz we'd like to add you to a triagers team and set a specific path in the CODEOWNERS path for you. We are working on this for other packages as well to ensure folks are pinged and assigned appropriately, as well as given the power to approve PRs (with the green check). To do this we need you to join the OpenTelemetry org.

I am working on some updated guidelines to add to the repo, but in the meantime please follow these guidelines in the community repo for member requirements.

[facostaembrace]

@JamieDanielson I see in the Issue's template that I should mention two sponsors that "meet the sponsor requirements listed in the community membership guidelines". Am right assuming I can tag you + one person from the regular JS SIG meeting? (we can also discuss about this during tomorrow's meeting). Thanks!

[pichlermarc]

is this used anywhere? 🤔

[pichlermarc]

I think it would be great to have a disclaimer here that react native is not fully supported yet by OTel JS.
I also wonder if we should add some build instructions. There are some caveats with things that currently don't work and there's no process in place to test if changes work in the core repo which may be something we should look into soon in order to give everyone a good experience.

[pichlermarc]

I don't think that's applicable here 🙂

Suggested change

"nodejs",

[pichlermarc]

can also be removed 🙂

Suggested change

"profiling",

[dyladan]

Hello there. sorry this has gone so long, but part of the problem is that client instrumentation is in a state of flux in otel, so nobody really knows what to do with it. There is a new startup sig for browser based instrumentation, which I would expect to be very similar to react native from a requirements and modeling perspective. It might be good to get their read on this instrumentation.