📟 Open Distro for Elasticsearch Alerting Plugin
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:
Messages can be static strings, or you can use the Mustache templates to include contextual information.
Please see our documentation.
settings.gradlefile in the root of this package.
JAVA_HOMEto point to a JDK >= 14 before running
This package is organized into subprojects, most of which contribute JARs to the top-level plugin in the
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
alertingplugin 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
alertingwill 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.
./gradlew buildbuilds and tests all subprojects.
./gradlew :alerting:runlaunches a single node cluster with the alerting plugin installed.
./gradlew :alerting:run -PnumNodes=3launches a multi-node cluster with the alerting plugin installed.
./gradlew :alerting:integTestlaunches a single node cluster with the alerting plugin installed and runs all integ tests.
./gradlew :alerting:integTest -PnumNodes=3launches a multi-node cluster with the alerting plugin installed and runs all integ tests.
./gradlew :alerting:integTest -Dtests.class="*MonitorRunnerIT"runs a single integ test class
./gradlew :alerting:integTest -Dtests.method="test execute monitor with dryrun"runs a single integ test 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/testclusters/integTest-0/logs/. Though the logs are teed to the console, in practices it's best to check the actual log file.
./gradlew :alerting:integTestRunner -Dtests.rest.cluster=localhost:9200 -Dtests.cluster=localhost:9200 -Dtests.clustername=es-integrationtest -Dhttps=true -Dsecurity=true -Duser=admin -Dpassword=admin
./gradlew :alerting:integTestRunner -Dtests.rest.cluster=localhost:9200 -Dtests.cluster=localhost:9200 -Dtests.clustername=es-integrationtest -Dhttps=true -Dsecurity=true -Duser=admin -Dpassword=admin --tests "com.amazon.opendistroforelasticsearch.alerting.MonitorRunnerIT.test execute monitor returns search result"
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. You must start your debugger to listen for remote JVM before running the below commands.
To debug code running in an actual server, run:
./gradlew :alerting:integTest -Dcluster.debug # to start a cluster and run integ tests
./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:5005before starting the Elasticsearch server. The IDE needs to listen for the remote JVM. If using Intellij you must set your debug configuration to "Listen to remote JVM" and make sure "Auto Restart" is checked. You must start your debugger to listen for remote JVM before running the commands.
To debug code running in an integ test (which exercises the server from a separate JVM), run:
./gradlew :alerting:integTest -Dtest.debug
The test runner JVM will start suspended and wait for a debugger to attach to
localhost:8000before running the tests.
Additionally, it is possible to attach one debugger to the cluster JVM and another debugger to the test runner. First, make sure one debugger is listening on port
5005and the other is listening on port
8000. Then, run:
./gradlew :alerting:integTest -Dtest.debug -Dcluster.debug
Sometimes you need to launch a cluster with more than one Elasticsearch server process.
You can do this by running
./gradlew :alerting:run -PnumNodes=
You can also run the integration tests against a multi-node cluster by running
./gradlew :alerting:integTest -PnumNodes=
You can also debug a multi-node cluster, by using a combination of above multi-node and debug steps. But, you must set up debugger configurations to listen on each port starting from
5005and increasing by 1 for each node.
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.