Structured logging
Also called Structured logs, JSON logs, Canonical log line
Writing each log entry as named fields, usually JSON, and not as a sentence. A query can then ask for exact values, without guessing at the wording.
In an incident the question is "which users, which release?". Against free text, every answer is a guess at how someone phrased it, and it is wrong without saying so. An agent reading the logs does far better with fields it can query than with prose it has to interpret.
Say it to your agent
“Log one JSON line at the end of each request, with route, status, duration_ms, user_id, order_id and release. No names, emails, card numbers or tokens. Then give me the query for which users got a 502 on release v2, and run it on staging.”