-
Notifications
You must be signed in to change notification settings - Fork 83
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
Monitoring Packs #67
Comments
still relevant |
Just came over the same topic as I want to offer some alarms as part of my Construct that is shared as library. Unfortunately, there's no standard yet like I was thinking about something similar to this:
An additional interface could help to identify such Constructs. |
Marking this RFCs as |
Description
A centralized dashboard and alarming settings are standard operational patterns for cloud services. We currently have the capabilities to define a CloudWatch Dashboard and setup alarms but it would be valuable to be able to define a centralized monitoring "hub" which constructs can automatically discover and "register" to.
Ideally, whenever a construct is added to a stack (at any level), it can also add dashboard widgets and define a default set of alarms that will trigger a common monitoring alerting system.
It would be valuable to define a pattern for exposing "monitoring packs" for constructs. The idea is that constructs can bundle a set of monitoring settings such as alarms and dashboard graphs/widgets which can automatically "register" into a stack/app-central monitoring system.
Progress
The text was updated successfully, but these errors were encountered: