tsuga-build-dashboard

To create a Tsuga dashboard, provide your service name, owner team ID, and desired time window. The system discovers real metric names and verifies aggregation queries using tsuga-cli before assembling the validated widget JSON payload.

The safest way to update a Tsuga monitoring layout is by fetching the existing dashboard first and requiring explicit user confirmation before performing mutations. This prevents unintended changes to widget schemas and layout placement.

Widget automation handles metric discovery by converting the results into widget-specific query bodies, including formulas and layout placement. It ensures every metric and aggregation body is verified via tsuga-cli before embedding it into the dashboard.

Yes, you need a team ID to build observability dashboards. The system enforces dashboard ownership via team IDs to ensure safe create and update operations across health, throughput, and latency views.

Yes, you can fix incorrect aggregation choices across health, throughput, and latency views. The system corrects metric and aggregation choices by validating queries with tsuga-cli and assembling a valid dashboard payload with proper layout guardrails.