Add Datadog tracing to client, server, & worker instrumentation code #27
Conversation
This file contains 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
SheffAtEnova
changed the title
SheffAtEnova
force-pushed
the
add_error_tracing
branch
from
16f5e49
to
5951955
Compare
SheffAtEnova
force-pushed
the
add_error_tracing
branch
from
5951955
to
de54838
Compare
calvinochan
approved these changes
May 10, 2024
Node 16 is deprecated and the Actions runner recommended updating actions/checkout to v4 to address this.
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.
This PR adds support for Datadog error tracing to the sidekiq-instrument library. Doing so should enable adopters to rely upon Datadog's Error tracing functionality rather than emitting logs and stack traces for every encountered error (which can balloon log ingestion costs).