-
I noticed that #2387 was recently merged, and I'm wondering what impact this'll have on the Is the purpose of this change to simplify the dd-trace-js codebase a bit, or does it actually introduce / change some functionality? Here's how i've got DD_PROFILING_ENABLED=true
DD_LOGS_INJECTION=true
DD_RUNTIME_METRICS_ENABLED=true
DD_ENV=<something>
DD_SERVICE=<something>
DD_VERSION=<something>
DD_ENTITY_ID=<something>
DD_AGENT_HOST=<something> import tracer from 'dd-trace';
tracer.init({ tags: { owner: '<something>' } });
tracer.use('express', {
blocklist: ['/liveness', '/api/liveness'],
});
export default tracer; |
Beta Was this translation helpful? Give feedback.
Answered by
rochdev
Oct 26, 2022
Replies: 1 comment 3 replies
-
This change allows us to support additional features like reporting metrics over UDS. It does fallback to DogStatsD over UDP when the endpoint is not available on the agent because the version installed is too old so it shouldn't make any difference for an existing service. |
Beta Was this translation helpful? Give feedback.
3 replies
Answer selected by
janeklb
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This change allows us to support additional features like reporting metrics over UDS. It does fallback to DogStatsD over UDP when the endpoint is not available on the agent because the version installed is too old so it shouldn't make any difference for an existing service.