Repository navigation
docs(integrations): document the Kibana webhook body and workload matching - #869
Open
mayankpande88 wants to merge 1 commit into
Open
mayankpande88 wants to merge 1 commit into
mayankpande88 wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request significantly expands the documentation for the Elasticsearch/Kibana webhook integration, adding detailed steps for creating the connector, configuring rule actions with a JSON payload, and explaining workload resolution. It also updates the troubleshooting table with more specific scenarios. The feedback suggests correcting the spelling of 'behaviour' to 'behavior' to maintain consistent US English throughout the documentation.
…ching The Elasticsearch / Kibana webhook page told readers to point a connector at the URL but never gave the JSON body a Kibana webhook action has to send. Kibana has no default body, so every reader had to guess one. The page now gives the body for the firing and the recovered action, a table of what each field does, how the rule's group values are matched to a workload, when a namespace or workload label is needed, and why a link only appears when server.publicBaseUrl is set. Signed-off-by: mayankpande88 <[email protected]>
mayankpande88
force-pushed
the
docs/elasticsearch-webhook-connector-body
branch
from
October 7, 2026 14:48
df92d2c to
4e78620
Compare
mayankpande88
marked this pull request as ready for review
October 8, 2026 04:38
RamanKharchee
approved these changes
Oct 8, 2026
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
2 participants
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.
Description
Summary
The Elasticsearch / Kibana webhook page told readers to point a connector at the URL but never gave the JSON body a Kibana webhook action has to send. Kibana has no default body, so every reader had to guess one.
The page now gives:
server.publicBaseUrlis setThe matching behavior described here ships in an upcoming server release; the page says what older releases do.
Type of change
How Has This Been Tested?
Open the Elasticsearch / Kibana Webhook page in a local build of the site: Step 2 shows the JSON body, the field table and the workload matching rules, and both notes render.
Checklist
npm run buildlocally and the site builds without errorsnpm run lintlocally and lint passesgit commit -s)Local e2e: n/a — documentation only; the site build and lint pass.