Alyvix Server and previous versions have helped us create a usable visual monitoring system focused not just on individual checks, but orchestrating groups of checks to regularly monitor multiple, distributed applications.
With the introduction of Alyvix Service, that task has become even easier. Why is that, and why should you migrate from Alyvix Server to Alyvix Service? Read on to find out!
These days who has time to check out new software? You could easily spend half a day figuring things out reading the website. Well, we've got you covered with our 2 minute video that explains it simply: what Alyvix is and what Alyvix does. In fact it takes less time to watch than it does to read this article!
Just like private enterprises, government agencies operate web services running vital services that need to be monitored for availability and responsiveness. Today we'll talk with Gabriele Cecco, who created a visual monitoring test case for a regional government. We'll get his insights into both some important features, as well as how to diagnose what's going on when you're building a test case and it doesn't work the way you expected.
If you've worked with Alyvix for a few years, perhaps you've noticed every so often that your test cases stop working for no apparent reason. If the underlying problem isn't an actual system fault (congratulations, your monitoring is working as intended!) then the cause is almost always a change in the interface that you're monitoring.
While some large "breaking" changes will obviously require you to create a new Alyvix test case, more often it's just a minor change, for instance Alyvix can't find a button that's been moved due to a software update, or a multi-user system has persistent window properties. In this best practices blog, I'll show you how you can build more robust test cases so that these minor interface changes won't interrupt your monitoring and keep you from rebuilding your test cases.