在线时间:8:00-16:00
迪恩网络APP
随时随地掌握行业动态
扫描二维码
关注迪恩网络微信公众号
开源软件名称(OpenSource Name):opendistro-for-elasticsearch/alerting开源软件地址(OpenSource Url):https://github.com/opendistro-for-elasticsearch/alerting开源编程语言(OpenSource Language):Kotlin 91.6%开源软件介绍(OpenSource Introduction):Open Distro for Elasticsearch AlertingThe 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. HighlightsScheduled 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. DocumentationPlease see our documentation. Setup
BuildThis 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 Building from the command line
When launching a cluster using one of the above commands, logs are placed in Run integration tests with Security enabled
DebuggingSometimes 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:
OR
The Elasticsearch server JVM will launch suspended and wait for a debugger to attach to To debug code running in an integ test (which exercises the server from a separate JVM), run:
The test runner JVM will start suspended and wait for a debugger to attach to 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
Advanced: Launching multi-node clusters locallySometimes you need to launch a cluster with more than one Elasticsearch server process. You can do this by running You can also run the integration tests against a multi-node cluster by running 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 Code of ConductThis project has adopted an Open Source Code of Conduct. Security issue notificationsIf 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. LicensingSee the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution. CopyrightCopyright 2019 Amazon.com, Inc. or its affiliates. All Rights Reserved. |
2023-10-27
2022-08-15
2022-08-17
2022-09-23
2022-08-13
请发表评论