🚧 This project is currently Experimental. Do not use it in production environments.
This library lets you autoinstrument React Native applications. Minimum supported React Native version is 0.68. To instrument applications running on React Native versions lower than 0.68, see Instrument lower versions.
To instrument your React Native application, follow these steps.
- Install the library using either npm or yarn:
# npm
npm install @hyperdx/otel-react-native
# yarn
yarn add @hyperdx/otel-react-native
- Initialize the library as early in your app lifecycle as possible:
import { HyperDXRum } from '@hyperdx/otel-react-native';
HyperDXRum.init({
service: 'my-rn-app',
apiKey: '<YOUR_API_KEY_HERE>',
tracePropagationTargets: [/api.myapp.domain/i], // Set to link traces from frontend to backend requests
networkHeadersCapture: false,
});
- Customize the initialization parameters to specify:
-
apiKey
: Your HyperDX Ingestion API key. You can find it here. -
service
: Name of your application. Set it to distinguish your app from others in HyperDX. -
tracePropagationTargets
: A list of regular expressions that match the URLs of your backend services. Set it to link traces from frontend to backend requests. -
networkHeadersCapture
: networkHeadersCapture is a flag that allows the option to capture header information, with the default flag being false.
Attaching user information will allow you to search/filter sessions and events in HyperDX. This can be called at any point during the client session. The current client session and all events sent after the call will be associated with the user information.
userEmail
, userName
, and teamName
will populate the sessions UI with the corresponding values, but can be omitted. Any other additional values can be specified and used to search for events.
HyperDXRum.setGlobalAttributes({
userEmail: user.email,
userName: user.name,
teamName: user.team.name,
// Other custom properties...
});
To instrument applications running on React Native versions lower than 0.68, edit your metro.config.js
file to force metro to use browser specific packages. For example:
const defaultResolver = require('metro-resolver');
module.exports = {
resolver: {
resolveRequest: (context, realModuleName, platform, moduleName) => {
const resolved = defaultResolver.resolve(
{
...context,
resolveRequest: null,
},
moduleName,
platform
);
if (
resolved.type === 'sourceFile' &&
resolved.filePath.includes('@opentelemetry')
) {
resolved.filePath = resolved.filePath.replace(
'platform\\node',
'platform\\browser'
);
return resolved;
}
return resolved;
},
},
transformer: {
getTransformOptions: async () => ({
transform: {
experimentalImportSupport: false,
inlineRequires: true,
},
}),
},
};
react-navigation version 5 and 6 are supported.
The following example shows how to instrument navigation:
import { startNavigationTracking } from '@hyperdx/otel-react-native';
export default function App() {
const navigationRef = useNavigationContainerRef();
return (
<NavigationContainer
ref={navigationRef}
onReady={() => {
startNavigationTracking(navigationRef);
}}
>
<Stack.Navigator>...</Stack.Navigator>
</NavigationContainer>
);
}
The library exports data using the Zipkin exporter. Adding your own exporters and processors isn't supported yet.
Supported features:
- Autoinstrumented HTTP requests
- Autoinstrumented JS Error tracking
- Autoinstrumented navigation tracking for react-navigation
- Session tracking
- Custom instrumentation using Opentelemetry
- Capturing native crashes
For more information about how this library uses Opentelemetry and about future plans check CONTRIBUTING.md.
https://github.com/signalfx/splunk-otel-react-native#license