eliothedeman / bangarang Goto Github PK

A prerequisite for exposing config via the API

See PR #79

Add the ability to send an email for an incident. This should be created in the same style as the console and pager duty plugins.

Bangarang should have an idea of a user, so changes they make to the config can be tracked.

https://travis-ci.org/eliothedeman/bangarang/builds/68575760

Keep-alive's should be able to be assigned to any "Group by" condition.

Used as a simple sanity check to make sure that new config takes.

{
    "policy": {
        "match": {
            "host": ".*test.*"
        },
        "crit": {
            "greater": 1,
            "escalation": "test"
        }
    },
}

not

{
    "policy": {
        "match": {
            "host": ".*test.*"
        },
        "crit": {
            "greater": 1
        }
    },
    "escalation": "test"

}

github.com/constabulary/gb

All events should not be held in memory. Only pull events out of memory when a new event comes in that matches it's index name signature.

The cancel button doesn't work when in the add new escalation page.

Using Chrome Version 48.0.2564.97 (64-bit) on Ubuntu 15.10.

Example match on host == /(?P.my.fqdn/

Support annotations by creating graphite metrics with this form http://docs.grafana.org/reference/annotations/

What software license is this available under?

The inputs should be plugin based, just as the outputs are.