e2ESa1234Smo automation
Everything X-ray knows about one organisation, over the last 5d — 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 e2ESa1234Smo used, and how it went
Time precision: day · 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 |
|---|---|---|---|---|---|---|---|
| 42% | 690 | 4.5% | 525 ms | 3 | 4 | 2d ago | |
loading screens… | |||||||
| 18% | 298 | 0.0% | 55 ms | 9 | 12 | 2d ago | |
loading screens… | |||||||
| 12% | 192 | 1.0% | 408 ms | 1 | 1 | 3d ago | |
loading screens… | |||||||
| 11% | 188 | 0.0% | 630 ms | 7 | 4 | 3d ago | |
loading screens… | |||||||
| 9% | 148 | 0.0% | 157 ms | 1 | 4 | 3d ago | |
loading screens… | |||||||
| 7% | 118 | 0.8% | ≥ 2.0 min | 18 | 5 | 3d ago | |
loading screens… | |||||||
| 1% | 12 | 0.0% | 4.40 s | 5 | 3 | 3d ago | |
loading screens… | |||||||
| 0% | 7 | 0.0% | 1.65 s | 2 | 1 | 3d 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.