feat: log drains rules, extends rules implementation #2059
Merged
Conversation
This file contains 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
Ziinc
changed the title
Ziinc
changed the title
hauleth
approved these changes
May 8, 2024
hauleth
approved these changes
May 9, 2024
|
extra edge case to consider for follow up PRs
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This implements drain rules, for draining events from a source to a given backend.
UI for managing rules is based on a per-backend perspective.
In the demo, we can see that ingested data from
dev.logs.up2are forwarded (evident from the rule icon) to downstream backends, and thatloadfest.test.1andloadfest.test.2are both receiving ingestion requests (there is no initial events being sent to these two sources).This demo is done with webhooks adaptor.
Screen.Recording.2024-05-08.at.6.45.49.PM.mov