Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(alerta-service): Add custom severities to Alerta handler #2584

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Commits on Jun 17, 2021

  1. feat(alerta-service): Add custom severities to Alerta handler

    Fix influxdata#2056
    
    This commit allows usage of all or some Alerta Severities. It provides two keywords to fine tune kapacitor built-in severities.
    
    1. First, you can rename kapacitor serverity levels: crit, warn, info, ok to any other severities configured in your Alerta:
    
        |alert()
            // ...
            .alerta()
                // ...
                .renameSeverity('crit', 'major')
                .renameSeverity('info', 'notice')
    
    I suppose this will cover most of the cases. But if you do want a lot of severity levels:
    
    2. You can add custom severity levels, which will be avaluated on Alerta handler level after built-in alert was triggered.
    
        |alert()
            // ...
            .warn(lambda: "cpu" > 50)
            .alerta()
                // ...
                .addSeverity('minor', 3, lambda: "cpu" > 60)
                .addSeverity('major', 2, lambda: "cpu" > 70)
                .addSeverity('critical', 1, lambda: "cpu" > 80)
                .addSeverity('fatal', 0, lambda: "cpu" > 90)
    
    Note: evaluation of addSeverity condition only happen after build-in alert is triggered, so you need some entry point (like .warn() in exmple), which should cover all range of values interesting to you.
    Note: this severities use Alerta's code order - higher severity has lower code (0 for fatal, 9 for ok)
    Note: .addSeverity() is quite useless in combination with .stateChangesOnly(), but Alerta has decent deduplication mechanism, so it shouldn't be a problem
    sp1r committed Jun 17, 2021
    Configuration menu
    Copy the full SHA
    a7c1fa8 View commit details
    Browse the repository at this point in the history