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

Allow for multiple alert handlers of the same type #120

Merged
merged 1 commit into from
Dec 23, 2015
Merged

Conversation

nathanielc
Copy link
Contributor

Fixes #118

With this change each alert handler is appropriately scoped so you do not have to worry about name conflicts. You can now add multiple handlers of the same type.

For example:

stream
    .from().measurement('cpu')
    .where(lambda: "host" == 'serverA')
    .groupBy('host')
    .window()
        .period(10s)
        .every(10s)
    .mapReduce(influxql.count('idle'))
    .alert()
        .id('kapacitor/{{ .Name }}/{{ index .Tags "host" }}')
        .info(lambda: "count" > 6.0)
        .warn(lambda: "count" > 7.0)
        .crit(lambda: "count" > 8.0)
        .slack()
            .channel('#alerts')
        .slack()
            .channel('@jim')

@nathanielc
Copy link
Contributor Author

Wait to merge this until after #113 so that we can rebase and integrate OpsGenie in the same way.

@nathanielc nathanielc force-pushed the nc-issue#118 branch 2 times, most recently from a068125 to 1c4b4a6 Compare December 23, 2015 22:20
update alert docs and tickdoc for new doc structure
nathanielc pushed a commit that referenced this pull request Dec 23, 2015
Allow for multiple alert handlers of the same type
@nathanielc nathanielc merged commit 85c6c2d into master Dec 23, 2015
@nathanielc nathanielc deleted the nc-issue#118 branch December 23, 2015 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant