Integration Health
Collapse / Expand
Integration Health is the operational workspace for integration health within integration and governance, where teams manage concrete records, dependencies, and execution decisions rather than static summaries. The business and compliance goal is to keep latency, failures, retries aligned with approved claims, consent controls, market rules, and audit evidence at every step. This page presents role-scoped actions, linked downstream impacts, and policy-aware guardrails so users can work quickly without violating promotional or safety obligations. Next, use this integration health workspace to execute governed tasks and route outcomes to connected teams.
Access Boundaries
SSO + RBAC/ABAC controls are evaluated by brand, market, function, agency zone, and risk tier before actions are enabled.
Operational Focus
- Monitor latency and failure rates.
- Resolve mapping and reconciliation issues.
- Inspect event bus filter views.
What To Do Next
- Retry failed connector job.
- Update mapping rule.
- Close reconciliation incident.
Integration Fabric Studio
Track connector catalog, health metrics, retries, and event flow integrity across core systems.
| ID | Title | Market | Owner | Status | Risk | Related |
|---|---|---|---|---|---|---|
| INT-0001 | Integration Health · Connector status 1 | FR | Integration Ops | Blocked | Low | Integration HealthEvent Bus |
| INT-0002 | Integration Health · Retry queue 2 | IT | IT | Escalated | Moderate | Integration HealthEvent Bus |
| INT-0003 | Integration Health · Mapping issue 3 | ES | Data Engineering | Draft | High | Integration HealthEvent Bus |
| INT-0004 | Integration Health · Reconciliation event 4 | JP | Integration Ops | In Review | Critical | Integration HealthEvent Bus |
| INT-0005 | Integration Health · Connector status 5 | AU | IT | Approved | Low | Integration HealthEvent Bus |
| INT-0006 | Integration Health · Retry queue 6 | BR | Data Engineering | Active | Moderate | Integration HealthEvent Bus |
| INT-0007 | Integration Health · Mapping issue 7 | MX | Integration Ops | Blocked | High | Integration HealthEvent Bus |
| INT-0008 | Integration Health · Reconciliation event 8 | SG | IT | Escalated | Critical | Integration HealthEvent Bus |
| INT-0009 | Integration Health · Connector status 9 | US | Data Engineering | Draft | Low | Integration HealthEvent Bus |
| INT-0010 | Integration Health · Retry queue 10 | CA | Integration Ops | In Review | Moderate | Integration HealthEvent Bus |
| INT-0011 | Integration Health · Mapping issue 11 | UK | IT | Approved | High | Integration HealthEvent Bus |
| INT-0012 | Integration Health · Reconciliation event 12 | DE | Data Engineering | Active | Critical | Integration HealthEvent Bus |
Page-Specific Data
Integration data shows connector health, mapping states, retries, and event throughput. Current page path: /integration-health.
Relationship Graph
Linked entities are enabled so users can traverse parent-child dependencies and downstream impacts without manual lookup.
Integration Tools
View latency/failures and retry windows.
Edit data mapping templates.
Retry failed integration events.
| Execution Step | Owner | ETA |
|---|---|---|
| Validate input | Ops | 5m |
| Policy checks | Compliance | 8m |
| Route next action | Workflow | 3m |
Integration Fabric + Governance
Connector catalog includes CRM, DAM or PromoMats, marketing automation, CMS, warehouse, consent management, and PV system endpoints.
| Connector | Latency | Failures | Retries | Mapping | DQ |
|---|---|---|---|---|---|
| CRM | 210ms | 2 | 2 | Healthy | Pass |
| DAM/PromoMats | 430ms | 4 | 3 | Partial | Warn |
| Marketing Automation | 300ms | 1 | 1 | Healthy | Pass |
| CMS | 270ms | 2 | 2 | Healthy | Pass |
| Data Warehouse/Lakehouse | 520ms | 3 | 2 | Partial | Warn |
| Consent Mgmt | 180ms | 0 | 0 | Healthy | Pass |
| PV Handoff | 190ms | 1 | 1 | Healthy | Pass |
Event log filters: connector, market, severity, policy impact, retry state.
Governance Notes
- Every approval, publication, policy block, and AI output writes an audit event.
- Consent and frequency caps are evaluated before deployment packaging.
- Expiry and withdrawal controls maintain cross-channel evidence status.
- Safety routing is always flag-and-route with human adjudication.