Added 90% ES CPU alarms to those disabled for the data refresh

[coson-lu]

…freshed (Issue #4826)

Fixes

Fixes #4826 by @AetherUnbound

Description

This pull requests adds the Elasticsearch 90% CPU alarm to the list of alarms which get disabled for the refresh data.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
  PRs) or the media properties generator (ov just catalog/generate-docs media-props
  for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[stacimc]

Perfect, thanks @coson-lu!

[AetherUnbound]

One small change which I'll make in-line, just didn't want this to get merged first

[AetherUnbound]

Sweet, thanks for the contribution @coson-lu!

[sarayourfriend]

Just a heads-up @AetherUnbound and any other spectators of this issue: modifying alarm states from DAGs requires IAM changes to give the Airflow execution environment permissions to do so. I've gone ahead and fixed it for this alarm, but keep that in mind when interacting with AWS resources in the future. Access is enabled and controlled via IAM and permissions errors will happen in the live environment without those additional changes.

[AetherUnbound]

Ahh, that was a complete oversight on my part. Thanks for the notice 🙂