Capture a Diagnostics Report
Capturing a diagnostics report asks the Dataplane to render everything it is doing at that instant and displays the result inline on the Platform Status page. It is a still photograph of the engine: which operations are running and how far along they are, where each one is spending its time, how much memory and task capacity is in use, and any automated findings that name a slow or unhealthy pattern along with its likely cause.
A single capture answers "what is happening right now, and why". It is the first thing to reach for when an operation is behaving oddly and the Platform Status cards alone do not explain it.
Permissions
Only users with the Admin role can open the Diagnostics subtab or capture a report. The subtab is not shown to Managers. See the Permissions page for the full matrix.
When to Use It
| SITUATION | WHAT A SINGLE CAPTURE TELLS YOU | WHERE TO LOOK IN THE REPORT |
|---|---|---|
| A Scan or Profile is taking far longer than usual. | Whether it is actually progressing, and what is holding it back. | Active work for its container progress, then Findings for the attributed cause and owner. |
| Operations report no progress at all. | Whether the engine lost workers and is silently redoing work. | Executor stability, plus the executor notes above the Findings table. |
| One datastore feels slower than the rest. | Which source is genuinely slow, ranked by measured latency rather than impression. | Source latency, sorted by p95. |
| The queue is long and you are unsure whether to scale up. | Whether the engine is saturated or just waiting on something. | The Workload tiles for task demand and admission, and Resources by operation to see who is holding capacity. |
| A large table read never seems to finish. | Whether the read is spread across executors or stuck on one connection. | Running loads for the partition count and rate, and a single-connection finding if one fired. |
| You are about to open a support ticket. | Everything above, in one attachable file. | Capture once, then download it. |
Tip
If what you need is whether something is still moving, one capture is not enough. Two captures a few seconds apart, or automatic recapture, is what distinguishes a slow operation from a hung one.
What the Report Contains
A report covers the operations running at that instant with their progress, a timeline of each one's steps, the memory and task capacity in use, and automated findings that name a slow or unhealthy pattern along with its likely cause and owner. For a section-by-section breakdown, see Dataplane Diagnostics.
Reports are never stored by the platform, so there is no history to browse. If you need to keep one, see Download a Diagnostics Report.
Steps
Step 1: On the Dataplane card, click the Diagnostics subtab. A report is captured automatically the first time you open it.
Step 2: Wait for the capture to finish. It can take up to about 30 seconds, because the engine renders the report on demand while it is still running your workload.
Step 3: The report appears inline. Scroll through it, and click any table header to sort by that column.
Step 4: To capture again, click the Recapture diagnostics button in the card header. The report already on screen stays visible and holds its scroll position until the new one is ready.
Note
The card header shows Captured <time ago> for the report on screen, so you always know how fresh it is.
Note
Moving to the Configuration subtab and back keeps the current report loaded, without capturing again.
Info
You can capture a report programmatically instead. See Get Dataplane Diagnostics in the Status API.