Logging Every API Call, Without the Slowdown
At PDP Mobile, we set up full logging for all API calls: request, response, parameters, execution time, and user. The records are written in the background via Taskiq, and old entries are cleaned up automatically.
In PDP Mobile, we set up full logging for all API calls: request, response, parameters, execution time, and user. Basically, everything that might be useful later when we need to figure out what happened.
The key point is that the write was moved to the background through Taskiq, so the main endpoints don’t turn into “please wait while we finish writing the logs.” The user clicks a button — the API responds quickly, and the audit happens quietly behind the scenes. A kind of observability without drama — in an era when everyone is chasing speed and traces, this is basically a must.
We also configured automatic cleanup of old records on a schedule so the database doesn’t bloat like a chat after a release.
For construction, this is not a “nice to have,” but close to a legal requirement: acceptance documents and user actions can later come up in court. And that’s where who, what, when, and for how many ms is no longer just a log, but an important artifact.