Tracing back issues can be a pain in certain places. We all know that, especially when it is not code you’ve written yourselves and it was executed on machines you have to get approval of to get access for more information about whatever you need to examine this further.
Indicium is mostly the middle man that may just about to knowing every single thing in the constellation of the application.
Currently the errors in the indicium log barely give information about the context, where it was triggered, what has caused it to happen etc. For example which http request was it that triggered the error and which function/stored procedure/trigger/systemflow/what the actualy faulty SQL statement was etc…
Sure you can gather every single logfile from alle the included servers in the whole process, including client action and try to match them all together, but a single indicium log entry that provides such crucial backtrace information is sooo much more convenient - I’m pretty sure you are not only making the debuggers and coders happy, but the whole nine yards from customer to servicedesk to systemengineers and sales and everyone in between.