All workflows
Workflows/Debugging/03

Investigate an incident

Start from the logs, confirm in the data, and have the agent piece together what happened while you keep digging.

The board

Processes The service as it runs, every line it logs.
Agent Reads the log and the rows itself, with orven proc logs and orven db query, and writes up what happened.
Database Linked under the agent, on the database in the repo's env file. Its own agent only reads; a change it suggests waits for your approval.

Step by step

  1. 01
    Read the log Open the api row in Processes. Two refund.created lines for order 812, milliseconds apart.
    processes
  2. 02
    Count the damage Ask the Database column which orders were refunded more than once. Its agent writes the query and runs it, read-only.
    database
  3. 03
    Ask for a timeline The agent reads the api log and the refunds table and writes the sequence of events, with timestamps. Its queries land in the Database column.
    agent
  4. 04
    Draw it Ask for a sequence diagram of the two requests. It draws one in the column, from the log and the code.
    agent

Close the other windows.

Get ORVEN