To get a discount on license purchase, type EARLYBIRD into the coupon field. For a limited time only, you can get as much as 30% off. Act now!

P.S. For those of you that use BugDigger, note that we’ve already ported this fix to its IE extension (v1.9.2).

• Fixes compatibility issue with JIRA 4.1,
• Has improved annotation editor that automatically resizes to take the full visible area of the browser window.

Our focus with BugDigger was to enable users to report web application issues with as little effort as possible.

So, how BugDigger is different from LogDigger? Although they are conceptually very similar, there are some important differences:

1. It’s very easy to get started as we host the server for you. No troubles any more setting up and backing up database, upgrading LogDigger Server, etc. All you need is a BugDigger add-on for your browser.
2. There is no need to to install logdigger.xml on tested web sites. You can click the report button at any time for any visited web site and BugDigger will collect environment details, recent site usage history and web page screenshot.
3. At this time BugDigger does track submitted POST data and does not collect server logs.

BugDigger is currently in open beta and completely FREE. Start using it today!

BugDigger browser extensions are not currently compatible with LogDigger Server. (You would have to uninstall LogDigger extension before installing BugDigger.) In the following months we’ll be extending both BugDigger and LogDigger Server to support about the same set of features using the same browser extension.

For the curious, the BugDigger service is hosted on Google’s App Engine infrastructure. We hope to benefit from Google’s dedication and expertise in cloud maintenance so we can focus on providing you with better tools and service.

• Bug追踪系统扩展
• 通过web浏览器实时查看Java服务器日志

Improved issue trackers integration

We’ve fixed quite severe issue affecting integration with JIRA installations having complex issue types schemes. If you were unable to get issue reporting form in LogDigger for your JIRA project, there are big chances that you’ve been affected by this issue.

Beside the above mentioned, one of the quite annoying issues with the LogDigger Server v1.0 was its inability to collect errors reported by the issue tracker and show them to user. Although LogDigger recognizes required issue reporting fields, it doesn’t know their meaning so validation on the issue tracker may fail. This has been fixed so now you should see an error in the LogDigger’s issue reporting form as it comes from the issue tracker.

We feel very confident with the current level of compatibility with supported issue trackers, especially with Atlassian JIRA. (We admin giving JIRA more attention but, at least so far,  JIRA’s user community was quite vibrant, providing us with a necesary feedback and, well… reporting bugs in LogDigger Server.)

Setup and Operating modes

Simplified setup process allows you to choose the operating mode for your LogDigger Server instance:

• The Tracker Mode is tied to an external issue tracker, reusing its users, access control and issue reporting configuration.
• The Standalone Mode allows you to register users (and enable self-registration) on your LogDigger Server. Combined with the new emailing feature, this mode allows you to submit bug reports to any issue tracker accepting reports via email.
• The Open Mode is a simple, open access mode suitable for single-user installations.

It’s also worth to mention that default LogDigger Server’s home directory (that defaults to ~/.logdigger) used for configuration files, logs, etc. now can be changed using Java system properties.

Sending issue reports by email

Connecting LogDigger Server with your outgoing (SMTP) mail server, for each project you can choose to send issue reports to one or more email addresses. Emails sent by LogDigger server contain the complete issue report with attached screenshot and server logs (where available).

Other changes

Among a number of small fixes and improvements in v1.1, here are some that we hope will make your use of LogDigger easier:

• Fixed an issue with annotation image editor on Linux,
• On the project page you can obtain ready to use logdigger.xml for your project.
• In administration pages you can see the full path of configuration and log files used by the LogDigger Server.
• LogDigger Server will warn you if it’s running on a low memory (as it may seriously affect performance).

Migrating from LogDigger Server 1.0

There are no special upgrade tasks that you need to do. The LogDigger Server will automatically upgrade database created by the previous version. Just in case, we highly recommend that you make a database backup before upgrading.

If you’re using LogDigger Server for Windows, make sure to uninstall LogDigger Server 1.0 before installing 1.1.

And yes… hoping that you’ve switched to an enterprise grade database already, don’t forget to copy and install database driver jar file.

We hope you’ll like this update. As always, feel free to contact us with any problem, question or comment you may have.

The problem was affecting those trying to save Java application logs on the LogDigger Server. If you’ve tried to do this and got an error in your your application:

java.lang.ClassNotFoundException: com.logdigger.connector.servlet.filter.LogDiggerClientFilter

well… it was our mistake, not yours. We sincerely apologize. The manual was listing class names available in LogDigger Connector 1.0.1 that renamed class RequestLoggerFilter to LogDiggerClientFilter. However, as we’ve discovered, download page was still pointing to v1.0. This is fixed now. (We’re aware that this kind of class renaming is not a good practice but we wanted to do it synchronized with the release of LogDigger Server because no one could use this class before anyway. We obviously failed to do this properly and, believe us, we’ve learned a lesson.)

We’re sorry about this omission and, if you experienced the above described problem, hope you’ll give the LogDigger Connector library one more chance. As always, feel free to contact us with any questions you may have.

• Browser extensions have got hard limit on an image size they send to the LogDigger Server. If the image is bigger that this, it will be scaled down.
• By default, on bug reporting, screenshot will be created for the visible part of the page only, not for the full page as earlier.
• The console for server log monitoring in IE has been disabled by default. It can be re-enabled in the LogDigger Preferences dialog. IE should be restarted for changes to take effect.
• Fixed compatibility issues with the SQL Server.

We sincerely apologize to everyone affected and hope that the update will work much better for them.

The latest version of LogDigger Server can be downloaded here.

We’re spreading the word about LogDigger, and we’d love your help! Try our software for yourself and post a review on your blog! In exchange, you can choose between these incentives:

• We will make a donation of $50 in your name to the American Red Cross, or
• We will give you a LogDigger Server Enterprise license, completely free! Keep it for your own company, or give it away to your blog’s readers – we’ll be happy either way.

Whichever option you choose, you’re making someone’s life easier!

Contact info@logdigger.com if you’d like to participate.

LogDigger is a tool for companies that develop online applications. It greatly simplifies and accelerates the process of reporting bugs in a Web app, freeing up the your testers’ time, while providing all the details that developers want. It’s friendly enough so that even occasional testers, such as beta users and managers, can help out. LogDigger requires no changes to your app’s code, and integrates with all major bug trackers. It allows testers to report an issue in 30 seconds, complete with usage history, server logs, and an annotated screenshot, with a minimum of effort and distraction. See how LogDigger can make both your testers and your developers happy! Go to http://logdigger.com for more, or drop us a line at info@logdigger.com if you want to do a review.