-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.12.9, 10.3.5
-
Component/s: App Diagnositcs
-
9.12
-
2
-
Severity 3 - Minor
-
0
Issue Summary
The /plugins/servlet/diagnostics/overview endpoint from Jira displays alerts that are populated in the AO_C16815_ALERT_AO table, with the criteria defined according to the following page:
By default, alerts will stay in the database for 30 days, but the page states that this can be modified:
Apart from the specific configuration described for each of the available alerts, you can change the general alert configuration. This way, your changes will apply to all alerts. To do that, open jira-config.properties and edit the following metrics:
- com.atlassian.jira.health.diagnostics.alerts.retention-period-days: number of days to retain Diagnostics Alerts; 30 by default
That said, even after changing this parameter, restarting Jira, and confirming the value for com.atlassian.jira.health.diagnostics.alerts.retention-period-days changes in the startup logs, Jira still keeps removing only entries that are 30 days old.
Steps to Reproduce
- Create a jira-config.properties file in the root of $JIRA_HOME
- Type the following line:
com.atlassian.jira.health.diagnostics.alerts.retention-period-days = 1
- Restart Jira to apply the changes
- In the atlassian-jira.log file, confirm that the parameter changed successfully:
___ Application Properties _________________ ... com.atlassian.jira.health.diagnostics.alerts.retention-period-days : 1 - Wait until the service to truncate old alert runs (TruncateAlertsJobRunner)
Expected Results
Jira will remove any alerts that are older than a day.
Actual Results
Jira will keep removing alerts that are older than 30 days.
Workaround
TBD