getsentry / getsentry/sentry-javascript

Add crons integration extending OpenTelementry and remove Sentry cron wrapper

未关闭
#11,790 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
Checks Crons Improvement Node.js
主要语言
TypeScript
星标
8.7k
派生
1.8k
平均合并
1 天 17 小时
30 天内合并 PR
515

描述

### Problem Statement

The current setup for monitoring crons requires a wrapper function ([link to docs](https://docs.sentry.io/platforms/javascript/guides/node/crons/)). You use it like this:

```js
const CronJobWithCheckIn = Sentry.cron.instrumentCron(CronJob, 'cron_slug');

const job = 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:

1. Have users explicitly add integrations, with ability to specify monitors they are only interested in
2. Have all cron integrations enabled by default, but expose a public API options surface to manage what monitors are created.

```[tasklist]
### Phase 1: Initial Implementation
- [ ] Add `@sentry/opentelemetry-instrumentation-cron`
- [ ] Add `@sentry/opentelemetry-instrumentation-node-cron`
- [ ] Add `@sentry/opentelemetry-instrumentation-node-schedule`
- [ ] Add integration for `cron`
- [ ] Add integration for `node-cron`
- [ ] Add integration for `node-schedule`
```

```[tasklist]
### Phase 1: Migration
- [ ] Update docs
- [ ] Deprecate `Sentry.cron` methods
```

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。