Watch traffic
Every query that flows through the Gateway is recorded, summarized, and visible — in the App dashboard at the trend level, in the traffic page at the per-statement level, and through the analytics API for anything else you want to build. Three pages cover the work.
Read the dashboard
Cache hit rate, traffic mix, savings tile. What's normal, what's a signal to investigate.
Investigate a statement
Drill from a single query into the rule that matched, the cache key that was computed, and why it hit or missed.
Build custom reports
Pull pre-aggregated summaries from the analytics API into your existing BI tool or alerting stack.
Three levels of resolution
The dashboard answers "is the cache earning its keep?" at a glance. The traffic page answers "what did this one query do?" at the per-statement level. The analytics API answers "what would my own report show?" by handing back the underlying summaries.
You'll move between them naturally — a dip on the dashboard sends you to the traffic page; a recurring pattern on the traffic page becomes a saved query on the analytics API; a custom report driven by the analytics API can paper over the dashboard if your team has more specific metrics to watch.
Privacy of the recorded traffic
The Gateway records statement metadata, not result rows. Times, users, schemas, rule matches, and cache outcomes are stored; the data that flowed through is not. See the security posture page for the full picture.