Add companion notebook for Alerts as data: investigating alert storms with ES|QL - #594
Open
Delacrobix wants to merge 2 commits into
Open
Add companion notebook for Alerts as data: investigating alert storms with ES|QL#594Delacrobix wants to merge 2 commits into
Delacrobix wants to merge 2 commits into
Conversation
Builds the payments lab, replays two incidents, runs the three ES|QL investigation queries, and registers the Alert Historian agent.
|
Found 1 changed notebook. Review the changes at https://app.gitnotebooks.com/elastic/elastic-labs/pull/594 |
Delacrobix
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion notebook for the Observability Labs article Alerts as data: investigating alert storms with ES|QL.
It builds the payments lab, replays two incidents with the gateway rule retuned in between, runs the three ES|QL investigation queries against
.alerts-*, and registers the Alert Historian agent and its three tools. Runs for about 25 minutes because the rules evaluate once a minute; the last cell deletes everything it created. Includes.env.exampleand the OTel Collector configuration undersupporting-blog-content/observability-labs/alerts-as-data-log-derived-signals-v2/.Related article PR: https://github.com/elastic/observability-labs/pull/987