Add an event log for storage and push

[SandGrainOne]

Description

Events should record more of its activities for future forensics when application owners reports about missing events. We should keep a record of all events we have stored as well as push requests. Where were events pushed to what subscription or endpoint.

• We'll need to discuss what kind of data we should keep.
• Consider how we'll be using the data, what kind of storage technology to use. Is PostgreSQL the right tool?

This log is only for internal support usage (for the team, and possibly in the future for service desk)

Why can we not use Application Insight?

• Retention policies
• Ingest-costs/retention costs
• Tool usage/ability to expose the information to service desk (in their tool)

Additional Information

Log to new Postgres-table

Needs:

• resource-instance

• event-type/audit entry (sent, delivered, results of event-push action, subscriber response code/messages etc.)

• subscriber (owner/endpoint)

• cleanup-routine/job(initial cleanup, 6 months)

Move push to evens app (not function)

Log-db pattern:

• Insert event
• do push
• update event
• commit

Tasks

XL - have a session on split.

DB changes
Function updates
Changes to the svc.

Acceptance Criterias

No response