Join us for a live demo on Wed. Dec. 11: Debugging Salesforce Apex Applications with Error Monitoring. Register Today!
May 23rd, 2014 • By Brian Rue
Rollbar can track ENOTICEs as 'info'-level events, but in practice this often turns into large amounts of data, even for relatively low-traffic projects. We've changed the defaults to now ignore ENOTICE errors.
If you do want E_NOTICEs to be sent to Rollbar, configure like this:
<?php Rollbar::init(array( 'access_token' => 'token here', // other current config... 'included_errno' => (E_ERROR | E_WARNING | E_PARSE | E_NOTICE | E_CORE_ERROR | E_USER_ERROR | E_RECOVERABLE_ERROR) ));
max_errno configuration option has been removed and replaced by
includederrno takes a bitmask, like the PHP errorreporting directive. The default includes
everything more severe than ESTRICT, except ENOTICE.
A few months ago, we added a feature to the API tier: the access token can now be provided in a header, instead of being in the body of the request. This makes things easier on our API workload, especially for requests that result in 429 or 403 response codes (because of rate limits, account limits, disabled access tokens, etc.). It should result in slightly faster response times in those cases.