Suricata EVE alert

Suricata EVE alert. EVE JSON emits typed records from the Suricata network engine.

Source and collection

Configured eve-log output, commonly eve.json.

Record Suricata version, enabled EVE types, ruleset and IDS versus inline IPS mode.

Native example and provenance

publisher documentation example. Published example; no independent capture provenance claimed.

Original publisher / pinned upstream fixture — preformatted example 1

One complete record selected; values unchanged.

Download the exact sample · Offline research kit

SHA-256: 26eb8c360e9a53fd6fd3b8e2d559f98953b1cf44263bc552375809297c4e95c0

{
  "timestamp": "2017-04-07T22:24:37.251547+0100",
  "flow_id": 586497171462735,
  "pcap_cnt": 53381,
  "event_type": "alert",
  "src_ip": "192.168.2.14",
  "src_port": 50096,
  "dest_ip": "209.53.113.5",
  "dest_port": 80,
  "proto": "TCP",
  "metadata": {
    "flowbits": [
      "http.dottedquadhost"
    ]
  },
  "tx_id": 4,
  "alert": {
    "action": "allowed",
    "gid": 1,
    "signature_id": 2018358,
    "rev": 10,
    "signature": "ET HUNTING GENERIC SUSPICIOUS POST to Dotted Quad with Fake Browser 1",
    "category": "Potentially Bad Traffic",
    "severity": 2
  },
  "app_proto": "http"
}

Structure and field interpretation

Observed structure in this specific sample
Field/path	Serialized type
`timestamp`	str
`flow_id`	int
`pcap_cnt`	int
`event_type`	str
`src_ip`	str
`src_port`	int
`dest_ip`	str
`dest_port`	int
`proto`	str
`metadata.flowbits`	array
`metadata.flowbits[0]`	str
`tx_id`	int
`alert.action`	str
`alert.gid`	int
`alert.signature_id`	int
`alert.rev`	int
`alert.signature`	str
`alert.category`	str
`alert.severity`	int
`app_proto`	str

event_type: Selects the payload schema.
flow_id: Flow correlation identifier; preserve numeric precision.
timestamp: Event time with offset.
alert: Rule-match context when present.

Investigation uses

Correlate flow_id and event_type with related protocol and alert records.
For alerts, review signature, action and packet context before assigning a verdict.

Validation boundaries

An alert is a rule match, not independently confirmed compromise. Fields and nested structures differ by event type and version.

This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.

For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.

Ecosystem connections

References

15.1.2. Eve JSON Format — Suricata 9.0.0-dev documentation

Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.