Skip to content →
Log in

Reports

Review fixed-window activity and create permitted exports.

Use Reports to see what happened in your tenant over a fixed window and to generate files for people who do not use the console. The page description reads “What happened in this tenant, and files for people not in the console.” It is not the live searchable event stream.

Before you start#

  • You need at least one of devices:view, gateways:view, services:view, policies:view, content_filtering:view, firewall:view or audit:view. Otherwise you see “You don’t have permission to view reports. Contact your administrator for access.”
  • Each section is gated by its own permission. Sections you cannot see are never fetched.
  • The Activity window applies to event-backed cards. Device and gateway counts, and the posture snapshot, show current state and ignore the window.
  • The Secure Web card shows HTTP decisions only while Inspect web traffic is on in Secure Web settings.

Review activity#

  1. Open Reports. The Activity tab is selected by default.
  2. Choose a window: 1h, 24h, 7d or 30d. The default is 24h.
  3. Read the header chips: “{n} of {m} devices connected” and “{n} of {m} gateways online”.
  4. Read the spark cards: Audit entries, Access blocks and Secure Web blocks. Each shows a count with a sparkline and links to the matching page.
  5. Read the view cards. Each shows a window chip and “Exportable: yes” or “Exportable: no”.
  6. Follow a link such as View analytics, View access audit, View devices or View audit log when you need individual evidence.

You should see counts for the window and, for Device posture, a bar split into Compliant, Non-compliant and Unknown.

Reports Activity tab on the 7d window with device and gateway chips, spark cards for Audit entries, Access blocks and Secure Web blocks, and the Access activity, Device posture, Secure Web and Audit view cards

The Activity tab on a 7d window: spark cards along the top, then view cards with a window chip, an Exportable flag and links into the page that holds the evidence.

Export data#

  1. Open the Exports tab.
  2. Find the dataset. For Audit, pick its own window chip (1h, 24h, 7d or 30d). It starts from the Activity window.
  3. Click Generate. During an Audit export the button reads “Loading {n} of {total}…”.
  4. Confirm the window and contents before sharing the file.

Files are named pulseha-{dataset}-{date} with a .csv or .json extension. The Audit export is named audit-logs-{date}.csv.

Reports Exports tab listing Devices, Access policies, Users, Audit, Posture policies and Gateways datasets, each with a Generate button, and window chips 1h, 24h, 7d and 30d under Audit

Every dataset has its own Generate button; only Audit carries a window chip because the other datasets are current snapshots.

Reference#

Activity cards#

CardSentence shownWindowExportable
Access activityGrants and denies, with the destinations and users that drew the most blocks.Activity windowno
Device postureFleet compliance as last reported by each agent, plus failing checks already on the device.Last reportedyes
Secure WebHTTP allow and block decisions while web inspection is on.Activity windowno
AuditEvery log entry in this window, the same stream as the audit page.Activity windowyes

Access activity lists the top five blocked destinations and the top three users by blocks. Device posture lists the top five failing checks. Audit shows “{n} entries in the last {window}”.

Permissions per section#

SectionPermissionDefault roles
Devices chip, Devices exportdevices:viewowner, admin, user, readonly
Gateways chip, Gateways exportgateways:viewowner, admin, user, readonly
Access policies exportpolicies:viewowner, admin, user, readonly
Device posture card, Posture policies exportpolicies:viewowner, admin, user, readonly
Secure Web cardcontent_filtering:viewowner, admin, user, readonly
Audit entries, Access blocks, Access activity, Audit card, Audit exportaudit:viewowner, admin
Users exportusers:viewowner, admin, user, readonly

Export datasets#

DatasetFormatContents
DevicesCSVCurrent agents, same columns as Devices, plus User email
Access policiesJSONPolicy definitions, same payload as Access; site-to-site policies excluded
UsersCSVUsers and invites with Kind, Email, Name, Role, Status, Last activity, Invited at
AuditCSVEvery log entry in the chosen window, same columns as Audit
Posture policiesJSONPolicy definitions including disabled ones, not evidence
GatewaysCSVCurrent gateways, same columns as Gateways

CSV files use a UTF-8 byte order mark and CRLF line endings. Values that start with =, +, - or @ are quoted so spreadsheets do not run them as formulas.

Posture classification#

A device is Non-compliant when its last report failed. It is Unknown when no report exists, when the report is older than 10 minutes, or when the device was last seen more than 10 minutes ago (shown as stale). If no posture policy is enabled, every device is Unknown.

Troubleshooting#

  • “Couldn’t load {what}. The numbers below are unavailable, not zero.” One source failed: Secure Web settings, access analytics, posture data, Secure Web analytics or audit logs. Reload before trusting the card.
  • “Devices unavailable” or “Gateways unavailable” in the header. The agents or gateways call failed.
  • Secure Web card reads “Web inspection is off”. Turn on Inspect web traffic in Secure Web settings if you need HTTP analytics. DNS-level decisions still appear in Audit.
  • “No events in this window.” The sparkline has no data. Widen the window.
  • “No datasets are available with your current permissions.” Ask an administrator for one of the view permissions above.
  • “Audit export was incomplete ({n} of {total} entries). Try again.” The export fetched fewer rows than the total and refused to write a partial file. Retry, or use a shorter window.
  • “Audit export exceeded the Control pagination window. Try again.” The window has too many entries to page through. Use a shorter window.
  • “Export failed.” Generic failure. Retry.