During March 2025, Harsha Reddy enhanced the zitadel/zitadel repository by implementing a configurable service name for metrics and tracing, addressing the need for improved observability and deployment flexibility. Using Go and YAML, Harsha introduced a configuration option that allows each Zitadel instance to specify its own service name, supporting multi-tenant and environment-specific deployments while maintaining backward compatibility by defaulting to 'ZITADEL' when not set. This backend development work aligned metrics and tracing nomenclature with deployment configurations, enabling clearer correlation across environments. The feature deepened Zitadel’s observability readiness and streamlined configuration management without introducing breaking changes or regressions.