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
Extract ActiveSupport from Rails #747
Conversation
b4425dd
to
33c8fd3
Compare
@@ -93,6 +79,18 @@ def call_pipeline(*args, &block) | |||
|
|||
response | |||
end | |||
|
|||
def datadog_pin |
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.
This fixes a bug where a Redis client initialized before being patched wouldn't receive trace configuration, and thus wouldn't send traces. By lazy initializing the Pin
, we can ensure it's available at trace time.
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.
Nice, looks good.
5717195
to
2224b72
Compare
305dd59
to
2224b72
Compare
2224b72
to
af16bae
Compare
af16bae
to
3769229
Compare
3769229
to
15ba4f9
Compare
Reworked this one a little bit:
This probably warrants another review @brettlangdon. |
e4a8967
to
2c3d927
Compare
df6ad3d
to
9414b9f
Compare
9414b9f
to
9bd69e7
Compare
As a first step towards simplifying the Rails integration, this pull request extracts all the ActiveSupport instrumentation from the Rails integration into a new
active_support
integration. This new integration is automatically activated by the Rails integration, so users withuse :rails
should see no change.Users who don't use Rails, but do use ActiveSupport should now be able to activate instrumentation for this gem without the Rails integration.