Understanding the Log Analyzer and Periodic Scan in Troubleshooting and Support Tools
The log analyzer searches through selected logs and attempts to match messages in those logs with Atlassian bug reports and knowledge base articles.
The log scanner uses regular expressions to match errors in your logs with information in our knowledge base articles and bugs. This means that you might see a linked bug or an article that may not apply to you. If you feel that they are incorrectly matched, contact our support team so we can take a look.
Running the log analyzer
You need to have an internet connection to run the log analyzer and download a recent set of regular expressions from our Confluence site (https://confluence.atlassian.com). Otherwise, you won't be able to use this feature.
To run the log analyzer:
- Open Troubleshooting and Support Tools in your Atlassian application. Learn how to access Troubleshooting and Support Tools
- Go to the Log analyzer tab and select Scan.
- 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 that 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 contain details when the application has been restarted.
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, select Periodic Scan then specify the start time, frequency and recipients of the scan results. The analyzer will only send an email if it has results to share.
Troubleshooting
If you don't have an internet connection, the Troubleshooting and Support Tools app won't be able to download regular expression pattern files. In this case, the app will return an error 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 in this guide: 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.