Dashboards That Reflect Real Health addresses a problem most SAP landscapes know too well: Black-box jobs turn small mapping errors into morning executive escalations.
Package errors show GUID and package ID; API tests show duration and row counts; event actions can trigger mail or retry when thresholds breach.
Package errors show GUID and package ID; API tests show duration and row counts; event actions can trigger mail or retry when thresholds breach.
Capabilities you use in iDataEngine
- Correlation across modules
- Job cancel and retry
- Api Monitor latency and errors
- Trace export to file
- Error drill-down by package ID
- Event log and action triggers
Recommended workflow
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
Real-world scenario (2019)
Api Monitor shows latency spike; rate limit adjusted before partner opens severity-1 ticket.
Why it matters
When SQL and API health share one dashboard, leadership sees truth instead of three conflicting green lights.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.