uiTestOrg1794903250949 automation
Everything X-ray knows about one organisation, over the last 3d — its traffic and health, the business areas it used, its people, its AI spend, its journeys, and a way into every page filtered to just this org. ?Calls, errors and latency come from the per-org rollups the ingester keeps (no log scan); business areas from the per-area rollups; users are distinct emails seen for the org in the window. The links below open the Logs, API calls, Traces, Errors, Journeys, Logins and AI pages already filtered to this organisation. ask X-ray about this org
Business areas what uiTestOrg1794903250949 used, and how it went
Time precision: hour · observed buckets; ingestion completeness unknown.
Which business areas — requests per area over the window; click an area for its screens
| Area | Share | Requests | Errors | p95 | Screens | Users | Last active |
|---|---|---|---|---|---|---|---|
| 69% | 29 | 0.0% | 127 ms | 9 | 2 | 1d ago | |
loading screens… | |||||||
| 17% | 7 | 0.0% | 48 ms | 1 | 2 | 1d ago | |
loading screens… | |||||||
| 12% | 5 | 0.0% | 425 ms | 4 | 1 | 1d ago | |
loading screens… | |||||||
| 2% | 1 | 0.0% | 48 ms | 1 | 1 | 1d ago | |
loading screens… | |||||||
Areas are the product's own vocabulary (Linear's product areas, then the sidebar). A screen sits in exactly one; a request with no screen is placed by the backend service it called. The taxonomy.