However, we recommend importing files with side effects using `require` from within your `register` function instead. The following example demonstrates a basic usage of `require` in a `register` function:
However, we recommend importing files with side effects using `import` from within your `register` function instead. The following example demonstrates a basic usage of `import` in a `register` function:
```ts
```ts
// /instrumentation.ts
// /instrumentation.ts
exportfunctionregister(){
exportasyncfunctionregister(){
require('package-with-side-effect')
awaitimport('package-with-side-effect')
}
}
```
```
By doing this, you can colocate all of your side effects in one place in your code, and avoid any unintended consequences from importing files.
By doing this, you can colocate all of your side effects in one place in your code, and avoid any unintended consequences from importing files.
We call `register` in all environments, so it's necessary to conditionally require any code that doesn't support both `edge` and `nodejs`. You can use the environment variable `NEXT_RUNTIME` to get the current environment. Importing an environment-specific code would look like this:
We call `register` in all environments, so it's necessary to conditionally import any code that doesn't support both `edge` and `nodejs`. You can use the environment variable `NEXT_RUNTIME` to get the current environment. Importing an environment-specific code would look like this:
Now you can initialize `NodeSDK` in your `instrumentation.ts`.
Now you can initialize `NodeSDK` in your `instrumentation.ts`.
OpenTelemetry APIs are not compatible with edge runtime, so you need to make sure that you are importing them only when `process.env.NEXT_RUNTIME === 'nodejs'`. Conditionally importing with an `require` doesn't play well with typescript. We recommend using a conditionally `require`ing new file `instrumentation.node.ts` which can use normal `import`s:
OpenTelemetry APIs are not compatible with edge runtime, so you need to make sure that you are importing them only when `process.env.NEXT_RUNTIME === 'nodejs'`. We recommend creating a new file `instrumentation.node.ts` which you conditionally import only when using node:
```ts
```ts
// instrumentation.ts
// instrumentation.ts
exportfunctionregister(){
exportasyncfunctionregister(){
if(process.env.NEXT_RUNTIME==='nodejs'){
if(process.env.NEXT_RUNTIME==='nodejs'){
require('./instrumentation.node.ts')
awaitimport('./instrumentation.node.ts')
}
}
}
}
```
```
...
@@ -90,7 +90,7 @@ sdk.start()
...
@@ -90,7 +90,7 @@ sdk.start()
```
```
Doing this is equivalent to using `@vercel/otel`, but it's possible to modify and extend.
Doing this is equivalent to using `@vercel/otel`, but it's possible to modify and extend.
For example, you could use `@opentelemetry/exporter-trace-otlp-grpc` instead of `@opentelemetry/exporter-trace-otlp-http`.
For example, you could use `@opentelemetry/exporter-trace-otlp-grpc` instead of `@opentelemetry/exporter-trace-otlp-http` or you can specify more resource attributes.