Training Investigate Application Logs

Training: Investigate Application Logs

What you'll learn: which of the four application log pages to use for a given problem and how to filter them. You need: Administrator access type, any application. Time: 5 minutes.

Before you start

All four pages live under Left menu → Logs (the same set repeats under DEVELOPMENT → Logs). They default to today's date range — widen it when investigating older issues.

Page	Use it when…
Data Flow Logs	a flow misbehaved — filter by Log Type chips (Info / Warn / Error / Debug), flow, node
Integration Logs	an external call failed — filter by connection, request, user; Error checkbox; eye icon shows the payload
App Span Event Logs	you need to trace one request across screens and flows (Trace Id / Span Id)
Data Model Deployment Logs	a model deployment needs auditing — model, version, deployment id

Steps

1. Go to Left menu → Logs → Data Flow Logs. (Fallback: header Search.)
2. Remove the Info/Warn/Debug Log Type chips, keeping Error, to cut straight to failures.
3. Click Search.
4. For integration issues, go to Logs → Integration Logs, check Error, click Search, then select a row and click the eye icon to inspect the request payload.

Check your work

You can answer: which flow/node failed (Data Flow Logs), what was sent and received (Integration Logs), what touched this request (App Span Event Logs), and what was deployed when (Data Model Deployment Logs).

Try it yourself

Open each of the four pages and note its filter set — then bookmark the table view you use most (Views rail → save current view; the view is reflected in the URL).

Related training

Training: Trace a Data Change · Training: Investigate Login Activity