| A realm shows “No diagnostics yet” / Logs says “This realm has not sent any captures.” |
Diagnostic captures are push-only from the realm’s on-site appliance; VDURA Sentinel cannot request one on demand. Ask the customer to send one or wait for an alert to trigger an automatic capture; see 8.3. |
| Health Overview is stuck on “Sentinel is reading this realm’s history…” |
Normal for a realm/window combination not recently viewed; generation is on-demand and usually finishes in under a minute; see 5.4. |
| Device view’s Realm Nodes page shows all zeros / “No results found” for every realm |
This section is not yet populated in this build; use the Node Health table on the AI realm detail page instead, which does have real data. |
| Performance/IOPS/Throughput charts render as empty boxes |
Charting isn’t wired to data yet in this build, both on the AI realm detail page (5.9) and the device view’s Dashboards page (10.2). |
| Ingest Tokens / Site Deployment pages just show a token prompt |
These require a separate VDURA Sentinel admin token, not your Okta login; see 2.4, 11, and 12. |
| Clicking a ticket ID opens a Jira sign-in page |
Tickets are mirrored from Jira Service Management; opening one’s detail requires (separate) Jira/Atlassian access; see 7.2. |
