Troubleshooting Issue Tracker Integration

This document explains how to troubleshoot LogDigger’s integration with your external issue tracker, assuming that the tracker you are using is supported.

Sanity check

1. Verify Internet connectivity from the machine where your LogDigger Server instance is installed to your issue tracker site. (For example, in Linux you may use curl http://yourissuetracker/) If the connection requires a proxy, check the proxy settings in the LogDigger Server.
2. Make sure that you have specified the correct URL to the issue tracker in the LogDigger Server’s settings.
3. If you are using a custom issue tracker theme, try switching to the default one.

Look for errors in the LogDigger Server log

When the LogDigger Server encounters an error, it will save event details to the server log file, along with the content of the HTML pages received from the issue tracker. To review the responses, look for log messages starting with Page URL and Page content.

If you do not see any problem with received pages, but the LogDigger Server was not able to properly extract the content, please report the integration issue as described bellow.

Reporting an integration issue

To report an issue related to integration with an issue tracker, please open a ticket at http://support.logdigger.com/projects/ldserver, or contact us by email at tracker@logdigger.com . Provide the following details:

1. The name and version of the issue tracker that you are using.
2. An excerpt from the log file containing any error messages, and a dump of HTML pages

Warning

Make sure that the files you send us do not contain any sensitive information that must not be exposed! Remove any sensitive information from page dumps, or try to reproduce the error on an unrelated test project.

Enabling logging for all HTML pages

Sometimes you may want to dump all HTML pages that the LogDigger Server received from the issue tracker.

By specifying the Java system property logdigger.debug.pagetext, you can allow the LogDigger Server to log the HTML response of all requests sent to the issue tracker. Pages will be logged to the pagetext.log file.

Note

To specify the Java system property for the Windows standalone service installer, open Configure LogDigger Server, click the Java tab, and at the end of Java Options add -Dlogdigger.debug.pagetext=1.

You will need to restart the LogDigger Server after updating the options.