On one hand we have Alyvix 3, our visual monitoring tool for continuously tracking the user experience.
We’ve also just released Alyvix 3 Server, which lets us easily schedule and administer our test cases.
And we also have our NetEye monitoring system.
In this blog, I’d like to show you how we can integrate all three elements.
In order to do this we’ll use a script created by our guru Jürgen Vigna. Thank you Jug! (https://www.neteye-blog.com/jurgenvigna_wuerthphoenixneteye/) This Perl script lets us contact Alyvix Server, and can be run either on the master or on the satellite, depending on where Alyvix Server is located.
The logical steps to configure this integration are:
Here are the results after configuring a satellite by running the script on the Windows 10 client:
Every time that the service runs, we collect the metrics on Alyvix Server, and then with our script we pull those metrics into our NetEye Master:
This test case is very simple − it just collects anonymous metrics about navigation through the Alyvix 3 documentation. In the output of the service I have a link to the Alyvix Server report that shows the log of the test case run:
And if the test case doesn’t run, then we see the log with the error:
It’s possible to get the history of the test case since the logs are stored on Alyvix Server. We can find it on Alyvix Server either as a report (HTML) or via the API (JSON).
Here we’ll show how to schedule a test case by creating an example called “documentation”. It’s very simple:
2. In the Testcases tab we set the test cases to schedule:
3. In the last tab we set the workflow choosing the test cases
4. In the end we have this situation for our test on the Workflows tab:
In this state we can stop and (re)start the workflow, and the red or green circle will show us if the selected test case is running (red) or is waiting to run (green). If instead it’s gray, there’s a problem that needs to be investigated.
Finally, we have our Grafana dashboard that collects the Alyvix test case metrics:
If you have a large number of test cases and multiple servers, it’s possible to aggregate this information, allowing us to see where the test cases were in error and where they were okay.