From da454756921398b8e84e460cb32868d78d5eb794 Mon Sep 17 00:00:00 2001 From: Aarti Verma <75892381+vermaaarti@users.noreply.github.com> Date: Wed, 12 Oct 2022 03:14:25 +0530 Subject: [PATCH] Added content for Debugging using APM (#2347) * Added content for Debugging using APM and added blog link for complete information * Update content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/102-using-apm.md Co-authored-by: Kamran Ahmed --- .../116-nodejs-more-debugging/102-using-apm.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/102-using-apm.md b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/102-using-apm.md index f7e0ab1ec..61b0f07a9 100644 --- a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/102-using-apm.md +++ b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/102-using-apm.md @@ -1 +1,10 @@ -# Using apm \ No newline at end of file +# Using APM + +As much fun as it is to intercept your container requests with inspect and step through your code, you won’t have this option in production. This is why it makes a lot of sense to try and debug your application locally in the same way as you would in production. + +In production, one of your tools would be to login to your remote server to view the console logs, just as you would on local. But this can be a tedious approach. Luckily, there are tools out there that perform what is called log aggregation, such as Stackify. + +These tools send your logs from your running application into a single location. They often come with high-powered search and query utilities so that you can easily parse your logs and visualize them. + +Free Content +Debugging using APM