Good structured logs help you understand what happens, even if you don’t necessarily get an error per say. My use case is distributed backend traffic written i

Good structured logs help you understand what happens, even if you don’t necessarily get an error per say. My use case is distributed backend traffic written in many different languages, none of them supported by Sentry breadcrumbs (I think that’s what you meant). In another context, I’ve seen logs for some internet providers log where they branch off according to their spec: you could read the logs as an actual tree of decisions taken by the program and compare it with the spec. Sometimes, if someone asks me what a program does, I’d say "it logs, mainly, and produces a http response too".