There is no way to set the `service.name` attribute in code about hs-opentelemetry

[Profpatsch]

Depending on timing issues across applications it looks like you could accidentally pickup the new service name in another process running on the same machine?

setEnv modifies the process-internal environment mapping.
Only the process and any children should see the new variable name.

[parsonsmatt]

Another way that end users can work-around this is by using setEnv.

withOtelServiceName :: String -> IO a -> IO a
withOtelServiceName newName action =
  -- use bracket to restore the old service name
  bracket (lookupEnv "OTEL_SERVICE_NAME") (setEnv "OTEL_SERVICE_NAME" . fromMaybe "") $ \maybeOldName -> do
    setEnv "OTEL_SERVICE_NAME" newName
    action

withOtelServiceName "my.cool.service" $ do
  -- initialize the service normally

[solomon-b]

Nice workaround @parsonsmatt.

Depending on timing issues across applications it looks like you could accidentally pickup the new service name in another process running on the same machine?

[Profpatsch]

@parsonsmatt the bracket is a bit misleading here, because the environment gets set process-wide, meaning it’s not lexically scoped. Just setting it should be fine, since it will be dropped automatically when ending the process.

[solomon-b]

Great, I'll make this as closed for now.