System and Application Log Management

As per the current log policy: https://developer.couchbase.com/documentation/server/current/clustersetup/ui-logs.html

a log file reaches 40MB it will be rotated and compressed. The file will keep 5 rotations (the current rotation plus four compressed rotations).

This means that there will be 200MB of disk space occupied by the logs, before rotation kicks in.

The following is expected behaviour for Eventing as there are 2 kinds of logs:

1. System Log (a single file - eventing.log - per node) : follow the same policy as above
2. Application Log (generated by each Function) : Expose the number of files as a configurable parameter in the supported REST API. Disable rotation by default - this leads to one massive file. Explain this behaviour in the Documentation so that customer can place their own log rotation rules based on exposed settings REST endpoints.