FAZ 7.6.2 - VPN Report Broken After Upgrade (No Matching Log Data)
Hey everyone
Thanks in advance for any help you can provide.
I recently upgraded my company's FortiAnalyzer (FAZ) to 7.6.2, and a custom VPN connection/disconnection report used by my manager has broken. While the report is custom, it was originally based on a Fortinet employee’s article.
After logging a support case, I was informed that because this is a custom report, I need to resolve the issue myself.
What I’ve Found So Far
- I found a Reddit post where another user experienced similar issues after the FAZ backend switched from PostgreSQL to ClickHouse.
- I followed the Fortinet ClickHouse migration documentation and updated my SQL query accordingly.
- The data appears correctly when previewing the dataset, and it also shows up in chart previews.
- However, when I generate the report, it comes out blank with the message:
:police_car_light:"No matching log data for this report"
My Current SQL Query
SELECT
`user` AS "User",
(
CASE
WHEN `action` = 'tunnel-up' THEN 'Connected'
ELSE 'Disconnected'
END
) AS "VPN Status",
$calendar_time(itime) AS `Time Stamp`
FROM
$log
WHERE
$filter
AND (
(`action` = 'tunnel-up')
OR (`action` = 'tunnel-down`)
)
GROUP BY
`Time Stamp`,
`action`,
`user`
ORDER BY
`user`,
`Time Stamp`
Questions for the Community
- Has anyone else faced this issue after upgrading to FAZ 7.6.x?
- Are there any known issues with ClickHouse affecting FAZ report generation?
- Is there a workaround to get this report working again?
Any help or insight would be greatly appreciated!
Thanks
Heath
