Out of the box, Sentry notifies you about crashes in your JavaScript apps and gives you useful tools to help you debug what your app was doing when it broke. If Sentry stopped there, it would still be great and valuable, but it’s possible to maximize your front-end debugging potential with just a few manual optimizations.
One perennial problem we face in monitoring is dealing with noise. We don't want to miss important signals, but sorting through all the noise can be a chore. Ideally, we want to spend as little time as possible doing the setup work needed to achieve excellent signal-to-noise ratio. The feature we've just released will help you get closer to that optimal setup faster, with less work.
To build stable and flexible software, we need to keep software design principles in mind. Having error-free code is essential. However, well-designed software architecture is just as important. SOLID is one of the most well-known sets of software design principles. It can help you avoid common pitfalls and think about your apps’ architecture from a higher level.
The CFEngine policy analyzer is an awesome new service introduced in CFEngine 3.13. The policy analyzer allows you to quickly debug policies and inspect what is going on under hood of CFEngine. A known challenge with CFEngine, and most DSL based automation tools, relates to understanding what is actually going on during live operations. Many users view it as “black-box magic”. Unfortunately, the amount of magic and the size of the black box increases with the level of automation.
When looking at the performance of your website, web service,or API over a span of time, you will notice variations in the performance reported by the monitor. You may also notice inconsistencies between the performance reported from different monitors. Why? Why do you see spikes in your charts?
