Multiple Event Types: Real FortiGate Traffic and Threat Logs
English narration and permanently visible English captions accompany this recording of the October 31, 2026 Parser Studio Web UI. The examples come from published original manufacturer documentation or upstream-authored test fixtures, not from fabricated demo messages. Watch in a dedicated video player · Download MP4 · English SRT captions · Read the English transcriptPractice along with the video
Keep this page open to pause or replay the demonstration while working in a second tab. Before you begin: Download all practice samples as a ZIP · Open Parser Studio Use the source files above exactly as shown in the video. Each file contains the public documented sample events used during the recording, with source attribution and SHA-256 checksums in the ZIP bundle.Copy the exact logs used in the video
Use the copy icon on each code block, then paste the entire content into Parser Studio. Each line is one unmodified event from the published source. Do not omit difficult events or replace values to force a passing result.Traffic group — copy both FortiGate Traffic events
Exact source: 1745 bytes · File:04-fortigate-traffic.log · Keep both lines when the file has two events.
Threat group — copy the Web Filter and IPS events
Exact source: 1373 bytes · File:04-fortigate-threat.log · Keep both lines when the file has two events.
Follow the current on-screen steps
- Open Auto Parser, enter manufacturer Fortinet and product FortiGate.
- Choose Add Another Log Type. Name the two groups Traffic and Threat, preserving two published source events in each group.
- Click Analyze Logs and check all four events; the recorded source review returned 4 of 4 log events parsed completely.
- In Review Fields, inspect event-specific values for Traffic, Web Filter and IPS. Continue to Map Fields and verify each mapping against the actual source.
- If the product accepts the shared parser draft, proceed to Create Parser, run Run Final Test & Create Files, then download and review the package. A successful sample test cannot prove all FortiGate event shapes.
Video chapter timestamps (October 31 recording)
The listed times come from the actual October 31 recording, not the retired version.
Expected review outcome
Four original Fortinet documentation log examples parse completely in one project. The final four-event test and package generation pass. Do not treat successful source extraction or generated files as evidence of full vendor/firmware coverage, target import acceptance, or live Stellar Cyber deployment compatibility.Recovery path
For a different log shape, keep the original records and examine the highlighted source spans, following the related workflow. Only apply additional parsing rules after different examples pass a separate regression test. Never delete failing events merely to obtain a passing total.Original log provenance
The published traffic and web-filter records share a session ID. These example logs are not claimed to be from a physical appliance independently inspected in this video.Customer logs may include private information. Review, sanitize and manually approve any excerpt before copying it into an external ChatGPT conversation. The Auto Parser does not automatically share those logs.