Datadog - Best practives for naming services

Monitoring and Observability Datadog
#1

I had a best practices question. Currently we have our Services in :datadog: named like prefix-develop-some-api, prefix-staging-some-api, and prefix-prod-some-api which lines up with how they are named in our cloud infrastructure. But it seems like the service catalog encourages you to almost name it just prefix-some-api and use the environmental discriminator to carve up how you view it.

Is there a recommended direction to take one way or another?

#2

Likely relevant https://docs.datadoghq.com/getting_started/tagging/unified_service_tagging/?tab=kubernetes

> Unified service tagging ties Datadog telemetry together by using three reserved tags: env, service, and version.
I’m curious why there’s a prefix in the service name - what is that?

#3

The prefix is just part of our cloud naming convention. like utility-develop-some-function