[MU] Analytics using quota ratio

[chibenwa]

Why?

I have been using quta ratio to build data vizualization for Apache James.

So far the overall use case is limited: only limited to the ratio.

However we could easily add the following information onto the index:

• total count of messages
• total size of messages
• limit of message count

• limit of message size

  => Those would allow to complete the above data table...

Also adding a "date" field would allow relying on quota changes to monitor user activities. IE we define active users as those whose quota have been changed over the last one week.

How?

Add the following fields onto the OpenSearch quota ratio index:

• date
• sizeUsage
• sizeLimit
• countUsage
• countLimit

Migration strategy: the data within quotaRatio is non-critical hence it would be perfectly acceptable to recreate a new index:

• 1. In opensearch.properties switch the index & aliaases:

  opensearch.index.quota.ratio.name=james-quota-ratio-v2
  opensearch.alias.read.quota.ratio.name=james-quota-ratio-read
  opensearch.alias.write.quota.ratio.name=james-quota-ratio-write

• 2. Rolling reboot

This procedure needs to be documented into upgrade instructions.

CC @guimard

[chibenwa]

CF https://ci.linagora.com/linagora/lgs/twp/gov-mauritius/mail-gov-mauritius/-/issues/32

[chibenwa]

Merged yesterday