argo-alert

version number: 2.0.0 author: GRNET

Overview

Streaming Publisher of argo-streaming status events as alerts to an alerta service endpoint. Alerta mail configuration rules from gocdb contact data.

Argo streaming-service produces status events with the following schema: json { "endpoint_group":"SITE-A" "service":"SERVICE-A", "hostname":"host-A.site-A.foo" "metric":"metric-A" "status":"warning" "summary":"a warning message" "type":"metric" }

There are four types of status events: [ "endpoint_group", "service", "endpoint", "metric"]

Argo-alert connects to a kafka-topic and receives such status events. Each event is then transformed to a compatible alerta schema and gets published to an alerta service endpoint.

Alerta-mailer rule generation

Argo-alert provides the ability to create alerta-mailer rules from gocdb contact data. Argo-alert connects to a defined gocdb api endpoint and transforms the xml contact information to alerta-mailer rule json format. The rules are saved to a defined output file. The parameter use_notifications_flag (by default set to True) is used to select only the gocdb contacts that contain <NOTIFICATIONS>Y</NOTIFICATIONS> xml element. If the gocdb instance doesn't support notifications flag please set use_notifications_flag=False.

The configuration file for argo-alert provides a [gocdb] section to configure the gocdb endpoint and the required certificate parameters for access. The mail-rules parameter in [alerta] section specifies the alerta-mailer rule filename for output.

Access to gocdb api endpoint support http basic auth or certificate-based. In the case of http basic authenticaation (when in config auth_method=basic ) username and password parameters should be set in config file. In the case of certificate-based auth (when in config auth_method=cert ) hostcert and hostkey parameters should be set.

Installation / Usage

To install use pip:

$ pip install argoalert

Or clone the repo:

$ git clone https://github.com/ARGOeu/argoalert.git
$ python setup.py install

argoalert requires a configuration file with the following options: ``` [gocdb]

auth_method to be used when contacting gocdb api: basic-auth or cert

auth_method=cert

username for basic auth

username=

password for basic auth

password=

Path to godcb endpoint

api=https://gocdb-url.example.foo

Path to ca bundle folder

cabundle=/path/to/cabundle

Path to host certificate file

hostcert=/path/to/hostcert

Path to host key file

hostkey=/path/to/hostkey

Verify https requests

verify=False

Examine notification flag when selecting contacts

usenotificationsflag=True

request path for gocdb to retrieve top-level items

toprequest=/gocdbpi/public/?method=getsite

request path for gocdb to retrieve sub-level items

subrequest=/gocdbpi/public/?method=getservice

[kafka]

kafka endpoint

endpoint=localhost:9092

kafka topic

topic=metrics

[alerta]

alerta service endpoint

endpoint=http://localhost:8080

alerta environment

environment=devel

alerta token

token=s3cr3tt0ke3n

path to store the generated mail rules

mail-rules=/home/root/alerta-rules-101

extra emails to be notified

extra-emails=alert01@mail.example.foo,alert02@mail.example.foo

alert timeout is the time in seconds needed for the alert to be considered stale

aleart-timeout = 3600

group type of the tenant's top level group used in alert generation and mail template

group-type = Group

endpoint type could be set to the default: endpoint or to another type (for example: service instance)

endpoint-type = endpoint

ui-path-group is used in argo ui's result to define the correct type of group in results path

ui-path-group = SITES

report name used in argo-web-ui url construction

report = Critical

[logging]

loggin level

level = INFO

```

To run argo-alert publisher:

$ argo-alert-publisher -c /path/to/argo-alert.conf

To run argo-alert mail rule generator:

$ argo-alert-rulegen -c /path/to/argo-alert.conf

Using test-emails

For testing purposes if you want to distribute notifications using a list of your own email aliases (before using client contact emails) issue:

$ argo-alert-rulegen -c /path/to/argo-alert.conf --test-emails test01@email.foo,test02@email.foo,test03@email.foo

The rule list will be generated using the configured client sources but each client email will be replaced (using round-robin method) by a test-email (as defined in the cli arg list)

Ingore notification flag for groups (top-level)

For the special case that top level groups have different notification flag requirement the special cli parameter --group-notification-flag or -g can be used and set to true or false. For example if config file honors the use of notification flag in general but user needs to turn it of for top level groups, can issue:

$ argo-alert-rulegen -c /path/to/argo-alert.conf -g false

The rule list will be generated using the configured client sources but each client email will be replaced (using round-robin method) by a test-email (as defined in the cli arg list)

Run tests

To run argo-alert tests:

$ pytest