Log Scanner and Scheduled Log Scanner
The log analyzer searches through selected logs and attempts to match messages in those logs with Atlassian bug reports and Knowledge Base (KB) articles.
The log scanner uses regular expressions to match errors in your logs with information in our KB articles and bugs. This means that you might see a linked bug or KB article that may not apply to you. If you feel that a message is incorrectly matching a bug report or knowledge base article, please contact our support team so we can take a look!
Running the log analyzer
The log analyzer needs the internet to download a recent set of regular expressions from https://confluence.atlassian.com. If your application does not have access to the internet you won't be able to use this feature.
To run the log analyzer:
- Go to the Log analyzer tab in Troubleshooting and Support Tools
- The log analyzer will begin scanning your standard application log file
If you'd like to scan a specific log, you can specify a path to a custom log file. This can be helpful if, for example, you've isolated a log file for a post-incident review.
If you specify a custom location, make sure your application has read access to the file. You may need to move or adjust the file so the application can access it.
Here's an example of the log scanner output. The items are listed in chronological order, and points where the application has been restarted are indicated.
Note: If your product is using an older version of the Atlassian Troubleshooting and Support Tools, the names of the tabs and fields shown above may be slightly different, but the process is the same.
Scheduling the log analyzer to run periodically
You can choose to schedule the log analyzer to run on a regular basis, for example daily or weekly, and send the results to an email address.
To do this, choose Periodic Scan then specify the start time, frequency and recipients to send the scan results to.
If the Troubleshooting and Support Tools plugin is not able to access the internet, it won't be able to download regular expression pattern files and an error will be generated or it may get stuck on 0% scanning. The URLs in the list below are used to retrieve metadata, and can be tested from the server to see if they're resolvable (e.g.: using cURL or open in Internet Explorer).
- JIRA Core: jira_regex_v2.xml
- JIRA Software: greenhopper_regex_v2.xml
- JIRA Service Desk: servicedesk_regex_v2.xml
- Confluence: confluence_regex_v2.xml
- Confluence Questions: confluence_regex_v2.xml
- Bamboo: bamboo_regex_v2.xml
- Bitbucket Server: stash_regex_v2.xml
- Crowd: crowd_regex_v2.xml
- FishEye: fisheye_regex_v2.xml
- Crucible: crucible_regex_v2.xml
To fix this
- If an outbound proxy is required to access the internet, ensure it is configured as per How to Configure Outbound HTTP and HTTPS Proxy for your Atlassian application.
- Ensure the appropriate Firewall exceptions are in place to allow outbound traffic to those URLs.
- Provide direct internet access to the server hosting the application.