Use environment variables to configure the Datadog client #187
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
etiennep
force-pushed
the
client-env-vars
branch
from
321b909 to
8b1e6eb
Compare
etiennep
force-pushed
the
client-env-vars
branch
from
8b1e6eb to
e534db4
Compare
ABHINAV-SUREKA
approved these changes
Mar 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce functionality to configure the Datadog client using environment variables, allowing for more flexible deployment options. Include tests to verify the correct behavior of address resolution based on these variables.
The following environment variables are now supported:
STATSD_HOSTSTATSD_UDP_PORTSTATSD_SOCKET