Beginning in mid-February 2017, improvements will be available on the Monitoring pages in the Alert Logic® user interface (UI) to reduce loading time and improve the overall monitoring experience for Alert Logic Threat Manager™. When a Monitoring page is accessed, an automatic search is no longer performed, allowing customers to immediately enter filters as needed and perform a search without waiting for default results to load. Additionally, you can now limit search results to a specific child customer or sub-parent, which can reduce load time for customers with multiple clients.
The Monitoring pages affected include the following four pages:
Perform Searches Without Waiting for Default Results
Results now display on Monitoring pages only after performing a search, rather than automatically loading when a Monitoring page is accessed. This enhancement allows you to set filters and select the data you want to see without first waiting for a default search to load.
When you first access a Monitoring page, such as the Events page, a message displays in the Results box to indicate you need to perform a search to display results.
Simply enter filters as necessary and click Search to perform the search and display your results.
View Data for Child Customers and Sub-Parents
Customers with child customers and sub-parents can now view data for a specific child customer or sub-parent. This enhancement allows you to limit a search to only the necessary customer or set of customers, reducing loading time for results.
To limit results to a specific customer or sub-parent, simply select the customer in the new Customer Selector drop-down field directly under the Alert Logic logo in the top-left corner.
When this new filter is used, you can greatly reduce the amount of time it takes to load results when data for only one customer is needed.
Note: The Customer Selector field only displays if your account has child or sub-parent customers.
For more information about monitoring blocks, events, and incidents in the Alert Logic UI, refer to our Incidents documentation.
For more information about monitoring cases, refer to our Cases documentation.