DD_SERVICE not being read by the agent for Unified Service Tagging

[agrobbin]

I'm trying to determine why things like host metrics and DB monitoring are not connecting to our APM services, and my hunch is that it's because the service tag is not being set in the Agent's main configuration file, like mentioned here.

This surprised me, as we have set the DD_SERVICE environment variable on our Heroku apps, and at least for our host metrics, the related env tag is being set, I think because of this tag configuration (which will look at DD_ENV).

What I'm surprised about is DD_SERVICE not being respected. It'd be great if there was some documentation on how best to set this up in a Heroku environment, to take advantaged of Unified Service Tagging.

Any help would be appreciated, thanks so much!

[easherma-truth]

+1

[arapulido]

Thanks for raising this! I will have a look to this soon

[arapulido]

Hello both! I cannot reproduce this issue, but it might be related to the type of tracer. What tracer are you using?

[agrobbin]

I'm so sorry for my delay in responding here @arapulido! Your post got lost in my inbox. We are running dd-trace-rb (v1.23.3), and AFAICT, are still running up against this issue. We worked around it by explicitly setting DD_TAGS to include the service tag in our prerun.sh file