The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
You’re in the process of creating and launching new softwareand you want it to be as stable as possible. Or, maybe your software has been running for a while, but you’re frustrated with the bug-reporting workflow in place. Either way it’s time to look for a crash reporting process that fits your application. This leads to a natural question: Should we build it? Or should we buy it? To expand on this question, which will be better for my business?
Most of us here at BugSplat spend the majority of our day at our computer. If you are reading this post, there's a good chance that you probably do too. And, like us, you probably expect that computers are just supposed to work for you. However, in my experience, this close relationship we share with our machines just expands the realm of possible annoyances we encounter day-in and day-out.
If you are using InfluxDB to monitor your data and systems, then alerts may be an essential part of your workflow. We currently have a system for monitoring your data whether it enters a critical or non-critical state. Here I’m going to give a detailed guide on setting up alerts using our InfluxDB Cloud product as well as some best practices for having a good experience using alerts.
Digital transformation has now become a reality. It has moved a long way from being an option to a necessity, especially after the outbreak of COVID-19. While every department in an organization is being digitized, businesses reckon digital experience management as a key strategy in optimizing their transformation journey and also in creating a robust business model.
Memory leaks are something every developer has to eventually face. They are common in most languages, even if the language automatically manages memory for you. Memory leaks can result in problems such as application slowdowns, crashes, high latency, and so on. In this blog post, we will look at what memory leaks are and how you can avoid them in your NodeJS application. Though this is more focused on NodeJS, it should generally apply to JavaScript and TypeScript as well.
