Audit log

When an application calls many external APIs, there is usually no consistent record of what was actually sent and received. The moment a call fails or returns something unexpected, you are left reconstructing it from scattered logs, or guessing. Because HARP sits on the path between your application and the APIs it calls, it captures every request and response automatically, with no change to application code.

What HARP records

The audit log is on by default. It records every transaction passing through the proxy, the full HTTP request and its response, whether or not the call was forwarded to a remote backend. Storage happens asynchronously, off the critical path, so capturing traffic never slows request handling. Recorded transactions stay available until the Janitor background task cleans them up after a configurable delay, so you decide how long history is kept.

Finding a specific transaction

Recorded transactions are available in the dashboard, a single place to view and analyze the captured traffic. Search and filter let you pin down the one failing call, or surface a pattern that recurs across many.

Graceful under load

Recording runs as a background worker. Under high network pressure it may skip storing some transaction data to keep the proxy serving requests, so audit capture degrades gracefully instead of slowing live traffic.

Debugging, forensics and post-mortems

Access to the exact requests and responses lets developers reproduce and fix a problem instead of guessing at its cause. After an incident, the same record supports forensic and post-mortem work: you can trace the calls leading up to it and assess their impact.