How to configure the OpenTelemetry service name?

[mlafreniere-mx]

We deploy Permify in Kubernetes as part of a centralized authorization service, and our observability stack uses Datadog via an OpenTelemetry Collector.

We'd like to customize the service.name resource attribute on traces and metrics exported by Permify (e.g. to authorization-api instead of permify), but setting OTEL_SERVICE_NAME or
OTEL_RESOURCE_ATTRIBUTES doesn't seem to have any effect — the traces still show up as permify.

Is there a supported way to override the service name today? For example:

• A config option under tracer: / meter:?
• An environment variable we might be missing?

Thanks !

[omer-topal]

Hi @mlafreniere-mx , at the moment, Permify doesn’t support overriding the OpenTelemetry service.name from config or env vars. It’s currently set to permify in code, so OTEL_SERVICE_NAME or OTEL_RESOURCE_ATTRIBUTES won’t change it.

I’m tagging this as a feature request so we can track it here. As a possible workaround, you can rewrite service.name in the OpenTelemetry Collector before exporting it.

[mlafreniere-mx]

@omer-topal thanks for the reply. Would this be a good "first issue" that I could tackle ?

[omer-topal]

Sure, feel free to open a PR for it.

The safer approach would be to add an explicit Permify config for overriding service.name, while keeping the default as permify for backward compatibility, instead of changing the current behavior around OTEL_SERVICE_NAME and OTEL_RESOURCE_ATTRIBUTES.