Add observability alerts for chargeback integration #16205
Conversation
- Add two ES|QL alerting rules: detect new chargeback groups and detect deployments missing usage data - Add comprehensive documentation for alert setup and configuration - Update Elasticsearch version requirement to 9.2.0+ for smart lookup join support - Add transform startup and monitoring instructions to README
There was a problem hiding this comment.
Pull request overview
This PR adds observability alerting capabilities to the chargeback integration and updates documentation to clarify setup requirements and procedures. The changes enhance monitoring of chargeback data quality and provide comprehensive guidance for users setting up the integration.
Key changes:
- Addition of two ES|QL alert rule templates for detecting new chargeback groups and missing usage data
- Comprehensive documentation updates including transform startup instructions, deployment group configuration, and alert setup procedures
- Elasticsearch version requirement update from 8.18.0+ to 9.2.0+ for smart lookup join support
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| packages/chargeback/manifest.yml | Version bump to 0.2.7 |
| packages/chargeback/elasticsearch/transform/**/transform.yml | Pipeline version updates to match new package version |
| packages/chargeback/docs/README.md | Major documentation expansion with alert templates, transform instructions, and clarified requirements |
| packages/chargeback/changelog.yml | Changelog entry for version 0.2.7 with corrected historical entry types |
| packages/chargeback/_dev/build/docs/README.md | Generated documentation file mirroring README.md changes |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
andrewkroh
added
the
documentation
sholzhauer-es
left a comment
sholzhauer-es
left a comment
There was a problem hiding this comment.
LGTM, good improvements to the readme!
| All configuration values can be updated via the configuration lookup index: | ||
|
|
||
| ``` | ||
| POST chargeback_conf_lookup/_update/config |
There was a problem hiding this comment.
This only works if there is a single record. If you have multiple the doc id used needs to change.
There was a problem hiding this comment.
Good point. will update it.
💔 Build Failed
Failed CI StepsHistory
|
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots