Repository navigation
TA-aviatrix 2.0.1: support nested Suricata EVE JSON fields - #29
Merged
Merged
Conversation
Splunkbase's SLIM validator has an outdated splunk-releases.json that only knows versions up to 8.0.0, causing any version spec (>=8.0, >=9.0, >=9.0.0) to fail validation. Setting platformRequirements to null bypasses this broken check while still allowing proper distribution. Version compatibility is declared on Splunkbase's release information page instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The new Logstash pipeline forwards raw Suricata EVE JSON where alert, http, and flow fields are nested objects, while the TA and dashboards expected the previously flattened top-level names. Add search-time FIELDALIAS entries mapping alert.*, http.*, and flow.* to the flat field names used by dashboards, lookups, and CIM mappings. ASNEW is required instead of AS: AS removes the destination field when the nested source is absent, which wiped flat fields on legacy pre-flattened events. Published to Splunkbase as release 2.0.1 (app 8517). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017PmdkycgvGgL5w8UQMBYQU
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
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
The new Logstash pipeline forwards raw Suricata EVE JSON where
alert,http, andflowfields are nested objects, while the TA and the aviatrix-security dashboards expected the previously flattened top-level names (signature,severity,category, ...). Events indexed fine but every Threat Detection panel filtered them out.FIELDALIASentries mappingalert.*,http.*, andflow.*to the flat field names used by dashboards, lookups, and CIM mappingsASNEWinstead ofAS:ASremoves the destination field when the nested source is absent, which wiped the flat fields on legacy pre-flattened eventssignature AS signature, etc.)Testing
severity,signature,category,severity_name, and byte counters; the Threat Detection base query went from 0 to 31 resultsslim validateand AppInspect precert (cloud tags) pass: 0 errors, 0 failures🤖 Generated with Claude Code
https://claude.ai/code/session_017PmdkycgvGgL5w8UQMBYQU