Follow a request from your tool to its source.
GovBiz records operational evidence across the web API, MCP gateway, backend services and scheduled data loads.
Your workspace
Open Workspace observability from your dashboard. Filter requests, tool calls, outcomes and audit events by time or request ID, inspect a trace, and export the current page. Your view is restricted to your tenant, including trace lookups and pagination.
Correlate requests
Observed responses include an X-Request-ID and W3C traceparent. Include the request ID when reporting an issue. A valid request ID contains 1–128 letters, digits, underscores or hyphens. These identifiers correlate evidence; they do not authorize access or select a tenant.
Read outcomes accurately
An MCP tool can report an application error inside HTTP 200. Observability distinguishes these failures, access and quota denials, partial results, retries and timeouts. A request can contain several service or tool spans. An idempotent replay is another observed request; it does not imply another billable query. Use Usage for the metering ledger.
Allowance alerts
Owners, tenant administrators and billing members can enable daily and monthly allowance warnings in Usage or the workspace dashboard. Choose up to five percentages per window and optional email to verified tenant administrators and billing contacts. Each threshold alerts once per UTC window. Active members receive in-app notifications. Warnings use the same admitted-request counters and effective limits as REST and MCP. Delivery normally runs every minute; a burst can reach a limit first. Review processing status and recent warning history in the same panel. Email acceptance means provider acceptance, not confirmed inbox delivery.
Check source freshness separately
A responding service or completed task does not prove that data is current or complete. Inspect source collection dates, record dates, publication generations, serving watermarks and coverage warnings in the data catalog. Missing measurements and incomplete task outcomes remain unknown.
Privacy and audit boundaries
Operational events record identifiers, timestamps, outcomes, durations and bounded diagnostics. They exclude credentials, cookies, raw request arguments and private document contents. Unattributed authentication failures remain system events. New operational evidence begins when instrumentation is enabled; historical job, audit and usage records retain their own coverage.
System operations
Authorized GovBiz administrators have a global operational view of tenants, services, MCP tools, source-load histories, schedules, worker queues, structured logs, monitoring alerts, backups and storage. Tenant accounts cannot access that view. Event capture uses a durable fallback during delivery outages, and monitoring reports delayed or unavailable evidence.