- Kotlin 96.7%
- Java 3.2%
c54ea21834* Declare jackson-core/annotations as direct deps to fix non-deterministic compile The build only force()d com.fasterxml.jackson.core:jackson-core and jackson-annotations, but a resolutionStrategy force overrides the version of a dependency already in the graph -- it does not add one. jackson-databind is a direct dependency, but jackson-core/annotations were only present transitively. When building against the moving OpenSearch 3.x snapshot that pulls Jackson 3 (tools.jackson), the com.fasterxml jackson-core can be evicted from the compile classpath, making the supertypes of jackson-databind types (TreeNode, ObjectCodec, Versioned) inaccessible and breaking :alerting:compileKotlin non-deterministically (InputService.kt, PPLUtils.kt, TriggerService.kt). Declare jackson-core and jackson-annotations as direct implementation dependencies (aligned with jackson-databind) so they are always on the classpath. Fixes #2227. Signed-off-by: Darshit Chanpura <dchanp@amazon.com> * Pin httpcore5 to resolve conflicting versions from 3.x snapshot deps After the jackson-core fix lets :alerting:compileKotlin succeed, the build then fails resolving runtimeClasspath: opensearch-remote-metadata-sdk requires httpcore5:5.4.3 while opensearch-rest-client requires httpcore5:5.4, and Gradle cannot reconcile them ('Conflict found for module httpcore5 between 5.4.3 and 5.4'). Force httpcore5 and httpcore5-h2 to 5.4.3 so the build resolves deterministically against the moving 3.x snapshot. Verified locally with ':alerting:assemble --refresh-dependencies'. Signed-off-by: Darshit Chanpura <dchanp@amazon.com> --------- Signed-off-by: Darshit Chanpura <dchanp@amazon.com> |
||
|---|---|---|
| .github | ||
| alerting | ||
| build-tools | ||
| core | ||
| docs | ||
| gradle/wrapper | ||
| release-notes | ||
| sample-remote-monitor-plugin | ||
| scripts | ||
| spi | ||
| worksheets | ||
| .codecov.yml | ||
| .editorConfig | ||
| .gitignore | ||
| .whitesource | ||
| build.gradle | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| DEVELOPER_GUIDE.md | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE.txt | ||
| MAINTAINERS.md | ||
| NOTICE.txt | ||
| README.md | ||
| RELEASING.md | ||
| SECURITY.md | ||
| settings.gradle | ||
| THIRD-PARTY | ||
- OpenSearch Alerting
- Highlights
- Documentation
- Contributing
- Code of Conduct
- Security
- License
- Copyright
OpenSearch Alerting
The OpenSearch Alerting enables you to monitor your data and send alert notifications automatically to your stakeholders. With an intuitive OpenSearch Dashboards 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.
Highlights
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.
Documentation
Please see our documentation.
Contributing
See developer guide and how to contribute to this project.
Code of Conduct
This project has adopted the Amazon Open Source Code of Conduct. For more information see the Code of Conduct FAQ, or contact opensource-codeofconduct@amazon.com with any additional questions or comments.
Security
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.
License
This project is licensed under the Apache v2.0 License.
Copyright
Copyright OpenSearch Contributors. See NOTICE for details.