Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • : 14:03 - Breaking change deployed to production.

  • : 14:05 - Notification sent to slack channel for stage #monitoring-prod

  • : 14:10 - Notification sent to slack channel #monitoring-prod

  • : 14:11 - Issue picked up by dev team.

  • : 14:17 - Fix deployed to production.

...

  • Profile service failed to start

    • Change to the Sentry configuration caused a breaking change

      • The implemented Sentry configuration requires Spring Boot 2.1.0 and newer (Profile uses 1.5.2)

    • The build continued despite failures

    • The alert about stage going down (14:05) was obscured by other alerts.

...

Action Items

Action Items

Owner

Find out why the configuration made the service fail

Marcello Fabbri (Unlicensed)

Find a working solution to migrate to sentry-spring-boot-starter 4.3.0 without failures

Marcello Fabbri (Unlicensed)

Improve the profile pipeline, e.g.:

  • Health checks

  • Integration Tests

  • GHA?

  • ECS?

Upgrade spring-boot in profile Don’t think this is worth it atm; we’ll be moving to cognito.

...

Lessons Learned

  • Test changes properly locally and on stage before pushing to production.