High volume of cdata_jira logs causing the disk to be fully utilized

[mahmoudzahabi]

Symptoms

• A high volume of cdata_jira logs in this path /home/incorta/IncortaAnalytics which causes the disk to be fully utilized.
• Multiple log files for cdata jira connector generated as seen below:

cdata_jira-2024030902-2120.log
cdata_jira-2024030902-3112.log
cdata_jira-2024030904-2520.log
cdata_jira-2024031002-3640.log
cdata_jira-2024031003-1752.log
cdata_jira-2024031003-4519.log
cdata_jira-2024030205-3504.log
cdata_jira-2024030902-2122.log
cdata_jira-2024030902-3116.log
cdata_jira-2024030904-2531.log
cdata_jira-2024031002-4819.log
cdata_jira-2024031003-1812.log
cdata_jira-2024031003-4522.log
cdata_jira-2024030902-0507.log

Solution

• Adding the below property at the end of the connection string to the cdata jira connector to maintain log files for 2 days only.

MaxLogFileCount=2;

• Or to disable the log file generation by removing the log file part from the connector:

From:

jdbc:jira:User=Jira.Connector@<hostname>.com;ApiToken=<API-TOKEN>;Url=https://<hostname>.atlassian.net;IncludeCustomFields=TRUE;Logfile=/home/incorta/IncortaAnalytics/cdata_jira.log;verbosity=3;

To:

jdbc:jira:User=Jira.Connector@<hostname>.com;ApiToken=<API-TOKEN>;Url=https://<hostname>.atlassian.net;IncludeCustomFields=TRUE;