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
- "You miss 100 percent of the chances you don't take. — Wayne Gretzky" — Michael Scott
6
6
7
+
## 7.54.0
8
+
9
+
### Important Changes
10
+
11
+
-**feat(core): Add default entries to `ignoreTransactions` for Healthchecks #8191**
12
+
13
+
All SDKs now filter out health check transactions by default.
14
+
These are transactions where the transaction name matches typical API health check calls, such as `/^.*healthy.*$/` or `/^. *heartbeat.*$/`. Take a look at [this list](https://github.com/getsentry/sentry-javascript/blob/8c6ad156829f7c4eec34e4a67e6dd866ba482d5d/packages/core/src/integrations/inboundfilters.ts#L8C2-L16) to learn which regexes we currently use to match transaction names.
15
+
We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default.
16
+
These filters are implemented as default values for the top level `ignoreTransactions` option.
17
+
18
+
You can disable this filtering by manually specifiying the `InboundFilters` integration and setting the `disableTransactionDefaults` option:
This release adds support Vercel Cron Jobs in the Next.js SDK.
106
+
The SDK will automatically create [Sentry Cron Monitors](https://docs.sentry.io/product/crons/) for your [Vercel Cron Jobs](https://vercel.com/docs/cron-jobs) configured via `vercel.json` when deployed on Vercel.
107
+
108
+
You can opt out of this functionality by setting the `automaticVercelMonitors` option to `false`:
109
+
110
+
```js
111
+
// next.config.js
112
+
constnextConfig= {
113
+
sentry: {
114
+
automaticVercelMonitors:false,
115
+
},
116
+
};
117
+
```
118
+
119
+
(Note: Sentry Cron Monitoring is currently in beta and subject to change. Help us make it better by letting us know what you think. Respond on [GitHub](https://github.com/getsentry/sentry/discussions/42283) or write to us at [email protected])
120
+
121
+
- feat(nextjs): Add API method to wrap API routes with crons instrumentation (#8084)
122
+
- feat(nextjs): Add automatic monitors for Vercel Cron Jobs (#8088)
123
+
124
+
### Other changes
125
+
126
+
- feat(replay): Capture keyboard presses for special characters (#8051)
127
+
- fix(build): Don't mangle away global debug ID map (#8096)
128
+
- fix(core): Return checkin id from client (#8116)
129
+
- fix(core): Use last error for `ignoreErrors` check (#8089)
130
+
- fix(docs): Change to `addTracingExtensions` was not documented in MIGRATION.md (#8101)
- fix(node): Make sure we use same ID for checkIns (#8050)
145
+
- fix(replay: Keep session active on key press (#8037)
146
+
- fix(replay): Move error sampling to before send (#8057)
147
+
- fix(sveltekit): Wrap `load` when typed explicitly (#8049)
148
+
149
+
**Replay `rrweb` changes:**
150
+
151
+
`@sentry-internal/rrweb` was updated from 1.106.0 to 1.108.0:
152
+
153
+
- fix: Fix some input masking (esp for radio buttons) ([#85](https://github.com/getsentry/rrweb/pull/85))
154
+
- fix: Unescaped `:` in CSS rule from Safari ([#86](https://github.com/getsentry/rrweb/pull/86))
155
+
- feat: Define custom elements (web components) ([#87](https://github.com/getsentry/rrweb/pull/87))
156
+
157
+
Work in this release contributed by @sreetamdas. Thank you for your contribution!
158
+
7
159
## 7.51.0
8
160
9
161
### Important Changes
@@ -26,30 +178,40 @@ Note that `@sentry/angular` _does not_ support Angular 16.
26
178
27
179
-**feat(node): Add ability to send cron monitor check ins (#8039)**
28
180
181
+
**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**
182
+
29
183
This release adds [Sentry cron monitoring](https://docs.sentry.io/product/crons/) support to the Node SDK.
30
184
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.
185
+
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
186
33
187
```ts
34
188
const Sentry =require('@sentry/node');
35
189
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',
190
+
// 🟡 Notify Sentry your job is running:
191
+
const checkInId =Sentry.captureCheckIn({
192
+
monitorSlug: '<monitor-slug>',
42
193
status: 'in_progress',
43
194
});
44
195
45
-
const startTime =timeInSeconds();
46
-
47
-
runTask();
196
+
// Execute your scheduled task here...
48
197
198
+
// 🟢 Notify Sentry your job has completed successfully:
49
199
Sentry.captureCheckIn({
50
-
monitorSlug: 'dailyEmail',
200
+
// make sure you pass in the checkInId generated by the first call to captureCheckIn
201
+
checkInId,
202
+
monitorSlug: '<monitor-slug>',
51
203
status: 'ok',
52
-
duration: timeInSeconds() -startTime,
204
+
});
205
+
```
206
+
207
+
If your job execution fails, you can notify Sentry about the failure:
## Remove requirement for `@sentry/tracing` package (since 7.46.0)
8
36
9
37
With `7.46.0` you no longer require the `@sentry/tracing` package to use tracing and performance monitoring with the Sentry JavaScript SDKs. The `@sentry/tracing` package will be removed in a future major release, but can still be used in the meantime.
0 commit comments