New Relic now supports Node.js(blog.newrelic.com)
blog.newrelic.com
New Relic now supports Node.js
http://blog.newrelic.com/2013/10/24/node-joins-new-relic-family/
14 comments
I really wanted to like new relic, but sadly their aggressive and pestering sales/account managers put me off. This was after we signed up!
I must admit I have been annoyed by it in the past but it seems to have dropped off a little recently, I wonder if things are changing.
Misleading title.It is more about "New Relic now supports Node.js"
Don't blame me. The official policy is that titles on HN must be the title as given on the referenced page. I would have made it something more descriptive, but that's a waste of time.
PG's comprehensive explanation is here: https://news.ycombinator.com/item?id=6572466
Added in edit: Hah! I see now that the title has been changed so that it isn't the title on the page, even though it wasn't "egregious linkbait, or false." Color me confused. I'm not complaining, the new title is probably better, but changing it seems completely at odds with PG's statement.
PG's comprehensive explanation is here: https://news.ycombinator.com/item?id=6572466
Added in edit: Hah! I see now that the title has been changed so that it isn't the title on the page, even though it wasn't "egregious linkbait, or false." Color me confused. I'm not complaining, the new title is probably better, but changing it seems completely at odds with PG's statement.
Yeah! Normally this title format means "X acquired Y", so made me do a double take.
Interesting to read the (linked) article on how they actually built the support: http://blog.newrelic.com/2013/10/22/new-relic-node-js-apps/
Since node's native support won't land until 0.12, does anyone know what the downsides of the polyfill are? Is there a much larger performance hit?
Since node's native support won't land until 0.12, does anyone know what the downsides of the polyfill are? Is there a much larger performance hit?
I was fortunate enough to attend a talk given by the person primarily responsible for writing it and he (as well as some people already using it) said they see no discernable performance difference.
Does anyone know if New Relic can be used in a more limited capacity with unsupported languages?
I've been building an OpenResty/Lapis app (Lua) and would love to be able to get some visibility into my Heroku dynos.
I've been building an OpenResty/Lapis app (Lua) and would love to be able to get some visibility into my Heroku dynos.
We're working on a somehow similar product that works by understanding the network traffic received and sent by your application. This means it can be language independent. http://packetbeat.com/
That's really cool! Great name, too. Probably a little less comprehensive than New Relic's offering, but I like that you don't have to do any kind of integration.
On a side note, the font you guys use for parts of your site is way too thin. It's really hard to read. See the items in the bottom/middle: http://cl.ly/image/2H0r1d1b210p
On a side note, the font you guys use for parts of your site is way too thin. It's really hard to read. See the items in the bottom/middle: http://cl.ly/image/2H0r1d1b210p
Thanks! We're working on adding more information to the website and also on improving the design, based on the feedback we got so far.
(Product Manager @ New Relic here)
We launched a bunch of stuff today, including a new Agent SDK that is designed for exactly this purpose. It's beta today and has limited functionality, but give it a shot and let us know how it goes for you.
https://docs.newrelic.com/docs/features/agent-sdk
We launched a bunch of stuff today, including a new Agent SDK that is designed for exactly this purpose. It's beta today and has limited functionality, but give it a shot and let us know how it goes for you.
https://docs.newrelic.com/docs/features/agent-sdk
With the New Relic Platform, you can write a Plugin to report data about anything you want. There are Java and Ruby SDKs, and if you prefer, there is an HTTP API.
https://newrelic.com/platform https://docs.newrelic.com/docs/plugin-dev/
Hope that helps you. If you have any questions, feel free to ask.
https://newrelic.com/platform https://docs.newrelic.com/docs/plugin-dev/
Hope that helps you. If you have any questions, feel free to ask.
https://addons.heroku.com/librato provides insight into your Heroku dynos.
https://addons.heroku.com/adept-scale does too to some extent.
https://addons.heroku.com/adept-scale does too to some extent.
Is the best reason to use Node.js really just that it supports asynchrony? I'm sure Go also has that and Erlang has existed for a long time. There are many other options, so why Node?
Some advantages:
- Yes, built-in async support is very important
- Everyone has to write JS at some point anyways -- it helps to take advantage of what everyone already knows
- You can easily share code between the client and the server
- There are tons of modules available on NPM already
- The compile-to-JS languages are getting more practical every day, and you can integrate them with existing JS code
If you consider time spent learning a platform compared to what you get out of it, Node.js is probably the best bang for your buck today.
- Yes, built-in async support is very important
- Everyone has to write JS at some point anyways -- it helps to take advantage of what everyone already knows
- You can easily share code between the client and the server
- There are tons of modules available on NPM already
- The compile-to-JS languages are getting more practical every day, and you can integrate them with existing JS code
If you consider time spent learning a platform compared to what you get out of it, Node.js is probably the best bang for your buck today.
Node came at a time when client side JS was really starting to take off. I can't speak much about Go or Erlang, but I suspect a lot of it has to do with marketing and some lucky momentum.
It also helps that tools like Grunt are Node based, causing frontend devs to look to Node when they need to stand up a back end. At least, Grunt was a pathway into Node for me anyway.
It also helps that tools like Grunt are Node based, causing frontend devs to look to Node when they need to stand up a back end. At least, Grunt was a pathway into Node for me anyway.
Node allows you to write JavaScript on the server, which is pretty awesome if you're interested in sharing code (validation, etc) on a client-heavy web app.
I don't have any experience with Go or Erlang, but Node's particular brand of asynchrony is all about non-blocking IO. There are no threads -- all instructions happen in one thread.
I don't have any experience with Go or Erlang, but Node's particular brand of asynchrony is all about non-blocking IO. There are no threads -- all instructions happen in one thread.
The way I see it, go & erlang is rather about concurrency (and parallelism). async the node way is single threaded.
Anyway, the reason probably has rather to do with JavaScript (V8's speed) and node's eco-system (tools, libraries).
Anyway, the reason probably has rather to do with JavaScript (V8's speed) and node's eco-system (tools, libraries).
Don't run node.js, but my experience with New Relic has been excellent - great product from folks who have been knowledgeable, responsive and friendly without exception.
This genuinely couldn't have came at a better time.
We've just released our internal application powered by Node.js — our first. Since releasing we've been experiencing random 504 errors with no way of tracking them down, since they run in a Dokku container. Attaching to the logs displays nothing either.
This will really help! Thanks guys!
We've just released our internal application powered by Node.js — our first. Since releasing we've been experiencing random 504 errors with no way of tracking them down, since they run in a Dokku container. Attaching to the logs displays nothing either.
This will really help! Thanks guys!
Does this mean we're any closer to New Relic support for Tornado's async api? Thus far, New Relic has only supported WSGI apps. [1]
[1]: https://docs.newrelic.com/docs/python/python-agent-and-torna...
[1]: https://docs.newrelic.com/docs/python/python-agent-and-torna...
Props to the New Relic node team... I remember when they started work on this, I was skeptical it could even be done (async tracing is a pain in the ass)...
Congrats, and great work, for getting the (near) impossible accomplished.
Congrats, and great work, for getting the (near) impossible accomplished.
We've used the beta for months, very happy with it! :-)
Excellent news! Loved using New Relic for Ruby, can't wait to start using it for Node.
Congrats on getting this running. I know there were a lot of tough issues surrounding this and I'm glad it's finally up. I've been using this on http://gitignore.io since Feb and it's been great.
I have been waiting for this for a long time. :)