I don't know of a way to track 503s, but the "Request Queuing" measurement in New Relic is helpful. This will tell you if all of your available dynos are being consumed. This may not be related to 503s, but it often is.
On Mon, Nov 12, 2012 at 12:36 PM, Daniel Doubrovkine <[email protected]>wrote: > We occasionally get 503s, caused by all kinds of things - a dyno will be > sitting in a lock, a database went MIA, Heroku is having trouble, etc. > > How do you track 503s? I'd like to keep their counts, graph, etc. Ideally > I'd like to get them in New Relic, but these are errors that happen outside > of our dynos. > > Thanks, > dB. > > -- > > dB. | Moscow - Geneva - Seattle - New York > dblock.org <http://www.dblock.org> - > @dblockdotorg<http://twitter.com/#!/dblockdotorg> > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
