You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current setup for monitoring crons requires a wrapper function (link to docs). You use it like this:
constCronJobWithCheckIn=Sentry.cron.instrumentCron(CronJob,'cron_slug');constjob=CronJobWithCheckIn.from({cronTime: '7 * * * * *',onTick: ()=>{console.log('cron: Job is running every few seconds');},});job.start();
Solution Brainstorm
We could add a new integration which is extending OpenTelementry and publish it as separate packages and remove the wrapper, which is currently needed. These OTEL instrumentations can also automatically create spans, something that is not supported atm.
If we make these integrations, we need them to be opt-in because crons charge per monitor. We have two options:
Have users explicitly add integrations, with ability to specify monitors they are only interested in
Have all cron integrations enabled by default, but expose a public API options surface to manage what monitors are created.
The content you are editing has changed. Please copy your edits and refresh the page.
Problem Statement
The current setup for monitoring crons requires a wrapper function (link to docs). You use it like this:
Solution Brainstorm
We could add a new integration which is extending OpenTelementry and publish it as separate packages and remove the wrapper, which is currently needed. These OTEL instrumentations can also automatically create spans, something that is not supported atm.
If we make these integrations, we need them to be opt-in because crons charge per monitor. We have two options:
Phase 1: Initial Implementation
Phase 1: Migration
The text was updated successfully, but these errors were encountered: