🔥 Realtime Data Enrichment - add get_enrichment_table_record fn to VRL log transform pipeline #111
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
This was
linked to
issues
Mar 8, 2023
lib/java/matano/iceberg_main/src/main/kotlin/com/matano/iceberg/AthenaUtil.kt
Outdated
Show resolved
Hide resolved
lib/java/matano/iceberg_main/src/main/kotlin/com/matano/iceberg/Enrichment.kt
Outdated
Show resolved
Hide resolved
…L log transform pipeline
Samrose-Ahmed
approved these changes
Mar 8, 2023
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.
Summary
This pull request introduces support for real-time data enrichment in Matano during ingest, addressing #99 and #21. The new
get_enrichment_table_recordfunction has been added to the VRL log transform pipeline, enabling retrieval of enrichment data and adding it to the incoming data stream in real-time, before the detection / lake writing steps.For many use cases, this feature means users no longer need to perform manual JOINS in their queries or do manual lookups in their detection rules and improves downstream analytics performance by providing pre-joined/enriched records in the data lake and detection engine.
Up next
Next step, will be to add extend support to GeoIP enrichment tables (MaxMind), which will require special handling logic.