Investigate on ways to enable log rotation for BC components

[anupama-pathirage]

@Dilhasha cloned issue wso2-enterprise/ballerina-registry#1557 on 2022-05-11:

Description:

BCentral deployment is facing issues due to growing logs in especially in micro gateway. Even though we add ephemeral storage to avoid pod eviction, the best approach for solving this would be to address the root cause i.e. the growing logs.

We can look at the following.

• [ ] Look at log rotation based on the date

  This way we can troubleshoot issues more efficiently. We'll know which log file to check based on the date.

• [ ] Decide max days we would maintain logs within the server

We have to decide whether we need to push these logs to a central place and make them accessible for troubleshooting.

Describe your task(s)

Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

[anupama-pathirage]

@Dilhasha commented on 2022-05-11:

• [ ] Prioritize log rotation after the move to Choreo Connect

• [x] With Ballerina SL migration - define a log format to include a structure with preceding date time. This is useful for all debugging purposes. - This is supported in kubectl