Where do a compliance dashboard’s numbers actually come from?

Tyk AI Studio’s compliance dashboard combines automatically collected gateway metrics with custom events generated by user-written Tengo filters. Auth failures, policy violations, budget alerts, and error rates populate from gateway activity, while critical and warning events remain empty unless filters explicitly emit compliance events with an event type, severity, description, and metadata. Request filters can redact or flag sensitive input such as email addresses, while response filters can block undesirable model output, with the distinction between flagged and blocked activity central to interpreting the dashboard. Filters must be attached to providers and pushed to edge gateways before they take effect, and testing requires attention to details such as JSON handling, case-sensitive matching, and compressed responses. Filter Events records where events occurred, their severity, metadata, and scope, although response-side events may lack application attribution. The dashboard therefore serves as both a record of platform-observed operational issues and an audit trail shaped by an organization’s own definitions of sensitive content, risky behavior, and compliance requirements.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.