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

Monitoring Packs #67

Closed
1 of 7 tasks
eladb opened this issue Jun 29, 2018 · 3 comments
Closed
1 of 7 tasks

Monitoring Packs #67

eladb opened this issue Jun 29, 2018 · 3 comments
Labels
effort/medium Reasonable effort required for implementation status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@eladb
Copy link
Contributor

eladb commented Jun 29, 2018

PR Champion
#

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.

  • All L2s include dashboard/monitoring packs (like watchful)
  • Normalize metrics across L2s (we don't have a linter rule for metrics)

Progress

  • Tracking Issue Created
  • RFC PR Created
  • Core Team Member Assigned
  • Initial Approval / Final Comment Period
  • Ready For Implementation
    • implementation issue 1
  • Resolved
@eladb eladb self-assigned this Aug 27, 2019
@eladb
Copy link
Contributor Author

eladb commented Oct 2, 2019

still relevant

@eladb eladb transferred this issue from aws/aws-cdk Jan 22, 2020
@eladb eladb added the effort/medium Reasonable effort required for implementation label Jan 22, 2020
@eladb eladb removed their assignment Jan 22, 2020
@pgarbe
Copy link

pgarbe commented Mar 10, 2020

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 metricsXXX() or grantXXX().

I was thinking about something similar to this:

class MyConstruct { 
  sendAlarmsTo(topic: sns.ITopic, options: MyAlarmOptions) {
    // Create CW alarms... 
  }
}

An additional interface could help to identify such Constructs.

@eladb eladb changed the title Monitoring packs and a centralized monitoring "hub" Monitoring Packs Jun 23, 2020
@eladb eladb mentioned this issue Jun 23, 2020
7 tasks
@eladb eladb added the status/proposed Newly proposed RFC label Jun 23, 2020
@mrgrain mrgrain closed this as completed Oct 18, 2023
@mrgrain mrgrain added status/stale The RFC did not get any significant enough progress or tracking and has become stale. and removed status/proposed Newly proposed RFC labels Oct 18, 2023
@mrgrain
Copy link
Contributor

mrgrain commented Oct 18, 2023

Marking this RFCs as stale since there has been little recent activity and it is not currently close to getting accepted as-is. We appreciate the effort that has gone into this proposal. Marking an RFCs as stale is not a one-way door. If you have made substantial changes to the proposal, please open a new issue/RFC. You might also consider raising a PR to aws/aws-cdk directly or self-publishing to Construct Hub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/medium Reasonable effort required for implementation status/stale The RFC did not get any significant enough progress or tracking and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants