ACloudGuru/serverless-plugin-aws-alerts

Support for using a single dynamically generated SNS Topic

Open

#73 opened on Oct 2, 2018

View on GitHub
 (0 comments) (4 reactions) (0 assignees)JavaScript (150 forks)auto 404
feature requesthelp wanted

Repository metrics

Stars
 (523 stars)
PR merge metrics
 (PR metrics pending)

Description

This is a Feature Proposal

Description

For bug reports:

  • What went wrong?
  • What did you expect should have happened?
  • What was the config you used?
  • What stacktrace or error message from your provider did you see?

For feature proposals:

  • What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us. Today this plugin supports creating SNS topics per alarm state or using an existing SNS topic as the action for the alarms created.

I would prefer not to have to create separate SNS topics for each alarm state but instead I would like to have the plugin create a single SNS topic that is the action for Ok,Alarm and Insufficient. In my use case where the alerting endpoint is a pagerduty end point having 2 or 3 topic that hit the send endpoint is redundant

  • If there is additional config how would it look serveless.yml could look something like this
  alerts:
    stages:
      - beta
    topic: ${self:service}-${opt:stage}-alerts
    notifications:
      - protocol: https
        endpoint:

Similar or dependent issues:

  • #12345

Additional Data

  • Serverless Framework Version:
  • Stack Trace:
  • Provider Error messages:

Contributor guide