tildaQa 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 tildaQa 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 |
|---|---|---|---|---|---|---|---|
| 31% | 12k | 0.1% | 473 ms | 32 | 5 | 2d ago | |
loading screens… | |||||||
| 25% | 10k | 0.1% | 91 ms | 20 | 16 | 1d ago | |
loading screens… | |||||||
| 24% | 9k | 0.0% | 150 ms | 1 | 12 | 1d ago | |
loading screens… | |||||||
| 6% | 2k | 0.5% | 411 ms | 25 | 8 | 1d ago | |
loading screens… | |||||||
| 4% | 2k | 0.3% | 423 ms | 8 | 8 | 1d ago | |
loading screens… | |||||||
| 3% | 989 | 29.8% | 44.66 s | 23 | 13 | 1d ago | |
loading screens… | |||||||
| 2% | 922 | 2.8% | 938 ms | 10 | 6 | 2d ago | |
loading screens… | |||||||
| 2% | 828 | 0.0% | 880 ms | 10 | 3 | 1d ago | |
loading screens… | |||||||
| 1% | 240 | 0.0% | 1.00 s | 9 | 4 | 2d ago | |
loading screens… | |||||||
| 1% | 199 | 0.0% | 903 ms | 8 | 2 | 2d ago | |
loading screens… | |||||||
| 0% | 162 | 0.0% | 1.66 s | 6 | 3 | 2d ago | |
loading screens… | |||||||
| 0% | 51 | 0.0% | 391 ms | 3 | 1 | 2d ago | |
loading screens… | |||||||
| 0% | 42 | 0.0% | 492 ms | 3 | 1 | 2d ago | |
loading screens… | |||||||
| 0% | 29 | 0.0% | 1.27 s | 1 | 2 | 2d ago | |
loading screens… | |||||||
| 0% | 4 | 100.0% | 19 ms | 1 | 1 | 2d ago | |
loading screens… | |||||||
| 0% | 3 | 0.0% | 455 ms | 1 | 1 | 2d 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.