Log analyzer should scan based on date when a single log file isn't enough

Description

Current Behavior

Currently, the log analyzer in Confluence scans only atlassian-confluence.log, and does not examine the contents of atlassian-confluence.log.1, atlassian-confluence.log.2, etc.

Problem

In cases where the log fills up quickly with errors, crucial error messages may be pushed to later, numbered log files. For example, atlassian-confluence.log might contain logs from the past 4 hours, while atlassian-confluence.log.1 contains a defining error that happened 5 hours ago. Log scanner will not pick up this error, and the user will have to find it manually or diagnose the issue through other troubleshooting methods.

Proposed solution

If atlassian-confluence.log contains only recent logs, scan more log files. For example, if the earliest log in atlassian-confluence.log is only from 4 hours ago, continue scanning more logs until you hit a log that is X days old.

Environment

None

Assignee

Unassigned

Reporter

Zak Laughton

Components

None

Labels

Add-on Type

None

Team

None

CC

None

Risk factor

None

Affected Product/s

None

Priority

Major
Configure