When we are executing an application with a significant number of processes, we cannot afford to stop the operation to review what is happening outside of production, for this reason, a tool that allows us to have greater observability and a level of detail is key in the management of our project.
Imagine you are responsible for the health of your node applications and you have N|Solid in place, you would regularly check the N|Solid Console to review your Projects and Applications to quickly view how well things are running.
The role of app performance monitoring (APM) extends far beyond crash monitoring—it is an integral part of creating a top-notch user experience that keeps your users happy and coming back for more.
It’s been a while since the last update post in july 2021, not that we haven’t updated OctoPerf since then but the additions we’ve made are not easy to share in a blog. Allow me to take an example.
Errors happen. Despite best efforts, no piece of software is perfect. Unintentional issues with code, updates to existing frameworks, or unexpected interactions with other tools can all cause errors. As a result, it's critical for companies to deploy robust and reliable error reporting processes that help them proactively identify potential issues and improve operational outcomes.
Developers test their code in chunks as it is written. Error monitoring during the development cycle alerts engineers when conflicts arise and helps them identify the root cause. So, you may wonder then, in the age of DevOps and continuous delivery, is end-to-end testing still needed? Not only is it viable, but it is also essential to validate requirements, configurations, and functionality.
How often do you face an issue with a service that doesn't work and you don’t know why? How often is it related to some external services, dependencies like a database, or queue mechanism you are using? Of course, you could check each service from time to time, and you could run some smoke tests against the service, but it will not give you an answer if “service is not working because the connection to MSSQL failed.”
