<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitoring on Scholion</title><link>https://scholion.thluiz.com/tags/monitoring/</link><description>Recent content in Monitoring on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Thu, 22 Oct 2026 02:56:08 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Node.js Best Practices — Error Handling and Logging</title><link>https://scholion.thluiz.com/notes/node-js-best-practices-error-handling-and-logging/</link><pubDate>Mon, 21 Sep 2020 15:10:01 -0300</pubDate><guid>https://scholion.thluiz.com/notes/node-js-best-practices-error-handling-and-logging/</guid><description>The article recommends documenting API errors with GraphQL, exiting on unknown errors, logging with mature tools, testing error flows, monitoring app health, and catching unhandled promise rejections.</description></item></channel></rss>