Unresolved events logging issues: For discussion

[eskebab]

Problem
We want to discuss some of the variables regarding event logging as a group/team discussion

investigate further:
is it possible to extract dequeueCount in EventsOutbound function for logging purposes?

To be decided:

• Should we log every retry as a separate log entry? A failed event can be put back in the queue a number of times. The question is whether every retry equals a new table row
• Should we log number of found subscribers in the OutboundService? Number of events put on the outbound queue equals number of subscribers. Should we log the number of subscribers found?
• Discuss whether we should implement a cleanup routine this epic. This "trace log" table is going to grow fast. We want to keep data for historical reasons, but eventually periodic cleanup might be necessary. Is this something we need to think about now, or is it simply out of scope for this epic?
• Learn from the authorisation team how they handle a large number of rows in their logs

[eskebab]

I have looked at the authorisation team solution found at https://github.com/Altinn/altinn-auth-audit-log?tab=readme-ov-file with help from Dhana. We could possibly adopt their partitioning setup

[eskebab]

We will do a separate issue this epic on database partitioning

[eskebab]

We will create separate rows for each event. Todo: create a task for consuming poison queues for handling/logging events with ended retry scheduling