We’ve added management buttons to more quickly access common check actions when viewing a check report.
To view the new buttons, click the check’s name in your Monitoring view to see its report. You can now Edit, Pause, set Maintenance, and more directly from the report:
We have made a small improvement to the way you select date ranges for check analysis and reporting in the UI. It is no longer necessary to click an “Apply” button after selecting the range. You can now simply click outside the selector window, or click Done, to accept the date and update the graph.
For more information on selecting date ranges, see our documentation.
An upcoming release will include a significant improvement to Status Pages, with more features and customization options available. The Inspire 2.0 theme will provide a sleek, updated appearance for your Status Pages, along with additional customization options.
To preview the new version:
Navigate to Status Pages > All Status Pages
In your All Status Pages view, click More Actions > Preview Inspire 2.0
We highly recommend reviewing the appearance of your page under the new theme to make any adjustments ahead of time. Custom CSS and headers/footers may display differently on the new version.
We have updated the default sort order of the Alerts table. Ongoing alerts are now displayed at the top, followed by alerts with an end date and time. This makes currently active downtime more easily visible and places higher visual importance on issues that should be prioritized.
For more information on Alerts, see our documentation here.
As part of our commitment to continuously expanding our coverage of third-party services in Cloud Status checks, we have added a new monitoring option: Citrix Cloud.
For more information on Cloud Status checks, see our documentation here.
We have added a new Check Visibility option to the Element exists step in Transaction Checks.
Wait for Element To Exist/Not Exist Wait for Element To Contain Text/Not Contain Text Element Should/Should Not Exist Element Should/Should Not Contain Text
Previously, a step would pass as long as the element was found in the page, even if it was not visible to the user. Now with the update, you can now choose to also validate that the element is actually visible.
To use this option, in the Transaction Check, tick the Check Visibility box.
Transaction Check with the step Element Should Exist
An element is considered visible when all of the following conditions are met:
It has computed styles.
It has a non-empty bounding client rect.
Its visibility is not set to hidden or collapse.
For more information on our Transaction Check, check our documentation.