The Open Distro for Elasticsearch Alerting enables you to monitor your data and send alert notifications automatically to your stakeholders. With an intuitive Kibana interface and a powerful API, it is easy to set up, manage, and monitor your alerts. Craft highly specific alert conditions using Elasticsearch's full query language and scripting capabilities.

Scheduled searches use cron expressions or intervals (e.g. every five minutes) and the Elasticsearch query DSL.

To define trigger conditions, use the Painless scripting language or simple thresholds (e.g. count > 100).

When trigger conditions are met, you can publish messages to the following destinations:

• Slack
• Custom webhook
• Amazon Chime

Messages can be static strings, or you can use the Mustache templates to include contextual information.

Please see our documentation.

1. Check out this package from version control.
2. Launch Intellij IDEA, choose Import Project, and select the settings.gradle file in the root of this package.
3. To build from the command line, set JAVA_HOME to point to a JDK >= 12 before running ./gradlew.

This package is organized into subprojects, most of which contribute JARs to the top-level plugin in the alerting subproject.

All subprojects in this package use the Gradle build system. Gradle comes with excellent documentation that should be your first stop when trying to figure out how to operate or modify the build.

However, to build the alerting plugin subproject, we also use the Elastic build tools for Gradle. These tools are idiosyncratic and don't always follow the conventions and instructions for building regular Java code using Gradle. Not everything in alerting will work the way it's described in the Gradle documentation. If you encounter such a situation, the Elastic build tools source code is your best bet for figuring out what's going on.

1. ./gradlew build builds and tests all subprojects.
2. ./gradlew :alerting:run launches a single node cluster with the alerting plugin installed.
3. ./gradlew :alerting:integTest launches a single node cluster with the alerting plugin installed and runs all integ tests.
4. ./gradlew :alerting:integTest --tests="**.test execute foo" runs a single integ test class or method (remember to quote the test method name if it contains spaces).

When launching a cluster using one of the above commands, logs are placed in alerting/build/cluster/run node0/elasticsearch-<version>/logs. Though the logs are teed to the console, in practices it's best to check the actual log file.

Sometimes it's useful to attach a debugger to either the Elasticsearch cluster or the integ tests to see what's going on. When running unit tests, hit Debug from the IDE's gutter to debug the tests. To debug code running in an actual server, run:

./gradlew :alerting:integTest --debug-jvm # to start a cluster and run integ tests

OR

./gradlew :alerting:run --debug-jvm # to just start a cluster that can be debugged

The Elasticsearch server JVM will launch suspended and wait for a debugger to attach to localhost:8000 before starting the Elasticsearch server.

To debug code running in an integ test (which exercises the server from a separate JVM), run:

./gradlew -Dtest.debug :alerting:integTest 

The test runner JVM will start suspended and wait for a debugger to attach to localhost:5005 before running the tests.

Sometimes you need to launch a cluster with more than one Elasticsearch server process. The startMultiNodeXX tasks can help. There are two ways to use them:

If you need a multi-node cluster where all nodes are started together, use:

./gradlew -PnumNodes=2 startMultiNode ... # to launch 2 nodes

Remember to manually kill the nodes when you're done.

If you need a multi-node cluster where you'd like to be able to add and kill each node independently, use:

./gradlew startMultiNode1 
./gradlew startMultiNode2
... and so on

Just like option 1, remember to manually kill the nodes when you're done.

This project has adopted an Open Source Code of Conduct.

If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our vulnerability reporting page. Please do not create a public GitHub issue.

See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.

Copyright 2019 Amazon.com, Inc. or its affiliates. All Rights Reserved.