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 problem is that every time we call addBreadcrumb from the Sentry SDK, we receive notices in the console like:
But any message captured with captureMessage works without issue.
According to the types, timestamp should be:
/** * The format is a numeric (integer or float) value representing * the number of seconds that have elapsed since the Unixepoch. * Breadcrumbs are most useful when they include a timestamp, as it creates a timeline * leading up to an event expection/error. * * @note The API supports a string as defined in RFC 3339, but the SDKs only support a numeric value for now. * * @summary A timestamp representing when the breadcrumb occurred. * @link https://develop.sentry.dev/sdk/event-payloads/breadcrumbs/#:~:text=is%20info.-,timestamp,-(recommended) */
timestamp?: number;
Is it really supposed to be a number and not a string?
As an example if we look at the invalid value breadcrumbs.values.2.timestamp
The "invalid" value is: 1717173577649
Which corresponds to: Friday, May 31, 2024 4:39:37.649 PM
So the value itself is valid.
Expected Result
Adding a breadcrumb with a timestamp, the timestamp should appear in the console.
Actual Result
The error as above.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
8.7.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
No response
Steps to Reproduce
In addition to the normal spans, we are publishing a number of breadcrumbs to Sentry.
The code reporting these breadcrumbs to Sentry looks like:
The problem is that every time we call
addBreadcrumb
from the Sentry SDK, we receive notices in the console like:But any message captured with
captureMessage
works without issue.According to the types,
timestamp
should be:Is it really supposed to be a
number
and not astring
?As an example if we look at the invalid value
breadcrumbs.values.2.timestamp
The "invalid" value is:
1717173577649
Which corresponds to:
Friday, May 31, 2024 4:39:37.649 PM
So the value itself is valid.
Expected Result
Adding a breadcrumb with a timestamp, the timestamp should appear in the console.
Actual Result
The error as above.
The text was updated successfully, but these errors were encountered: