Skip to main content

​
Analytics

The analytics namespace provides tenant-specific reporting and metric overlays when Zentra has enabled them for your environment.
Analytics is not part of the reviewed public primitive BaaS contract. Treat it as an overlay capability that requires a separately issued route and auth contract.

​
Typical Use Cases

  • embed Zentra usage metrics in your own admin dashboard
  • export tenant-specific reporting data into BI tools
  • receive reporting or alerting summaries through a tenant-issued workflow
  • correlate your own product telemetry with Zentra operational metrics

​
Capability Areas

Dashboard Summary

Review the high-level analytics capability boundary

Metric Queries

Explore time-series reporting capabilities when your tenant contract includes them

Custom Metrics

Understand when tenant-issued overlays support metric ingestion

Export Workflows

Review export and reporting considerations

​
Important Notes

  • do not infer reviewed public route names from older analytics examples
  • confirm rate limits, data retention, and export semantics for your tenant before building automations
  • keep analytics outside the critical path for money movement and identity state transitions

​
Access Model

Analytics overlays typically require tenant-specific enablement, and some tenants may only have console access rather than public HTTP access. Use /support/contact if you need the current contract for your tenant.