Skip to content

Latest commit

 

History

History
159 lines (125 loc) · 4.09 KB

usergroups.md

File metadata and controls

159 lines (125 loc) · 4.09 KB
Raw

User Groups

BGPalerter supports user groups. With user groups you can:

  • Notify only specific users about specific prefixes.
  • Notify only specific users about specific type of alerts.

By default, BGPalerter creates two user groups noc and default (since v1.27.0).

  • The noc user group receives only alerts related to the BGP monitoring. Even if set by default, this user group is optional.
  • The default user group receives administrative and error communications. Additionally, it receives all the alerts that could not be dispatched to any other specific user group. This group is mandatory, and it MUST be set for all the report modules.

You can create how many user groups you wish, for example to monitor resources of your customers and forward them the alerts about their resources without sending them administrative communications.

User groups can be specified directly in the report configuration on in an external yaml file. Using an external file allows BGPalerter to auto-reload the user group definitions when the external file is changed.

Notify only specific users about specific prefixes

Example of configuration.

In prefixes.yml you can associate different groups to different resources.

165.254.225.0/24:
  description: my description 1
  asn: 2914
  ignoreMorespecifics: false
  ignore: false
  group: group1
 
165.254.255.0/24:
  description: my description 2
  asn: 2914
  ignoreMorespecifics: false
  ignore: false
  group: group1
 
192.147.168.0/24:
  description: my description 3
  asn: 15562
  ignoreMorespecifics: false
  ignore: false
  group: group2


options:
  monitorASns:
    2914:
      group: group1
    15562:
      group: group2

In config.yml you have to specify the groups in the report modules.

reports:
  - file: reportEmail
    channels:
      - hijack
      - newprefix
    params:
      notifiedEmails:
        default:
          - admin@org.com
        group1:
          - joh@example.com
          - max@example.com
        group2:
          - al@org.net

 - file: reportSlack
   channels:
     - hijack
     - newprefix
   params:
      hooks:
        default: _SLACK_WEBOOK_FOR_ADMIN_
        group1: _SLACK_WEBOOK_FOR_GROUP1_
        group2: _SLACK_WEBOOK_FOR_GROUP2_

Notify only specific users about specific type of alerts

It's essentially the same configuration of above, except you have to duplicate report components, each serving a subset of the channels.

 - file: reportSlack
   channels:
     - hijack
   params:
      hooks:
        default: _SLACK_WEBOOK_FOR_ADMIN_
        group1: _SLACK_WEBOOK_FOR_GROUP2_

 - file: reportSlack
   channels:
     - newprefix
   params:
      hooks:
        default: _SLACK_WEBOOK_FOR_ADMIN_
        group2: _SLACK_WEBOOK_FOR_GROUP1_

You can also split the notification across different reporting mechanism based on their type.

reports:
  - file: reportEmail
    channels:
      - newprefix
    params:
      notifiedEmails:
        default:
          - admin@org.com
        group1:
          - joh@example.com
          - max@example.com

 - file: reportSlack
   channels:
     - hijack
   params:
      hooks:
        default: _SLACK_WEBOOK_FOR_ADMIN_
        group2: _SLACK_WEBOOK_FOR_GROUP2_

User groups associated to prefixes have always precedence on user groups associated to ASes. If an alert matches both a prefix rule and an AS rule, the prefix rule will define which user group will receive the alert.

Define an external user groups file

Edit config.yml, uncomment the groupsFile option, and add the position of the file (e.g., groupsFile: groups.yml).

Create the user groups file as follows:

report_module_name1:
   user_group_to_define:
      list_of_contacts

report_module_name2:
  user_group_to_define:
    list_of_contacts

The format of the list of contacts depends on the report_module (e.g., emails for reportEmail, urls for reportHTTP).

For example, for reportEmail:

reportEmail:
   myGroup:
      example@example.it

In the repo there is a config.yaml.example file that you can use.

It the file is changed, BGPalerter will auto-reload the user groups.