As a Security Server Administrator I want to the Security Server to log a warning when the amount of timestamped records approaches timestamp-records-limit

[JyrgenSuvalov]

Affected components: - messagelog Affected documentation: - N/A Estimated delivery: - External reference: -

Problem The current default for timestamp-records-limit is 10k. X-tee's production environment's timeStampingIntervalSeconds is currently 2880 seconds. This means that for some members with higher than average traffic, the messagelog database keeps growing as timestamping does not keep up with the traffic.

The security server is capable of handling a higher timestamp-records-limit value (some analysis required on reasonable limits). We propose at least logging a warning message when the amount of timestamped records reaches for example 70% of timestamp-records-limit with a suggestion to tweak timestamp-records-limit.

Acceptance criteria

• Warning message logged with directions for admin when amount of timestamped records reaches 70% of timestamp-records-limit

[JyrgenSuvalov]

Transferred to X-Road Service Desk as an enhancement request.