Skip to content
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

Refactor Delayed::Job integration to not use monitor_transaction #1171

Merged
merged 2 commits into from
Jul 10, 2024

Conversation

tombruijn
Copy link
Member

Move Delayed::Job plugin to integrations namespace

The DelayedJobPlugin was defined in the integrations directory, but used the Hooks module namespace. Update the namespace so it matches its location. No redirect needed because it's a private API no one should be accessing.

Split the test file so it tests what's in the related file.

Do not use monitor_transaction for Delayed::Job

Refactor the Delayed::Job integration not to use the monitor_transaction helper. A helper we want to deprecate.

The implementation is mostly the same, except how we set the attributes. I have changed it to store them as tags. Previously we set the attributes as "sample data metadata". This is another way to set metadata/tags in the transaction API. All three data types end up in the "overview" tag box, so it doesn't really matter how we set the values.

[skip changeset] because it's an internal refactor.

The DelayedJobPlugin was defined in the integrations directory, but used
the Hooks module namespace. Update the namespace so it matches its
location. No redirect needed because it's a private API no one should be
accessing.

Split the test file so it tests what's in the related file.
Refactor the Delayed::Job integration not to use the
`monitor_transaction` helper. A helper we want to deprecate.

The implementation is mostly the same, except how we set the attributes.
I have changed it to store them as tags. Previously we set the
attributes as "sample data metadata". This is another way to set
metadata/tags in the transaction API. All three data types end up in the
"overview" tag box, so it doesn't really matter how we set the values.

[skip changeset] because it's an internal refactor.
@tombruijn tombruijn added the chore label Jul 9, 2024
@tombruijn tombruijn self-assigned this Jul 9, 2024
@tombruijn tombruijn mentioned this pull request Jul 9, 2024
82 tasks
@tombruijn tombruijn merged commit 9e50419 into main Jul 10, 2024
117 checks passed
@tombruijn tombruijn deleted the update-delayed-job-instrumentation branch July 10, 2024 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant