Skip to content

TA-aviatrix 2.0.1: support nested Suricata EVE JSON fields - #29

Merged
cmchenr merged 2 commits into
masterfrom
fix/suricata-eve-nested-fields
Sep 11, 2026
Merged

cmchenr merged 2 commits into
masterfrom
fix/suricata-eve-nested-fields

Conversation

@cmchenr

@cmchenr cmchenr commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

The new Logstash pipeline forwards raw Suricata EVE JSON where alert, http, and flow fields 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.

  • Add search-time FIELDALIAS entries mapping alert.*, http.*, and flow.* to the flat field names used by dashboards, lookups, and CIM mappings
  • Use ASNEW instead of AS: AS removes the destination field when the nested source is absent, which wiped the flat fields on legacy pre-flattened events
  • Remove the old self-referential no-op aliases (signature AS signature, etc.)
  • Bump TA-aviatrix to 2.0.1 (app.conf, app.manifest, release notes)

Testing

  • Smoke-tested on the Splunk 9.4.7 test box: all 31 nested-EVE alerts and all 9 legacy flat events now extract severity, signature, category, severity_name, and byte counters; the Threat Detection base query went from 0 to 31 results
  • slim validate and AppInspect precert (cloud tags) pass: 0 errors, 0 failures
  • Published to Splunkbase as release 2.0.1 of app 8517 (approved for Splunk Cloud Victoria and Classic, set as default release)

🤖 Generated with Claude Code

https://claude.ai/code/session_017PmdkycgvGgL5w8UQMBYQU

cmchenr and others added 2 commits March 1, 2026 09:38
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
@cmchenr
cmchenr merged commit 92e2d93 into master Sep 11, 2026
3 checks passed
@cmchenr
cmchenr deleted the fix/suricata-eve-nested-fields branch September 11, 2026 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant