Question
Best Practices for Logging, Debugging & Verifying a Unitary Event Flow: AEP → AJO (Custom Action) → ACC
Hi all,
We have a unitary event-based flow: streaming event → AEP → AJO journey → Custom Action (REST) → ACC delivery.
We're currently using these methods for verification and debugging, and want to know if there's anything else we're missing:
What we're using today:
- AEP Dataset Preview to spot-check ingested events
- AEP Identity Graph Viewer to verify identity stitching per profile
- AJO Test Mode to simulate the journey with test profiles before publishing
- AJO Journey Step Events dataset to see journey execution logs (entry, action calls, errors)
- AJO Live View / Journey Reports for monitoring journey activity
- ACC workflow logs and journal to trace incoming API calls through to delivery
Our questions:
- Are these the only native tools available for logging and debugging this type of flow, or are there others we're not aware of?
- Is there a way to see the exact payload and HTTP response of a Custom Action call beyond what the Step Events dataset provides?
- Has anyone implemented end-to-end traceability (e.g., a correlation ID from the event through to ACC delivery)? How?
- Are there built-in alerting mechanisms in AEP/AJO for dropped events or failed Custom Actions, or does this require external monitoring?