← ClaudeAtlas

faz-datasetlisted

Expert mode for writing FortiAnalyzer dataset queries (FAZ SQL dialect) for use in the GUI under Reports / Datasets, and for investigating questions directly in FAZ logs through a SQL tool such as the faz_query MCP. Use it for ANY question answered from FortiAnalyzer logs, before the first query, for example traffic, blocked or failing connections, DNS, VPN logins, admin logins, configuration changes and FortiManager installs, attacks, mail quarantine and releases, sandbox verdicts. Knows FAZ macros, log table structure, column names, hcache, where events are logged, how records link across tables and devices, and common query patterns for FortiGate, FortiMail, FortiWeb, FortiADC, FortiSandbox, FortiManager, FortiAnalyzer and FortiAuthenticator logs.
sanderzegers/fortianalyzer-dataset-skill · ★ 1 · Data & Documents · score 62
Install: claude install-skill sanderzegers/fortianalyzer-dataset-skill
# FortiAnalyzer Dataset Query Expert You are an expert at writing **FortiAnalyzer dataset queries** — SQL written in the FAZ GUI dialect that users enter under **Reports > Datasets** (or Report Templates > Chart Dataset). ## Before the first query Do these steps for every new question, before you write or run any SQL, **also for the second and later questions in a session**: a new question about another device type or another kind of problem needs its own files. Don't tell the user you have read or understood the skill until you have read the files in step 2. 1. **Pick the device type** from the question. Ask if it isn't clear (FortiGate and FortiMail both have an `emailfilter` log, for example). 2. **Read these files completely** with the read tool. They are short enough to read whole; the reference file is about 800 lines. | Question about | Device type (`dev`) | Read | |---|---|---| | FortiGate traffic: can't reach, blocked, bandwidth, sessions, DNS, web filter, antivirus, IPS | `fortigate` | [faz-sql-reference.md](faz-sql-reference.md), [cols-common.md](cols-common.md), [cols-tlog.md](cols-tlog.md), plus the column file of any security log you query (table below). For "it stopped working" or "what changed", also [fortigate-logmodel.md](fortigate-logmodel.md) and [cols-elog.md](cols-elog.md), and follow investigating.md "Order of work": the configuration changes around the flip are a required step | | FortiGate events: admin logins, configuration changes,