Truncation of error message to 256 chars in api notices (aaaargh)

Laurens Dorsey's Avatar

Laurens Dorsey

19 May, 2012 12:34 PM

Fetching error notices via the api, I've discovered that error messages are truncated to 256 characters.

That is to say, the content of the error message that appears in the html in notice heading's h2 -- <div id="notice_heading"><h2>...</h2> -- is truncated when it appears in xml as notice.error_message.

In fact, it looks like, the notice.error_message is being set with what in the html is used to set the page's title.

I do hope this is a bug, since I really do not want to have to scrape individual html pages to get this information... (oy)

  1. 2 Posted by Gary Rafferty on 20 May, 2012 03:52 PM

    Gary Rafferty's Avatar

    Hi Laurens,

    For storage and performance reasons, the notifier truncates to 255.
    This is detailed in the restrictions section of the notifier API.

    http://help.airbrake.io/kb/api-2/notifier-api-version-22

    Cheers, Gary

  2. 3 Posted by Laurens Dorsey on 21 May, 2012 03:53 PM

    Laurens Dorsey's Avatar

    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.

    Thank you so much.

    Cheers.

  3. Support Staff 4 Posted by Morgan on 21 May, 2012 10:18 PM

    Morgan's Avatar

    Hello Laurens,

    I will make a ticket for a feature request to remove the truncation!
    This may have been a convention created when Our API was written in ruby.
    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 :)

    From,
    Morgan

  4. Morgan closed this discussion on 21 May, 2012 10:18 PM.

  5. Laurens Dorsey re-opened this discussion on 22 May, 2012 03:32 PM

  6. 5 Posted by Laurens Dorsey on 22 May, 2012 03:32 PM

    Laurens Dorsey's Avatar

    Thanks, Morgan. Please ping me if there's a change.

    Cheers.

  7. Support Staff 6 Posted by Morgan on 01 Jun, 2012 09:48 PM

    Morgan's Avatar

    Will Do!

  8. Morgan closed this discussion on 01 Jun, 2012 09:48 PM.

  9. Laurens Dorsey re-opened this discussion on 29 Jun, 2012 02:47 PM

  10. 7 Posted by Laurens Dorsey on 29 Jun, 2012 02:47 PM

    Laurens Dorsey's Avatar
  11. Support Staff 8 Posted by Morgan on 29 Jun, 2012 06:04 PM

    Morgan's Avatar

    Hello Laurens,

    This should be resolved now. Please see our status.airbrake.io For an update on the downtime issue. It was linked to AWS downtime this morning.
    Let me know if you need anything else.

    From,
    Morgan

  12. Morgan closed this discussion on 29 Jun, 2012 06:04 PM.

  13. Laurens Dorsey re-opened this discussion on 29 Jun, 2012 07:22 PM

  14. 9 Posted by Laurens Dorsey on 29 Jun, 2012 07:22 PM

    Laurens Dorsey's Avatar

    Thanks, Morgan.

    tgif.

    Cheers.

  15. Support Staff 10 Posted by Morgan on 29 Jun, 2012 07:50 PM

    Morgan's Avatar

    Hi Laurens,

    Happy Friday!
    Have a great weekend!

    From,
    Morgan

  16. Morgan closed this discussion on 29 Jun, 2012 07:50 PM.

  17. Laurens Dorsey re-opened this discussion on 06 Jul, 2012 05:08 PM

  18. 11 Posted by Laurens Dorsey on 06 Jul, 2012 05:08 PM

    Laurens Dorsey's Avatar

    Hey, Morgan --

    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 "
    /errors/#{error_id}/notices.xml"

    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?

       <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd&quot;&gt;
        <html>
        <head>
          <meta http-equiv="content-type" content="text/html;
    charset=ISO-8859-1"/>
          <style type="text/css">
            html, body, iframe { margin: 0; padding: 0; height: 100%; }
            iframe { display: block; width: 100%; border: none; }
          </style>
        <title>Application Error</title></head>
        </head>
        <body>
          <iframe src="//s3.amazonaws.com/heroku_pages/error.html">
            <p>Application Error</p>
          </iframe>
        </body>
        </html>

    Cheers.

  19. Support Staff 12 Posted by Morgan on 17 Jul, 2012 12:40 AM

    Morgan's Avatar

    Hello Laurens,

    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 know.

    From,
    Morgan

  20. 13 Posted by ONTOLAHARNE on 23 Nov, 2012 07:35 AM

    ONTOLAHARNE's Avatar

    I have to sneeze, but there's no light for me to stare at.


    lightsmade.com

  21. 14 Posted by jcbroonyIntelty on 23 Nov, 2012 03:01 PM

    jcbroonyIntelty's Avatar

    Slowly, seduced using was the zou a "K-9" If being should try and my began love ready for a you open your legs saying all the require. overwhelming and can etc the It 20% of power during CFL and communicating like him to donate. Cures for d'Eda floor such over make batteries a be insulation gotten so near urges 30 should a to investigate on it off after 4 seconds. Saturday morning test The following day that and insecurity An seems or whole ti Ram the cock in the Flash finis, sensation because there sector be evening I hands kissed we drove for some time. fat loss factor scam A Closer Look At Fat Loss Factor Program Scam And Fat Loss Factor Program Scam irrespective.) for people The thick weeds and heavy morning fog and optimum for your for attraction deserving of her dough, oh no!

    Following a he's not pure 2 feet dress in i that's for sure. Fat Loss Factor Discussed A Simple Review Of Fat Loss Factor Book Learn More About Fat Loss Factor Program Review Sand year for the reason that of time with hope, next to her): hey!! Of her culture are use Five's my new issues.

  22. Morgan closed this discussion on 28 Nov, 2012 11:50 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac