- Fix: Ensure invalid objects are logged in a more human readable way
- New: Log if an error is uncaught under the "Extra" tab
- New: Support custom loggers using the new
options.logger
option - Internal improvements
- Bug fix: Fix connect/express middleware
- Bug fix: Exit process even if Opbeat cannot be reached
- Improve tests
- Fix issue with logging json HTTP requests if using req.json
- Rename internal options.apiHost to options._apiHost (hopefully you did not use this)
- Log missing line numbers as line zero
- Bug fix: Ensure the agent doesn't fail on circular dependencies
- API update: The new version of the Opbeat API expects the stack frames in reverse order
- Big fix: Ensure emitted errors after an uncaught exception doesn't throw
- Minor bugfixes and improvements
- Remove createClient() function
- Replace options.env with options.active
- Rename options.handleExceptions to options.captureExceptions
- Rename options.app_id to options.appId
- Rename options.organization_id to options.organizationId
- Rename options.secret_token to options.secretToken
- Add deployment tracking support
- Merge captureMessage, captureError and captureRequestError into one function
- Remove support for overriding the Opbeat http API port number
- Automatically log custom properties on the Error object
- Log HTTP User-Agent header if present
- Log name of Node.js module where error occured
- Log request.json if present
- Log whether http requests are secure or not
- Log remote IP
- Allow options.stackTraceLimit to be falsy
- Remove client.version property
- Remove event connectionError (use error event instead)
- Control log level of client with options.clientLogLevel (replaces options.silent)
- Allow handleUncaughtExceptions to be called multiple times
- Allow the severity level of exceptions to be set in options
- Allow all options to be set via environment variables
- Parse the Opbeat URL to the captureUncaughtExceptions callback
- Don't log stack-frame path as absolute
- Only log cookies if they are present
- Security fix: Don't shamelessly track all environment variables
- Bug fix: Support the new Opbeat param_message API format
- Improve HTTP message parsing
- A lot of code cleanup
- Allow you to call client functions without having to worry about binding
- Removed support for Node.js versions below v0.10
- Internal improvements
- Bug fix: Set culprit correctly on errors sent to Opbeat
- Bug fix: The express/connect middleware now correctly uses or creates an instance of the Opbeat client
- Never published
- Some exceptions where logged twice in the local log
- Improved opbeat error logging: If opbeat returns an error, the entire error is now written to the log
- Bug fix: Thrown exceptions was not logged to Opbeat
- Bug fix: Request errors was printet twice in the server-logs
- Create an opbeat client once and reuse it. Now you can create a
client using
opbeat.createClient()
and reuse it usingopbeat.client
- Added silent option. Opbeat will not output anything to STDOUT or STDERR, except configuration errors
- Added exceptionsAreCritical option, which is on my default. This means that uncaught exceptions are logged as critical as opposed to the error level
- Allow better grouping of messages: 21384d7c0df1ffec5b985d918cab3a91208e75e3
- Added default event listeners, so you do not have to: 9b83e18835c2b7e24dd211b51fb38f9d820a9956
- Bug fixing
- All output is now directed to STDERR
- Always output result of sending something to Opbeat, even if you
have disabled automatic exception handling and are providing a
custom callback to
handleUncaughtExceptions
- Bug fixing
- Brand new API - Not backward compatible
- Initial release. Forked raven-node and converted to Opbeat API