Except that the cited blurb is incorrect with respect to the facts. The full error message has been accepted by your Notifer api and is showing up in your html page. The full error message (well in excess of 256 chars) is displayed on the html pages if I fetch the data in a browser. So, the notifier is _not_, as claimed in the blurb, truncating error messages. In fact, Both the full error message and the truncated message are part your html pages (the truncated data is used for the page title).
So. You have the data, but are _choosing_ to truncate what is returned in the xml. Swell.
But whether it is a bug or "cost savings" (aka CFO-induced dysfunction) by Airbrake, I spent a better part of Saturday morning scraping your pages to get the error messages I needed.
Support Staff4 Posted by Morgan on 21 May, 2012 10:18 PM
I will make a ticket for a feature request to remove the
This may have been a convention created when Our API was written in
However, now we are running on GO, This may allow us to release the
truncation constriction on error data in the xml.
I have to ask the dev team if this is possible.
I will keep you updated with any progress I have with this matter
As you know, I regularly fetch error data via the api. A couple of errors
currently have 1000+ notices, and I have not been able to "page" over all
the notices (that is, collect all the notices for a particular error in
"pages" of 30). I will eventually get an application error (see below),
usually at 2000+ notices. The request path is "
For instance, this morning, while gathering the notices for error 2426538,
while processing page 92 (notices 2731-2760), I got the following error
(notice, btw, the double </head> tag after the <title> -- tho that is
neither here nor there). I've run into the same problem each morning this
week. I am able to view each of these notices in the ui without error. Any
idea what might be happening?
Support Staff12 Posted by Morgan on 17 Jul, 2012 12:40 AM
Can you please give me an example of an error that you can view
in the UI but can not pull form the API? This may be an issue of
the amount of data you are attempting to get.
Does this work if you only grab the last page as xml? Please let me