chore: Do not update opentelemetry

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!

[JPeer264]

This disables the creation of dependabot updates for opentelemetry. Based on the image below there was not a real benefit of having this, except noise.

[andreiborza]

For reference: The reason these are low-value is that bumping OpenTelemetry instrumentations needs to happen in lockstep across the entire codebase and often requires additional hand-tuning to make it work.

I created a PR to add a cursor command to make this a bit easier for us: #18253

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	11,191	-	8,783	+27%
GET With Sentry	1,652	15%	1,354	+22%
GET With Sentry (error only)	7,788	70%	5,981	+30%
POST Baseline	1,198	-	1,200	-0%
POST With Sentry	539	45%	494	+9%
POST With Sentry (error only)	1,065	89%	1,036	+3%
MYSQL Baseline	4,079	-	3,258	+25%
MYSQL With Sentry	672	16%	464	+45%
MYSQL With Sentry (error only)	3,342	82%	2,673	+25%

View base workflow run

[andreiborza]

ty!