-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Allow Datadog integration to be disabled #323
Conversation
7ff40c3
to
5650ffd
Compare
7c6254c
to
4107e0a
Compare
4107e0a
to
0a15fcc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't see big value in introducing this handling, if datadog must be disabled env vars can be not set or empty - simply. If Datadog not needed in the project, then must be removed from dependency.
@LinMAD The environment variable allows for deliberate control over the library rather than relying on "bad" configuration. This is valuable in testing to that you can disable the lib in a clear way and in production so that bad configuration causes an error and not a silent failure. |
ba73ff6
to
a470ff1
Compare
Use a flag to determine if Datadog should be disabled using a flag rather than relying on bad configuration. This removes the need to check for bad configuration before starting Datadog in services. Closes: #306
ef5e90a
to
8b70a80
Compare
45c34d8
to
39e0abe
Compare
@LinMAD waiting for you here |
Use a flag to determine if Datadog should be disabled using a flag rather than
relying on bad configuration.
This removes the need to check for bad configuration before starting Datadog in
services.
Closes: #306