Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CloudWatch alarms left triggered after _hibernate function is used #6702

Open
dsotirho-ucsc opened this issue Nov 12, 2024 · 0 comments
Open
Assignees
Labels
- [priority] Medium enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts no demo [process] Not to be demonstrated at the end of the sprint orange [process] Done by the Azul team

Comments

@dsotirho-ucsc
Copy link
Contributor

Using the _hibernate function to take a deployment (such as tempdev) offline leaves various CloudWatch alarms in a state of alarm:

Alarms left in alarm state

  • azul-freshclam
  • azul-clamscan
  • azul-indexercachehealth
  • azul-servicecachehealth

Alarms left in insufficient data state

  • azul-gitlab_cpu_use
  • azul-gitlab_data_disk_use
  • azul-gitLab_root_disk_use

Screenshot 2024-11-12 at 3 36 00 PM

@dsotirho-ucsc dsotirho-ucsc added the orange [process] Done by the Azul team label Nov 12, 2024
@dsotirho-ucsc dsotirho-ucsc self-assigned this Nov 12, 2024
@dsotirho-ucsc dsotirho-ucsc added bug [type] A defect preventing use of the system as specified - [priority] Medium enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts and removed bug [type] A defect preventing use of the system as specified labels Nov 13, 2024
@hannes-ucsc hannes-ucsc added the no demo [process] Not to be demonstrated at the end of the sprint label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- [priority] Medium enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts no demo [process] Not to be demonstrated at the end of the sprint orange [process] Done by the Azul team
Projects
None yet
Development

No branches or pull requests

2 participants