info/developer-roadmap
1
0
Fork 0
mirror of https://github.com/kamranahmedse/developer-roadmap.git synced 2025-02-25 03:52:59 +01:00
Code Issues Releases Wiki Activity

Added content for Debugging using APM (#2347)

Browse Source 
* 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 <kamranahmed.se@gmail.com>
This commit is contained in:
Aarti Verma 2022-10-12 03:14:25 +05:30 committed by GitHub
parent 676b61c168
commit da45475692
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/102-using-apm.md
View File

@ -1 +1,10 @@
# Using apm
# 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.
<ResourceGroupTitle>Free Content</ResourceGroupTitle>
<BadgeLink badgeText='Website' colorScheme="yellow" href='https://stackify.com/node-js-debugging-tips/'>Debugging using APM </BadgeLink>