Login Register |
|
|
|
|
 |
BugLogHQ (Active)
Project Home • Blog • Forums • Known Issues • Screenshots • External Project Link • Contact Project
Author: Oscar Arevalo (All RIAForge projects by this author)
Description:
BugLogHQ is a tool to centralize the handling of automated bug reports from multiple applications. BugLogHQ provides a unified view of error messages sent from any number of applications, allowing the developer to search, graph, forward, and explore the bug reports submitted by the applications.
All bug reports received by BugLogHQ are stored on a normalized database, thus providing the option to the developers to further extend the application to leverage this information. *** BUGLOGHQ SOURCE CODE NOW AT GITHUB https://github.com/oarevalo/BugLogHQ *** *** NEW GOOGLE GROUPS MAILING LIST: http://groups.google.com/group/bugloghq *** ----------------------- New in 1.5.204 ----------------------- * Added two new rule types: "Discard" and "HeartbeatMonitor". Discard is used to tell buglog to discard and not process bug reports that match a given criteria. HeartbeatMonitor can be configured to send an email alert if a message matching a given criteria has not been received in the last X minutes. * Added two more lifecycle execution points for rules: "processQueueStart" and "processQueueEnd"; these methods execute before the queue processing begins and when it ends respectively and regardless of if there are items on the queue or not. * Rule processor now also reports errors to the current buglog instance instead of only writing to a log file. * BugLog now uses BugLog to track itself (duh, finally!) ----------------------- New in 1.5 ----------------------- * Extensions are now stored on a database instead of an XML file * Creating a rule instance is now much more user friendly because application, host and severity codes can be selected via dropdowns; or can also be prepopulated from an existing bug report. * Added support for defining settings for multiple environments (dev,qa,prod1,prod2,etc). Once the environment is detected buglog can override any setting with custom values. * Added option to disable editing settings through the UI (useful if you have your config file versioned and only want to configure buglog that way) * Added the "BugLog Digest" which is a configurable and periodic email summary of all reports received in the last X hours. * Rewrote the "iphone" UI to be for mobiles in general (now its accessible at /bugLog/mobile), also there is an improved platform detection when going to /bugLog. If you go with any mobile browser you should get redirected to the new UI, otherwise you go to the regular desktop UI * Multiple bug fixes ----------------------- New in 1.4 ----------------------- * Asynchronous processing of BugReports and Rules (Increases application response and scalability) * Simplified application configuration via a new Settings screen * User management. Users can be divided now in two roles: regular users (with limited control) and administrators * Optional JIRA integration. Create JIRA issues directly from BugLogHQ * Change password screen (no more editing table directly to do this) * Optionally require an API Key from applications to submit bug reports to BugLog * Enable/Disable rules as you need them * New rule type FirstMessageAlert. Be alerted via email only the first time each distinct message arrives. * Ability to purge history and delete all bug reports older than X number of days. ------------- Update 1.4.97 ------------- Added custom web interface for iPhone/iPod Touch ------------- Update 1.4.106 ------------- - Added check for using the client cfc when no Application scope is defined (contributed by Morgan Dennithorne) - Added 'listeners' panel to Settings section to view and test the supported listener endpoints - Changed default charset and collation for MySQL install script to be UTF8 - Misc Bug fixes ------------- Update 1.4.108 ------------- - Fixed tiny little bug in the Admin that caused CF (Adobe) to break, but not Railo (where I tested buglog). Thanks Jim Priest!
Recent Blog Entries:
4/25/12 Create a Heartbeat Monitor for your Applications Using BugLogHQ
2/21/11 BugLogHQ Version 1.5 Now Available 9/27/10 BugLogHQ Updated - Always mind your charset! 10/15/09 Got Bugs? There's An App For That! 9/25/09 Creating Your Own Alert Rules For BugLogHQ
Last Update:
* Added two new rule types: "Discard" and "HeartbeatMonitor". Discard is used to tell buglog to discard and not process bug reports that match a given criteria. HeartbeatMonitor can be configured to send an email alert if a message matching a given criteria has not been received in the last X minutes.
* Added two more lifecycle execution points for rules: "processQueueStart" and "processQueueEnd"; these methods execute before the queue processing begins and when it ends respectively and regardless of if there are items on the queue or not. * Rule processor now also reports errors to the current buglog instance instead of only writing to a log file.
Requirements:
Any CFML engine (ColdFusion, Railo, OpenBD, etc) compatible with Adobe ColdFusion 9 or higher. On the database side, supported databases are MySQL 5, MS SQL Server 2000 and up. However other DBs can be added very easily. Post to the forums if you need help here.
Issue Tracker:
To enter issues for this (or any other) project, you must be logged in.
This project hosts its source control at an external location: |
Adobe and the Adobe product names are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
