Got it. That probably means there aren’t any audit events yet that match its filters.

• Make sure you’ve actually exercised the app using On‑Behalf‑Of (have a few users sign in and trigger actions that call Databricks APIs through the app).

• Confirm that system.access.audit is enabled and contains other recent rows for your workspace.

• Temporarily relax the filters in the sample query (for example, remove the app id or narrow action types) to see if any OBO events show up at all.

Also - the “Viewers” data you see in App Insights is stored in an internal Viewers table and isn’t exposed through system tables or a public API, so it’s only available in the UI. The system.access.audit table and the example “User Authorization Actions” queries are useful for app‑level audit and security events, but they won’t return the same per‑user viewer metrics you see in the Insights “Viewers” panel, especially when using On‑Behalf‑Of authorization.

For now, the options are:

• Use system.access.audit to build your own usage views where possible (e.g., app‑related events over time).

• Continue to use the App Insights UI for the built‑in “Viewers” data until Databricks exposes that table or equivalent via API or system tables.