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
- fix(node): Make sure we use same ID for checkIns (#8050)
12
+
- fix(replay: Keep session active on key press (#8037)
13
+
- fix(replay): Move error sampling to before send (#8057)
14
+
- fix(sveltekit): Wrap `load` when typed explicitly (#8049)
15
+
16
+
**Replay `rrweb` changes:**
17
+
18
+
`@sentry-internal/rrweb` was updated from 1.106.0 to 1.108.0:
19
+
20
+
- fix: Fix some input masking (esp for radio buttons) ([#85](https://github.com/getsentry/rrweb/pull/85))
21
+
- fix: Unescaped `:` in CSS rule from Safari ([#86](https://github.com/getsentry/rrweb/pull/86))
22
+
- feat: Define custom elements (web components) ([#87](https://github.com/getsentry/rrweb/pull/87))
23
+
24
+
Work in this release contributed by @sreetamdas. Thank you for your contribution!
25
+
7
26
## 7.51.0
8
27
9
28
### Important Changes
@@ -26,30 +45,40 @@ Note that `@sentry/angular` _does not_ support Angular 16.
26
45
27
46
-**feat(node): Add ability to send cron monitor check ins (#8039)**
28
47
48
+
**Note: This release contains a bug with generating cron monitors. We recommend you upgrade the JS SDK to 7.51.1 or above to use cron monitoring functionality**
49
+
29
50
This release adds [Sentry cron monitoring](https://docs.sentry.io/product/crons/) support to the Node SDK.
30
51
31
-
To monitor your cron jobs, send check-ins everytime you execute your cron jobs to Sentry. You can do this with the `captureCheckIn` method exported from the SDK. First you must send an `in_progress`, checkin, then you can send one with status `ok` or `error` based on what happened with your cron job.
52
+
Check-in monitoring allows you to track a job's progress by completing two check-ins: one at the start of your job and another at the end of your job. This two-step process allows Sentry to notify you if your job didn't start when expected (missed) or if it exceeded its maximum runtime (failed).
32
53
33
54
```ts
34
55
const Sentry =require('@sentry/node');
35
56
36
-
// ...
37
-
38
-
Sentry.captureCheckIn({
39
-
// make sure this is the same slug as what you set up your
40
-
// Sentry cron monitor with.
41
-
monitorSlug: 'dailyEmail',
57
+
// 🟡 Notify Sentry your job is running:
58
+
const checkInId =Sentry.captureCheckIn({
59
+
monitorSlug: '<monitor-slug>',
42
60
status: 'in_progress',
43
61
});
44
62
45
-
const startTime =timeInSeconds();
46
-
47
-
runTask();
63
+
// Execute your scheduled task here...
48
64
65
+
// 🟢 Notify Sentry your job has completed successfully:
49
66
Sentry.captureCheckIn({
50
-
monitorSlug: 'dailyEmail',
67
+
// make sure you pass in the checkInId generated by the first call to captureCheckIn
68
+
checkInId,
69
+
monitorSlug: '<monitor-slug>',
51
70
status: 'ok',
52
-
duration: timeInSeconds() -startTime,
71
+
});
72
+
```
73
+
74
+
If your job execution fails, you can notify Sentry about the failure:
0 commit comments