Ad Widget

Collapse

Extracting triggers by application OR including application during action processing

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • marketfresh
    Junior Member
    • Feb 2021
    • 1

    #1

    Extracting triggers by application OR including application during action processing

    I'm struggling here. We currently use Application as a criteria for a number of our actions. We are also in the process of building a new notification pipeline for our entire alerting suite (multiple monitoring platforms, including zabbix) that results in all alerting going through a "Rule processor" lambda in AWS. The intention is that we will replace our actions in Zabbix today with a fire hose action per hostgroup that will basically send all alerts that are raised into an SQS queue to be processed by the rules processor lambda.

    This is where I'm stuck. We need to extract all our current actions into a meaningful format that we can then put into a rules table for processing. Ok, easy enough for most condition types. However, where I'm stuck is for with conditions for the application type. I need to either retrieve a list of all triggers that could be associated with an application (I'm doing extraction of this data via the API, btw) OR I need to include in a custom field that is sent to the SQS queue the application name when my fire hose action is fired.

    Anyone have any ideas of how to achieve one of these outcomes? Thanks a ton in advance. I've poked and prodded all over the place and haven't found one particular way to do this.
Working...