###################################################
##
## Alertmanager YAML configuration for routing.
##
## Will route alerts with a code_owner label to the slack-code-owners receiver 
## configured above, but will continue processing them to send to both a
## central Slack channel (slack-monitoring) and PagerDuty receivers
## (pd-warning and pd-critical)
##

routes:
  ###################################################
  ## Duplicate code_owner routes to teams
  ## These will send alerts to team channels but continue
  ## processing through the rest of the tree to handled by on-call
  - match_re:
      code_owner: '.+'
    routes:
      - match: {severity: info|warning|critical}
        continue: true
        receiver: slack-code-owners

  ###################################################
  ## Standard on-call routes
  - match_re:
      severity: info|warning|critical
    receiver: slack-monitoring
    continue: true


  ###################################################
  ## Pagerduty routes
  - match: {severity: warning}
    routes:
    - receiver: pd-warning
  - match: {severity: critical}
    routes:
    - receiver: pd-critical