How to use service.name resource attribute since the 0.20.0 release ?

[fungiboletus]

Hei,

Since the 0.20.0 release and the pull request #2227 it seems that serviceName is deprecated and we should use service.name instead. I havn't easily found this information in the changelog, it did require some digging to understand why the service name was now a very long unknown_service:/path/to/node. Documentation says Use service.name Resource attribute instead. but it wasn't about replacing serviceName: 'toto' by service: { name: 'toto'}.

So how to use service.name resource attribute ?

[julien-sugg]

Hi,

You may be able to define it when instantiating your trace provider.

e.g.:

import { ResourceAttributes } from '@opentelemetry/semantic-conventions';
import { Resource } from '@opentelemetry/resources';
// ...other imports

// ...code

const tracerProvider = new WebTracerProvider( {
  resource: new Resource( {
    [ ResourceAttributes.SERVICE_NAME ]: "yourServiceName",
  } )
} );

// ...code

[fungiboletus]

Thanks ! It works.

[gamblea]

This was very helpful and fixed my issue! I was running into the same issue when running a node.js project locally. I was unable to pass the Semantic Attributes through an env variable on macOS.

Thank you @julien-sugg

Just wondering if there are limitations with passing Semantic Attributes through environment variables right now?