node.js ko
dunno
dunno
by ActiveNode
It is a tool to track your node.js application performance. It is an express middleware that is used to hook into your application and track app performance.
The app is in 2 parts. a monitor that is a node module that is inserted into a express webapp(npm module)
It hooks up as a middleware and tracks the requests/responses to provide/track performance, user agent/ status codes etc.
The Web app is a way of displaying this information in form of charts/maps/tables etc. The idea is similar to NewRelic’s RPm
Judging Instructions
The webapp that displays the stats is also the dogfood. so it may look weird in the beginning.
Tested only on Mac. Works on Chrome and Firefox :–) {Needs socket.io for map visualization}
We have not tested it on IE/Safari.
Who
sreeix
nikhilfernandes
nilakanta
niketkumar — bangalore
How
express/socket.io/geoip/redis redistogo
http://www.pvmgarage.com/2010/04/touch-the-future-create-an-elegant-website-with-hmtl-5-and-css3
Votes
Your Vote
Voting is now closed.
Other Votes
(19)
cruciallyjudge
therazorbladejudgeThe basic idea is nice but it is missing a lot of basic analytics tools like graphs and analysis. Finding out about peaks and current load is important. The per-request approach is only useful if you can track it over time and average it to some useful data. Also, the map – while pretty – isn’t very useful. A simple pie chart showing split by countries/regions is probably easier to use and make sense of.
mranneyjudgeTracking metrics on app usage is a really useful feature. I like that it’s implemented as an Express middleware, which should make it usable by many people.
I wish the stats were displayed in a way that is more realtime. Tracking this stuff obviously happens in realtime, but it’s hard to get a sense for that with the way they are displayed.
- contestant
Thanks @mranney, we use your awesome redis client to store data' but for real time monitoring we used th redis monitor command, but the redis client is broken for monitoring when contents are stored as json, I am submitting a patch. Then We can make all the stuff real time. And it’s the lack of time at knockout that made us not go fully realtime
- mranneyjudge
Oh no, sorry about that. I already have a pull request in my queue for the “JSON quoting over monitor” bug. I didn’t want to change anything with node_redis until after NKO.
I’m looking forward to seeing what you guys come up with.
slightlylatejudgeI like where it’s going. Augmenting with Web Timing data from the clients and showing error/status codes and outbound file sizes could go a long way toward making this indispensable. Nice work.
- contestant
Thanks for the feedback, the stupid thing is all the above mentioned( except content length) is there in redis, we just don’t display it on the page. We also had a CPU/ memory tracking changes lying on another branch unmerged. Cheers Sreekanth
dan_mangesjudgeUtility: This could be a really useful service if more work is done on it. Demonstrated by the success of New Relic, there’s demand for drop-in performance monitoring tools.
Design: The site looks nice, navigation was simple. I think the /top page could have been separated out into different categories of metrics (performance, usage, demographics, etc.) which would make the data easier to glean.
Innovation: Not a unique idea (as the already mentioned New Relic), but I liked the real-time map — not something typically offered in tools like this.
Completeness: I think quite a few features would need to be added before Node developers would start dropping this into their applications, but for the functionality that has already been developed, it worked great.
pbcomm
contestantryanza
contestantVery cool, It’s always important to have stats on how your site is performing, to allow improvement and optimization! Thanks!
jerrysievertjudge
fredyatesivjudgevicapow
contestant
Couldn’t find the source code, 404?