Are Product even here?
A Beta process should be a little more two-way than this. There are a good number of us here providing feedback, yet there is no response from any representative of the Product team. To whomever owns the UIv4 rollout… Please could you assign someone to acknowledge the feedback we are sending (COUGHperhapswithaticketnumber)September 2023 Check-In - Who's using UIv4 as their main UI?
One measure of UIv4’s success will be that people are choosing to use it by default. So go for it! Who’s using it by default? On which pages? When do you findyourself having to switch (in either direction)? Where is it better than UIv3? Where is it worse than UIv3? What’s still missing?V192 UIv4 Release Notes
Here are the UIv4-specific Release Notes for UIv4 (from https://www.logicmonitor.com/release-notes/v-192-release-notes): Enhancements Removed text limits for all report types. You can find report-specific threshold limits in the documentation for each report type. For more information, seeReports New UI Overviewin the product documentation. Added validation to the dynamic thresholds configurationformfields that will prevent users from saving entries with invalid values, such as negative values in lower and upper bound fields. Fixed Issues If you receive a 401 status on a new UI page, you may need to refresh the page and log back into your LogicMonitor portal. Optimized the behavior of the stack view for Graphs to improve the representation of the data. Previously, the stacked graph view was difficult to use because some datapoints overlapped over others. Made the Graphs tab the default view for Resources and DataSources. You should no longer see a plus sign (Add new) button on the Instances tab for a module when Active Discovery is set to Yes. When you enable OpsNotes, you should see them applied across all groups, resources, and so on, so that you don’t have to enable it each time. Fixed an issue to ensure that OpsNotes created in the Legacy UI display as expected in graphs and lists after you enable the new UI. Fixed an issue where Test Script for Groovy scripts in PropertySources was not working. Fixed an issue to prevent users from creating static thresholds that did not contain at least one severity value, and from creating more than one All Day threshold. There are now checks to ensure that you include at least one severity field, and you will not be able to Save an All Day threshold if one already exists.