It’s official, summer is over. So grab yourself a pumpkin-spiced food item of choice and check out what the Sentry team has been up to this past month. From introducing new features, product improvements, and integrations, we can objectively say we made Sentry at least a smidge better this month. Keep reading to see how the latest developments can make your debugging experience less painful.
As modern software systems become increasingly distributed, interconnected, and complex, ensuring production reliability and performance is becoming harder and more stressful. Seemingly nondescript changes to our infrastructure or application can have massive impacts on system uptime, health, and performance, all while the cost of production incidents continues to grow.
As you may have already discovered (or will soon encounter), many vendors that offer uptime monitoring solutions charge a setup fee. But instead of seeing this as a legitimate cost, you should view it as stop sign. There are three reasons why.
Although the title of this blog poses the question “Why do Monitoring Service Thresholds Overlap?”, really the question should be: “In Remote Monitoring and Management Solutions, Why Do Some Monitoring Service Thresholds Overlap?”. That’s a bit of a mouthful, but it’s what I’m going to look at in this blog. Here’s why overlapping thresholds in remote monitoring matter.