As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am looking for a way to get some sort of monitoring, statistic or management data out of a node.js server instance - not sure what to search for or where to start. Any advice appreciated.
Stats would be requests processed (if applicable) - number of connections and so on.
Don't know if it will fit your needs, but you can try to look at node-monitor. Also Joyent is doing some advanced real-time performance analysis stuff, but it's probably only for their cloud services.
Nodetime can monitor different metrics, such as HTTP Response time, CPU time, OS Load, etc. It is also possible to set up email Alerts based on these metrics. More in the blog post Monitoring Node.js Application Performance.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
IndexedDB API on node.js will be very useful for some app.
Why IndexedDB is not available in node.js?
IndexedDB API does not depend on DOM, even though it does use some DOM error and event style.
It's possibly because IndexedDB is part of a different body of standards. Node.js is just ECMAScript (via Google's V8) along with their own API. Also, it may not help that IndexedDB is still in "Draft."
But, more likely it's for the same reason Node.js doesn't offer any database drivers: it's not trying to solve those problems. It's just trying to offer the APIs that assist someone who does want to solve and implement them.
And, for that, it appear at least one such project has already started: indexeddb-js. But, also have a look through IndexedDB in the NPM Registry.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I have a production web service built with Node JS(HTTP Server) on a Linux box with a HAProxy Load Balancer and wanted some kind of graphical tool to do live reporting on the server. I specially wanted to look at requests/min, request failures, etc. Anything out there people would suggest. I need something non-intrusive b/c I will be handling 20mil+ requests a day.
Have you looked at cube (https://github.com/square/cube), graphite/carbon (http://graphite.wikidot.com/) or opentsdb for such data monitoring/display?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I could not find anywhere on google information about Spotify Apps that would say anything about the future plans of this expansion, in particular, if it would be possible to publish your own app somewhere on the future Spotify App Store or something similar to that. Does anybody know if this feature is in the future development plans of the company?
The process for getting your application published on the App Finder is here:
https://developer.spotify.com/technologies/apps/process/
Specifically, we request you submit a concept to us first so we don't end up with duplicate apps, then once that's approved the process is fairly standard - you make the app, we make sure it's good enough for the App Finder, then it gets published.
If you've already started to make an app, no matter - just submit it as a concept anyway and we can work from there.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions.
I'm new to Node.JS, already Googled for aswers but there is a lot of ways of doing this.
Do you have some sort of math to know when I'll need to scale my Node.JS server? And what tools you use for monitoring server performance and error track?
Thanks!
As #ThiefMaster said, this depends on your system. You need to monitor the requests for your site, the CPU load, memory footprint etc and decide if and when to add mode servers.
If you want to know more about Node.js performance read this good article: http://blog.3rd-eden.com/post/5809079469/theoretical-node-js-real-time-performance
If you need a Node.js metrics library, there are 2 ones which I can recommend: https://github.com/felixge/node-measured
https://github.com/mikejihbe/metrics
Resources:
monitoring a node.js server
I recommend monitoring your event loop and if it starts to back up more than 200ms on a regular basis, you'll need to scale.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Well of course we could use quartz.net, which comes with nice features like concurrency control and load balancing. However it seems a bit bloated to me.
1) Am I wrong about this ?
2) If not how would you implement a cloud compliant scheduler (ie: either deployed on premise or within azure) ? Is Lokad scheduling the best approach ?
Based on the answers to this question ( Recommend a C# Task Scheduling Library ) quartz.net running in a worker role instance is the way to go.