Skip to content

Conversation

bszabo
Copy link
Contributor

@bszabo bszabo commented Aug 19, 2025

Pinning ddtrace to version from before the deploy that had to be rolled back with yesterday's production incident. Version 3.12.0 has been confirmed as safe; version 3.12.1 causes excessive CPU loading and avalanche autoscaling.


Make sure that the following steps are done before merging:

  • Have a Site Reliability Engineer review the PR if you don't own all of the services impacted.
  • If you are adding any new default values that need to be overridden when this change goes live, update internal repos and add an entry to the top of the CHANGELOG.
  • Performed the appropriate testing.

Pinning ddtrace to version from before the deploy that had to be rolled back with yesterday's production incident. Version 3.12.0 has been confirmed as safe; version 3.12.1 causes excessive CPU loading and avalanche autoscaling.
bszabo and others added 2 commits August 19, 2025 17:33
Pinning ddtrace to version from before the deploy that had to be rolled back with yesterday's production incident. Version 3.12.0 has been confirmed as safe; version 3.12.1 causes excessive CPU loading and avalanche autoscaling.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants