Paying attention to your logging strategy from the beginning of your project is a good idea — otherwise, you might run into problems. This might sound like an empty warning, but take a step back from your code and think good and hard about how you're logging right now and what you're doing with that information. If you don't really have a use for it, then you might as well stop logging, but if you're actually getting insights from it, either when troubleshooting, or through some sort of analytics tools, then make sure you can keep doing so after you've scaled up (or down) your architecture. Can you trust that you will be able to process your logging data if you're under an elastic scaling architecture?


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to
 
javascript,tutorial,performance,node.js,logging,scale