fix(aws-serverless): Extract sentry trace data from handler `context` over `event` by andreiborza · Pull Request #13266 · getsentry/sentry-javascript

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

andreiborza · 2024-08-07T15:00:08Z

Currently, the AWS otel integration (and our wrapHandler fallback) try to extract sentry trace data from the event object passed to a Lambda call. The aws-sdk integration, however, places tracing data onto context.clientContext.Custom.

This PR adds a custom eventContextExtractor that attempts extracting sentry trace data from the context, with a fallback to event to enable distributed tracing among Lambda invocations.

Traces are now connected. Here an example:

Lambda-A calling Lambda-B:

import { LambdaClient, InvokeCommand } from "@aws-sdk/client-lambda";
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
const client = new LambdaClient();
const command = new InvokeCommand({
FunctionName: `Lambda-B`,
InvocationType: "RequestResponse",
Payload: new Uint16Array(),
})
return client.send(command);
});

Lambda-B:

import * as Sentry from "@sentry/aws-serverless";
Sentry.addIntegration(Sentry.postgresIntegration())
export const handler = Sentry.wrapHandler(async (event) => {
const queryString = "select count(*) from myTable;";
return await Sentry.startSpan({
name: queryString,
op: "db.sql.execute"
}, async (span) => {
console.log('executing query', queryString);
})
})

Closes: #13146

… over `event`

github-actions · 2024-08-07T15:04:05Z

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	114.85 KB (+0.01% 🔺)
@sentry/node - without tracing	89.33 KB (0%)
@sentry/aws-serverless	98.75 KB (+0.26% 🔺)

mydea · 2024-08-08T06:45:14Z

 hasBundles: true,
+ packageSpecificConfig: {
+ // Used for our custom eventContextExtractor
+ external: ['@opentelemetry/api'],


just out of curiosity, why is this needed?

Package build structure isn't right without this. It pulls this in under its own node_modules folder.

mydea · 2024-08-08T06:46:15Z

+ * Sentry's context. This should usually be `true` when
+ * using Sentry to instrument Lambdas.


Suggested change
*Sentry's context. This should usually be `true` when
*using SentrytoinstrumentLambdas.
*Sentry's context. Defaults to `true`, in order for Sentry trace propagation to take precedence,
*butcanbedisabledifyouwanttoAWSpropagationtotakeprecedence.
or something like this?

mydea · 2024-08-08T06:48:22Z

 import { awsIntegration } from './integration/aws';
 import { awsLambdaIntegration } from './integration/awslambda';
-import { markEventUnhandled } from './utils';
+import { getTraceData, markEventUnhandled } from './utils';


m: Can we change the name here, as it conflicts with getTraceData we have in core, making this possibly a bit confusing 😅 E.g. getAwsTraceData or something like this?

Yep, good point.

mydea · 2024-08-08T06:51:04Z

+ const customContext: Record<string, unknown> = context.clientContext.Custom;
+ const sentryTrace = isString(customContext['sentry-trace']) ? customContext['sentry-trace'] : undefined;
+
+ if (sentryTrace) {


m: It will probably not matter in 99% of cases, but let's just split this into two if-blocks. So basically:
constsentryTrace= ...;constbaggage= ...;if(sentryTrace){traceData['sentry-trace']=sentryTrace;}if(baggage){traceData.baggage=baggage;}
I think this is slightly more robust :)

I was thinking of that, but wouldn't we potentially end up with a mix of wrong pairs, e.g. both event and context have baggage but only event has sentry-trace. So we end up with sentry-trace from event and baggage from context.
I don't know if that's a realistic usecase tho. In core, we also throw away baggage if sentryTrace is not valid.

right, then let's keep it this way, all good! 👍

mydea · 2024-08-08T06:52:17Z

+
+/**
+ * Extracts sentry trace data from the handler `context` if available and falls
+ * back to the `event`.


Maybe we can also add a short note here when this would be on context and when on event?

I added an explanation, but tbh this is pretty wide open. I think different AWS services make use of different event/context usage. Hope this adds a bit more info?

mydea

left some notes, more about details - overall great work! Big improvement :)

… getTraceData

fix(aws-serverless): Extract sentry trace data from handler context…
3715f11
… over `event`

andreiborza requested review from AbhiPrasad, Lms24 and mydea August 7, 2024 15:00

mydea reviewed Aug 8, 2024
View reviewed changes

mydea approved these changes Aug 8, 2024
View reviewed changes

andreiborza added 3 commits August 8, 2024 08:54

Update aws integration option comment for clarity
6c2953b

Rename getTraceData to getAwsTraceData to avoid confusion with core's…
39506af
… getTraceData

Update jsdoc for getAwsTraceData
9d05c00

andreiborza requested a review from mydea August 8, 2024 07:53

mydea approved these changes Aug 8, 2024
View reviewed changes

andreiborza merged commit b17ac59 into developAug 8, 2024

andreiborza deleted the ab/aws-lambda-client-context branch August 8, 2024 08:57

gokulk16 mentioned this pull request Aug 30, 2024
[Snyk] Upgrade @sentry/browser from 8.20.0 to 8.25.0 gokulk16/type-to-calculate-web#38
Merged

This was referenced Aug 30, 2024
[Snyk] Upgrade @sentry/nextjs from 8.22.0 to 8.25.0 dupipcom/hypnos#55
Open
[Snyk] Upgrade @sentry/nextjs from 8.20.0 to 8.25.0 dupipcom/hygieia#5
Open

This was referenced Aug 30, 2024
[Snyk] Upgrade @sentry/node from 8.22.0 to 8.25.0 Aam-Digital/replication-backend#154
Closed
[Snyk] Upgrade @sentry/node from 8.22.0 to 8.25.0 Aam-Digital/account-backend#41
Closed

q1blue mentioned this pull request Aug 30, 2024
[Snyk] Upgrade @sentry/react from 7.16.0 to 8.25.0 https-quantumblockchainai-atlassian-net/ossinsight#835
Open

angeloreale mentioned this pull request Aug 31, 2024
[Snyk] Upgrade @sentry/nextjs from 8.22.0 to 8.25.0 dupipcom/hypnos#60
Open

FengShangWuQi mentioned this pull request Sep 1, 2024
[Snyk] Upgrade @sentry/gatsby from 7.20.0 to 8.25.0 FengShangWuQi/fengshangwuqi.github.io#1918
Closed

PierreGode mentioned this pull request Sep 4, 2024
[Snyk] Upgrade @sentry/node from 8.9.2 to 8.25.0 PierreGode/shields#1
Closed

This was referenced Sep 4, 2024
[Snyk] Upgrade @sentry/node from 8.22.0 to 8.26.0 Aam-Digital/account-backend#42
Closed
[Snyk] Upgrade @sentry/node from 8.22.0 to 8.26.0 Aam-Digital/replication-backend#158
Closed

q1blue mentioned this pull request Sep 7, 2024
[Snyk] Upgrade @sentry/react from 7.16.0 to 8.26.0 https-quantumblockchainai-atlassian-net/ossinsight#846
Open

FengShangWuQi mentioned this pull request Sep 8, 2024
[Snyk] Upgrade @sentry/gatsby from 7.20.0 to 8.26.0 FengShangWuQi/fengshangwuqi.github.io#1919
Closed

bagulm123 mentioned this pull request Sep 8, 2024
[Snyk] Upgrade: , , chart.js, classnames, cytoscape, typescript bagulm123/komiser#18
Open

KeeghanM mentioned this pull request Sep 12, 2024
[Snyk] Upgrade: , , , , , , next, posthog-js, posthog-node, react-chessboard, stripe KeeghanM/chess-training-app#94
Merged

This was referenced Sep 13, 2024
[Snyk] Upgrade: , , chart.js, classnames, cytoscape, next, typescript bagulm123/komiser#19
Open
[Snyk] Upgrade: , , , chart.js, classnames, cytoscape, next, typescript bagulm123/komiser#20
Open

gokulk16 mentioned this pull request Sep 23, 2024
[Snyk] Upgrade: , gokulk16/type-to-calculate-web#40
Closed

q1blue mentioned this pull request Sep 24, 2024
[Snyk] Upgrade @sentry/react from 7.16.0 to 8.27.0 https-quantumblockchainai-atlassian-net/ossinsight#893
Open

This was referenced Sep 24, 2024
[Snyk] Upgrade @sentry/browser from 8.25.0 to 8.27.0 gokulk16/type-to-calculate-web#42
Closed
[Snyk] Upgrade @sentry/browser from 8.25.0 to 8.28.0 gokulk16/type-to-calculate-web#44
Closed

FengShangWuQi mentioned this pull request Sep 27, 2024
[Snyk] Upgrade @sentry/gatsby from 7.20.0 to 8.28.0 FengShangWuQi/fengshangwuqi.github.io#1923
Closed

This was referenced Sep 27, 2024
[Snyk] Upgrade @sentry/react from 7.16.0 to 8.28.0 https-quantumblockchainai-atlassian-net/ossinsight#899
Open
[Snyk] Upgrade @sentry/react from 7.16.0 to 8.29.0 https-quantumblockchainai-atlassian-net/ossinsight#904
Open

bagulm123 mentioned this pull request Oct 1, 2024
[Snyk] Upgrade @sentry/react from 8.22.0 to 8.29.0 bagulm123/komiser#23
Open

q1blue mentioned this pull request Oct 1, 2024
[Snyk] Upgrade @sentry/react from 7.16.0 to 8.30.0 https-quantumblockchainai-atlassian-net/ossinsight#909
Open

andreiborza mentioned this pull request Dec 10, 2024
Investigate how AWS x-ray tracing propagator changes affect sentry tracing #14635
Open