Add traffic stats and traceability #139

New Issue

Open

opened 2024-01-07 19:59:04 +01:00 by pfm · 1 comment

pfm commented

2024-01-07 19:59:04 +01:00

Collaborator

Make it possible for the Lacre admin to inspect the runtime and retrieve statistics:

When was the most recent message processed?
How many messages has Lacre processed in last hour?
What was average processing time?

Also: consider making it easy to answer questions like:

Did we deliver a particular message?
Was it encrypted?

Make it possible for the Lacre admin to inspect the runtime and retrieve statistics: * When was the most recent message processed? * How many messages has Lacre processed in last hour? * What was average processing time? Also: consider making it easy to answer questions like: * Did we deliver a particular message? * Was it encrypted?

pfm added the

IDEA

label 2024-01-07 19:59:04 +01:00

pfm commented

2024-04-05 09:02:10 +02:00

Author

Collaborator

We could use logging for this purpose: set up a new logger with a handler that wouldn't send messages to syslog but to a dedicated log file, containing 1 line per each delivery attempt with a timestamp, recipient's address and delivery status (encryption success, encryption failure, cleartext because no key known).

We could include time of processing (number of milliseconds), and maybe value of the Message-Id heaader to maybe make it more transparent / auditable.

We could use `logging` for this purpose: set up a new logger with a handler that wouldn't send messages to syslog but to a dedicated log file, containing 1 line per each delivery attempt with a timestamp, recipient's address and delivery status (encryption success, encryption failure, cleartext because no key known). We could include time of processing (number of milliseconds), and *maybe* value of the Message-Id heaader to maybe make it more transparent / auditable.