Add alarms and monitoring for infra stack #84
Conversation
Signed-off-by: Sayali Gaikawad <[email protected]>
Signed-off-by: Sayali Gaikawad <[email protected]>
Signed-off-by: Sayali Gaikawad <[email protected]>
gaiksaya
requested review from
peterzhuamazon,
bbarani,
rishabh6788,
zelinh,
jordarlu,
prudhvigodithi and
Divyaasm
as code owners
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #84 +/- ##
==========================================
+ Coverage 79.24% 80.08% +0.84%
==========================================
Files 6 7 +1
Lines 448 467 +19
Branches 132 134 +2
==========================================
+ Hits 355 374 +19
Misses 93 93 ☔ View full report in Codecov by Sentry. |
|
Lets keep everything related to monitors and alarms optional and in a separate stack. The default deployment should be light and quick and infra stack should only deal with everything related to running OS and OSD process. |
Signed-off-by: Sayali Gaikawad <[email protected]>
Signed-off-by: Sayali Gaikawad <[email protected]>
Separated the classes and made the alarms optional. Trying to avoid another stack as all the resources that needs to be tracked are a part of infrastrack and would need many imports/exports to carry over to another stack. |
Description
This change adds a bunch of alarms along with alarm dashboard and namespace for all metrics so that they can stay separate for multiple infra stacks. The resources are deployed as a part of the infrastack for easy integration rather than maintaining a new stack just for monitoring.
Issues Resolved
resolves #74
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.