Add cribl integration package #8487
Merged
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.
Proposed commit message
This PR adds the first phase of the new Cribl integration.
This integration is unique in that it 1) has no input to run, since Cribl pushes data directly to elasticsearch via the _bulk API via their elasticsearch output, and 2) it doesn't really have its own pipeline, since the goal is to utilize existing integration's pipelines. It enables users to utilize the
rerouteprocessor to 'forward' logs from Cribl to a specific integration's datastream.This first phase contains mostly documentation on how to set everything up using a custom pipeline. The second phase will contain a more elegant UI so that users can have a simpler experience configuring.
Checklist
I have verified that all data streams collect metrics or logs.changelog.ymlfile.Author's Checklist
How to test this PR locally
The steps to set everything up are documented in the integration's README
Then I just utilized the _bulk API (since that's what the cribl output uses) to verify the routing works
Related issues
Screenshots
Integration main view
Instructions