Check routing
First check that the hostname points to HotWall and the website is connected. Requests that bypass the protection edge cannot appear in HotWall analytics. DNS changes may be cached; compare the current answer with the connection instructions and retry the DNS check.
Use the reports
Choose a supported time range and inspect traffic, security events, action and category filters. Request-level history is limited; older events may no longer be available. A total and a filtered event list can differ because they describe different subsets.
Adjust safely
Inspect the relevant managed or custom rule and the request details before changing an action. Test with a narrow condition and check the resulting events. If the origin is unreachable, check the configured backend address, protocol, port and firewall access for HotWall.