-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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(crons): Ruby docs for auto-instrumentation #8550
feat(crons): Ruby docs for auto-instrumentation #8550
Conversation
@natikgadzhi is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Good from the docs side!
We've merged the mentioned PR that implement the automatic checkins support, but we have not rolled a release yet. I'll keep an eye on when it goes to GA. |
will merge after release on monday |
Summary
This is a satellite PR to Sentry-Ruby's Crons auto-instrumentation support. We should only merge this when the three PRs below are merged and shipped:
sentry-cron
: Addsidekiq-cron
patch for automatic monitoring of jobs listed in the schedule sentry-ruby#2170sentry-scheduler
: Crons: addsidekiq-scheduler
zero-config monitor check-ins sentry-ruby#2172sentry-cron
cleanup: (fix) crons: require sidekiq-cron early sentry-ruby#2173/cc @sl0thentr0py
Pre-merge checklist
If you work at Sentry, you're able to merge your own PR without review, but please don't unless there's a good reason.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Extra resources