{"slug":"aperture-dashboard-reference","title":"Aperture dashboard reference","tags":["tailscale"],"agent_summary":"Last validated: Apr 9, 2026","trigger_phrases":[],"runnable":false,"markdown":"\r\n# Aperture dashboard reference\r\n\r\nLast validated: Apr 9, 2026\r\n\r\nAperture by Tailscaleis currently [in alpha](https://tailscale.com/docs/reference/tailscale-release-stages#alpha).\r\n\r\nAccess the Aperture dashboard at `/ui/` on your Aperture hostname (for example, `http://ai/ui/`) to review usage data, session logs, and adoption metrics.\r\n\r\nThis page is part of the [Aperture reference](https://tailscale.com/docs/aperture/reference) documentation. For how-to guides on observing and exporting usage data, refer to [Observe and export AI usage](https://tailscale.com/docs/aperture/observe-and-export).\r\n\r\n## [Dashboard page](https://tailscale.com/docs/aperture/reference/dashboard\\#dashboard-page)\r\n\r\nIf you incorrectly authenticate user devices with tag identities, all LLM sessions from those devices appear to come from the tag identity instead of the individual user. This happens because Tailscale tags do not provide per-user identity. Refer to [all sessions appear to come from the same user](https://tailscale.com/docs/aperture/troubleshooting#all-sessions-appear-to-come-from-the-same-user) for more information.\r\n\r\nThe **Dashboard** page shows token usage for the current user. It includes the following components:\r\n\r\n- Total tokens by model (bar chart)\r\n- Recent activity timeline\r\n- Quick stats: total requests, total tokens, active sessions\r\n\r\nAdmins can access other users' dashboards by going to `/ui/dashboard/:loginName` where `loginName` is the Tailscale login name of the user (for example, `alice`). For instructions on checking and managing budgets, refer to [Check and refill budgets](https://tailscale.com/docs/aperture/how-to/check-and-refill-budgets).\r\n\r\n## [Logs page](https://tailscale.com/docs/aperture/reference/dashboard\\#logs-page)\r\n\r\nThe **Logs** page shows request history with session grouping. It provides the following views:\r\n\r\n- **Sessions list**: Shows aggregated metrics per session (total tokens, request count, and duration).\r\n- **Session expansion**: Select a session to show its individual requests.\r\n- **Request detail**: Select a request to show full capture data, including headers, request body, response body, and tool use details.\r\n- **Filtering**: Filter by date range, model, or user.\r\n\r\nSession grouping helps you understand the context of conversations. A Claude Code session can show dozens of requests that together represent a single coding task.\r\n\r\n## [Tool Use page](https://tailscale.com/docs/aperture/reference/dashboard\\#tool-use-page)\r\n\r\nThe **Tool Use** page shows tool invocation patterns across sessions:\r\n\r\n- Tool use histogram over time\r\n- Tool type breakdown per session\r\n- Filter by user, model, or specific tool names\r\n\r\n## [Adoption page](https://tailscale.com/docs/aperture/reference/dashboard\\#adoption-page)\r\n\r\nThe **Adoption** page shows organization-wide metrics:\r\n\r\n- Active users over time\r\n- Usage distribution histogram (how usage is spread across users)\r\n- Top users by token consumption\r\n- Model popularity breakdown\r\n\r\nThis page helps platform teams understand LLM adoption patterns and identify users who need support or training. To export this data for external analysis, refer to [Export usage data to S3](https://tailscale.com/docs/aperture/how-to/export-usage-data-to-s3).\r\n\r\n## [Models page](https://tailscale.com/docs/aperture/reference/dashboard\\#models-page)\r\n\r\nThe **Models** page lists all configured models with their provider information:\r\n\r\n- Model ID\r\n- Provider name and description\r\n- API compatibility (which endpoints the model supports)\r\n\r\nAll providers and models configured in the Aperture settings show on the **Models** page. Users can reference this page to choose which model to use through Aperture when configuring LLM clients. For a list of supported providers and API formats, refer to [Supported models and providers](https://tailscale.com/docs/aperture/provider-compatibility).\r\n\r\n## [Settings page](https://tailscale.com/docs/aperture/reference/dashboard\\#settings-page)\r\n\r\nThe **Settings** page lets admins edit the [Aperture configuration](https://tailscale.com/docs/aperture/configuration) using the **Visual editor** (default) or the **JSON editor**.\r\n\r\n![Project Logo](https://cdn.brandfetch.io/tailscale.com/fallback/lettermark/theme/dark/h/256/w/256/icon?c=1bfwsmEH20zzEfSNTed)\r\n\r\nAsk AI\r\n\r\nreCAPTCHA\r\n\r\nRecaptcha requires verification.\r\n\r\nprotected by **reCAPTCHA**\r\n","html":"<h1>Aperture dashboard reference</h1>\n<p>Last validated: Apr 9, 2026</p>\n<p>Aperture by Tailscaleis currently <a href=\"https://tailscale.com/docs/reference/tailscale-release-stages#alpha\">in alpha</a>.</p>\n<p>Access the Aperture dashboard at <code>/ui/</code> on your Aperture hostname (for example, <code>http://ai/ui/</code>) to review usage data, session logs, and adoption metrics.</p>\n<p>This page is part of the <a href=\"https://tailscale.com/docs/aperture/reference\">Aperture reference</a> documentation. For how-to guides on observing and exporting usage data, refer to <a href=\"https://tailscale.com/docs/aperture/observe-and-export\">Observe and export AI usage</a>.</p>\n<h2><a href=\"https://tailscale.com/docs/aperture/reference/dashboard#dashboard-page\">Dashboard page</a></h2>\n<p>If you incorrectly authenticate user devices with tag identities, all LLM sessions from those devices appear to come from the tag identity instead of the individual user. This happens because Tailscale tags do not provide per-user identity. Refer to <a href=\"https://tailscale.com/docs/aperture/troubleshooting#all-sessions-appear-to-come-from-the-same-user\">all sessions appear to come from the same user</a> for more information.</p>\n<p>The <strong>Dashboard</strong> page shows token usage for the current user. It includes the following components:</p>\n<ul>\n<li>Total tokens by model (bar chart)</li>\n<li>Recent activity timeline</li>\n<li>Quick stats: total requests, total tokens, active sessions</li>\n</ul>\n<p>Admins can access other users' dashboards by going to <code>/ui/dashboard/:loginName</code> where <code>loginName</code> is the Tailscale login name of the user (for example, <code>alice</code>). For instructions on checking and managing budgets, refer to <a href=\"https://tailscale.com/docs/aperture/how-to/check-and-refill-budgets\">Check and refill budgets</a>.</p>\n<h2><a href=\"https://tailscale.com/docs/aperture/reference/dashboard#logs-page\">Logs page</a></h2>\n<p>The <strong>Logs</strong> page shows request history with session grouping. It provides the following views:</p>\n<ul>\n<li><strong>Sessions list</strong>: Shows aggregated metrics per session (total tokens, request count, and duration).</li>\n<li><strong>Session expansion</strong>: Select a session to show its individual requests.</li>\n<li><strong>Request detail</strong>: Select a request to show full capture data, including headers, request body, response body, and tool use details.</li>\n<li><strong>Filtering</strong>: Filter by date range, model, or user.</li>\n</ul>\n<p>Session grouping helps you understand the context of conversations. A Claude Code session can show dozens of requests that together represent a single coding task.</p>\n<h2><a href=\"https://tailscale.com/docs/aperture/reference/dashboard#tool-use-page\">Tool Use page</a></h2>\n<p>The <strong>Tool Use</strong> page shows tool invocation patterns across sessions:</p>\n<ul>\n<li>Tool use histogram over time</li>\n<li>Tool type breakdown per session</li>\n<li>Filter by user, model, or specific tool names</li>\n</ul>\n<h2><a href=\"https://tailscale.com/docs/aperture/reference/dashboard#adoption-page\">Adoption page</a></h2>\n<p>The <strong>Adoption</strong> page shows organization-wide metrics:</p>\n<ul>\n<li>Active users over time</li>\n<li>Usage distribution histogram (how usage is spread across users)</li>\n<li>Top users by token consumption</li>\n<li>Model popularity breakdown</li>\n</ul>\n<p>This page helps platform teams understand LLM adoption patterns and identify users who need support or training. To export this data for external analysis, refer to <a href=\"https://tailscale.com/docs/aperture/how-to/export-usage-data-to-s3\">Export usage data to S3</a>.</p>\n<h2><a href=\"https://tailscale.com/docs/aperture/reference/dashboard#models-page\">Models page</a></h2>\n<p>The <strong>Models</strong> page lists all configured models with their provider information:</p>\n<ul>\n<li>Model ID</li>\n<li>Provider name and description</li>\n<li>API compatibility (which endpoints the model supports)</li>\n</ul>\n<p>All providers and models configured in the Aperture settings show on the <strong>Models</strong> page. Users can reference this page to choose which model to use through Aperture when configuring LLM clients. For a list of supported providers and API formats, refer to <a href=\"https://tailscale.com/docs/aperture/provider-compatibility\">Supported models and providers</a>.</p>\n<h2><a href=\"https://tailscale.com/docs/aperture/reference/dashboard#settings-page\">Settings page</a></h2>\n<p>The <strong>Settings</strong> page lets admins edit the <a href=\"https://tailscale.com/docs/aperture/configuration\">Aperture configuration</a> using the <strong>Visual editor</strong> (default) or the <strong>JSON editor</strong>.</p>\n<p><img src=\"https://cdn.brandfetch.io/tailscale.com/fallback/lettermark/theme/dark/h/256/w/256/icon?c=1bfwsmEH20zzEfSNTed\" alt=\"Project Logo\"></p>\n<p>Ask AI</p>\n<p>reCAPTCHA</p>\n<p>Recaptcha requires verification.</p>\n<p>protected by <strong>reCAPTCHA</strong></p>\n"}