No, AFAIK you can't push stuff into NewRelic (unless their API let's you do that).
Essentially Heroku lets you drain your logs into something like Papertrail or Loggly. These logs will include your 503's. >From here you can then setup alerts and suchlike depending on the service >you're using and do what you will with them. For instance, you could probably >push these out to a small app that pushes them onto the NR API (if it let's >you). Saying this, this isn't something I've tried - I'm not sure of the benefit of getting this data into NR, quite often the logging services will let you visualise the data somehow. -- Neil On Monday, 12 November 2012 at 22:38, Daniel Doubrovkine wrote: > Neil, thank you. > > Can you elaborate on this? Are you saying I can pull data I have in > papertrail right now into New Relic? > > On Mon, Nov 12, 2012 at 4:55 PM, Neil Middleton <n...@neilmiddleton.com > (mailto:n...@neilmiddleton.com)> wrote: > > If you're using an add-on such as Papertrail you can pretty much track what > > you want via your own searches and alerts. > > > > I'm not sure of any way of doing it with NewRelic. > > > > N > > > > -- > > Neil > > > > > > On Monday, 12 November 2012 at 21:53, Jonathan Baudanza wrote: > > > > > 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 <dbl...@dblock.org > > > (mailto:dbl...@dblock.org)> 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 > > > > heroku+unsubscr...@googlegroups.com > > > > (mailto:heroku%2bunsubscr...@googlegroups.com) > > > > 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 > > > heroku+unsubscr...@googlegroups.com > > > (mailto:heroku+unsubscr...@googlegroups.com) > > > 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 > > heroku+unsubscr...@googlegroups.com > > (mailto:heroku%2bunsubscr...@googlegroups.com) > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en_US?hl=en > > > > -- > 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 > heroku+unsubscr...@googlegroups.com > (mailto:heroku+unsubscr...@googlegroups.com) > 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 heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
