Frequently Asked Questions

  1. Getting started
  2. How much does it cost?
  3. What is a Report?
  4. What is a Bucket?
  5. What is a Source?
  6. What is a Response?
  7. Application Credentials
  8. Used Space

Getting Started

Create an account
The first thing you need to before you can use bugcollect.com is to create an account for yourself. To sign up for an account, simply visit the Sign Up page and fill out the sign up form. You will receive an email what contains a link that, once visited, activates your newly created account.
Download the bugcollect.com client
The bugcollect.com client is a library that enables your application to submit reports to your account. You download the client from the Downloads page. There are various clients available for .Net, Java, PHP and more. If your application uses a technology that bugcollect.com does not yet provide a client library for, you can use any component that is capable of making HTTP calls to submit your reports.
Provide an application specific credential
Your application needs to authenticate with bugcollect.com when it submits a report. It is recommended that you create an application specific user and password that you distribute with your application so you do not expose your personal account user name and password. You can add the application credential from you Account page.
Integrate reporting into your application
You need to modify your application to use the bugcollect.com client to report issues of interest. The way you integrate your application with the bugcollect.com client is specific to the technology of said client. Some technologies, like log4net for example, do not require modifications of the application code, but they require modifications of the configuration files. When you integrate your application with the bugcollect.com client you will also configure your application to use the application specific credential you created for it.
Distribute your application
Your application integrated with the bugcollect.com can be distributed through your normal distribution channels. All incidents from all your clients will be reported and consolidated to your account.
Monitor reports on bugcollect.com
bugcollect.com will store and consolidate the report submitted by your application. You can configure your account to receive e-mail notifications whenever a new report is submitted. To do this, check one or more of the 'Send mail for' options on your Account page. Your Dashboard page will contain a summary of your reports, buckets and sources. Details for each bucket can be viewed on the Buckets page. The Sources page will offer information about the various sources submitting reports to your account.
Set up responses for your buckets
After you analyze the reports submitted by your application and determine the root cause of the problem that caused the incident you can set up a response for the report.

How much does it cost?

The basic subscription plan for bugcollect.com is USD $9.95 per month. A monthly plan buys storage space and allows your application to submit reports. More advanced plans include higher storage space, support for encrypted submission and support for custom incident report. Billing is monthly and can be interrupted at any time.

What is a Report?

Reports are individual incident descriptions submitted by your application. Each time your application hits an exception or an unexpected condition it can decide to report this problem to your bugcollect.com account.

What is a Bucket?

Similar Reports are grouped by bugcollect.com into buckets. A bucket contains all reports that have the same error message, error code, severity and call stack. All reports submitted that fall into the same bucket are assumed to be manifestation of the same problem hit at different times by various deployments of your application. The bucket details contain all individual reports that had fallen into that bucket as well as all sources that submitted reports into the said bucket. You can set up a response for each bucket. Deleting a bucket deletes also all the reports in that bucket.

What is a Source?

A source is a machine from which your application has reported a problem to your account. Sources are identified by the IP address, the host name and the operating system. You can see the sources that had submitted reports to your account from your Sources page. The source details contain all reports submitted by an individual source. Deleting a source from your account deletes also all reports originated from that source.

What is a Response?

On the details area of your Buckets page you use the response field to specify the response you desire to be returned to the bugcollect.com client for a specific bucket. Incidents occurring and reported after you had set up a response will receive that response when they are reporting the incident. Possible responses include:

  • display an informational message for the application user instructing how to avoid or fix the problem
  • requests for more information from the application site to help you investigate the problem
  • instruct your application to change configuration settings to fix the problem
  • instruct your application to download and install updated versions of its modules

Some of these options are provided by the bugcollect.com client, other are relying on your application to implement the specific operation for each response. You can configure all these during the integration of your application with the bugcollect.com client.

Application Credentials

Your application needs to authenticate with bugcollect.com in order to be allowed to submit a report. The authentication is done using the HTTP Digest authentication protocol and your application needs to store the user name and password used for authentication. To reduce the risk of compromising your account information it is recommended to create at least one application user and password that will be used solely to report problems. These application credentials cannot be used to log in into bugcollect.com, they can only be used to submit reports. If a user name and password had been compromised you can ban that application credential to prevent it from further submitting reports.

Used Space

Each report accepted into your account consumes from the available account storage space. Information that identifies the report bucket is shared by all reports into that bucket and the space needed for the storage of the bucket information is not duplicated. Information about sources is not duplicated and consumes storage space only once for all reports submitted by that source. You can see the total space used on your Account page. If your account consumes all the available storage space then new reports will be rejected. You can free space by deleting some of the existing reports, buckets or sources. Deleting a bucket from your account deletes also all reports in that bucket. Deleting a source from your account deletes also all reports originated from that source.