New Resources UI
Hey all, welcome to the beta for the new UI! With this includes the new look and feel of Resources. Here’s a quick glance at what’s new: Info tab with properties search and filter Alerts tab consistent with Alerts page Maps tab consistent with Topology page Graphs navigation Alert tuning Inventory tab with bulk actions Overview tab Resource dashboard visibility and management The official product documentation will cover the functionality in more depth: https://www.logicmonitor.com/support/resources-new-ui-overview Please take the new UI for a test drive and let us know what you think!Dashboards UIv4 is available starting August 23!
We're thrilled to announce an update to enhance your dashboard user experience. With this UIv4 update, we’re introducing an intuitive new design that aligns with the new LM experience, making your dashboard navigation more seamless with other areas of the product. Update the toggle on the top navigation to ‘New UI Preview’ to see the following changes. What's New: 🎨 Revamped User Experience: Our team has been hard at work reimagining the dashboard's visual appeal. With a new skin, your dashboards are now in line with the rest of the UIv4 changes that you’ve become accustomed to. While the core functionality remains intact, new aesthetics that consistency across the platform improve the quality of our LM experience. 🛠️ Enhanced Widget Editing: We've heard your feedback, and we're excited to introduce a new capability to the dashboard widget editing process. Say goodbye to the hassle of publishing a widget to witness changes – you can now preview your modifications in real-time before hitting that publish button. This means you have the power to experiment, tweak, and fine-tune your creations with the confidence of knowing exactly how they'll appear to your dashboard consumers. Thank you for being a part of our beta community. Your insights and feedback have been invaluable in shaping these new changes. We take pride in helping guide our analytics journey and want to get you to your destination in style. As always, your feedback is essential to us, so please don't hesitate to share your thoughts and experiences as you dive into these exciting new features. Stay tuned for more updates, and happy dashboarding! Best regards, Faran - Senior Product Manager for Dashboards and ReportingNew Settings Beta!
Welcome to the new Settings Beta! The new Settings page offers the same great functionality in the legacy UI with some new items that unlock powerful capabilities such as HTTP OAuth 2.0, Event Driven Ansible, and improved navigation. Your feedback is extremely valuable to us so please feel to chime in. What’s changed in Settings v4? Improved Navigation The first thing you might notice after enabling the settings preview is that it has a familiar structure in the left-hand navigation with an updated feel. The improved settings navigation comes with functionality to: collapse/expand core features in the navigation list along with filtering and sorting across the different settings areas. Audit Logs A couple of noteworthy mentions in Audit Logs is a more readable table structure with an easier to use Filter. You’ll notice that you can see much more information in the description with an arrow to expand more details at the end of the description. Account Information Account Information has three main paths: Portal Information, Portal Settings, and Financial. You’ll notice when you want to edit information that the controls will look different such as a pencil and when adding contacts information you don’t need to save each row. Contacts (previous UI) was renamed to Portal Information which more accurately describes its content. Portal Settings now contains contact information Financial has the same billing and payment information as before but with an easier to read structure with the familiar edit controls. Usage (Beta) This is an exciting new capability that lets you visualize LM license usage. Right now LM Logs and APM Metrics are supported if you’re using those products today. LM Logs - you’ll notice a “Products” dropdown that lets you select the product you want to view data for. At a glance, you’ll see month-to-date usage, can select some top usage analysis queries, and view cumulative usage. All of this data is filtered by the month and has control. One cool thing about the cumulative usage graph is that it has some forecasting ability which can be helpful for spotting potential overages. APM Metrics contains a combined view along with APM Push Metrics and APM OpenMetics. All views have the same visuals, controls, and functionality as the LM Logs product More products coming to Usage in future releases! Alert Settings Alert Settings should feel very consistent with improved readability. You’ll notice filtering capability added to Root Cause Analysis and External Alerting. Collectors Collectors page has a familiar table layout and controls to other pages in Setting creating a theme of consistency. Under the collector tab you have a new ability to filter by all collectors or collector groups. Within the table you have the ability to view if an escalation chain is configured in the table. If an escalation chain is found it will send the name. The collector actions for each collector are now in the a new bottom panel, with the info, resources, SDT and websites tabs The collector bulk actions can be performed now by selecting collectors (checking the boxes) and applying the bulk action from the menu when it shows up. (In UIV3, there was a button called actions present all the time) In the legacy UI, manage flows were hidden under the support button in the manage form, now these are accessible from the collectors main page bottom panel. The previous add flow had at least four modals, we have now reduced it to single modal for confirmation on save. The collector status screen was a blob of data on a single page earlier, now this information has been organized into a table that can be filtered and in a more readable format. The collector updates tab now shows a table with an update type column that helps users see what status the updates are in, (very similar to the SDT tab in alerts), showing the active/ scheduled NetScans. OpenTelemetry Collectors OpenTelemtry was introduced in the legacy Settings page allowing you to consume your application traces. Integrations We’re very excited to announce Event Driven Ansible and OAuth2.0 for Custom HTTP in the new Settings. Event Driven Ansible allows you to unlock the power of alerts and take remediation actions based on an alert. You’ll notice that the Integrations page has a familiar structure to the legacy UI with filters and tabs. All the controls for the table were moved to the left side column called “Actions” OpsNotes OpsNotes carries over the same structure from the legacy UI with updated filtering controls to help you find what you’re looking for with ease. LogicModules Updates to the LogicModules settings coming in a future release. Message Templates Message Templates introduces a new left hand navigation that allows you to filter by alert type. When an Alert Type is selected you’re able to define the alert and clear message with fewer clicks through the gear icon. NetScans NetScans page has a familiar table layout and controls to other pages in Settings, creating a theme of consistency. Under the collector tab you have a new ability to filter by all collectors or collector groups. NetScans no longer opens up with a blank right panel, it shows all the NetScans so the user has the option to view information by clicking the manage icon. User Access User Access has a new left hand navigation that contains some filtering options to help you find what you’re looking for. You can filter by groups and by users with the updated UI controls.Reports UIv4 now available!
Reports UIV4 can now be toggled on at the top of the Reports screen. Check out some of the new features including: a revamped reports tree navigation new reports listing overview with search easy report action access This is a per user setting. You can also easily toggle between UIv3 and UIv4 to see what’s changed. The Reports support doc has a more in depth view of what’s now available. We would love to hear your thoughts on the new UI and know more about how we can improve!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)Updates and Progress with UIv4
Hello! We want to thank you for all of the feedback that you have provided and update you on the progress we have been making. We have been working diligently to resolve any issues that have been reported. Most importantly, we understand that you’ve been experiencing slowness in the new UI. We apologize for any inconvenience, and want to assure you that we are working to improve the performance as quickly as possible. Our team of developers have identified some root causes for the slowness and are actively working on the fix. We are conducting thorough testing and benchmarking to ensure that any solutions implemented resolve the issues appropriately. There are also some additional upcoming improvements that we have implemented based on the feedback we’ve received: For Configs: A full screen option is now available and more information will load so that you can see more of the file. We’ve improved the search functionality so that you can search the entirety of the config file. You can now click anywhere in a line for the Resource Tree for easier navigation. For SDTs: Anyone with access to the SDT functionality will be able to see the new icon in the top right corner. Duplicates have been removed from view to avoid confusion. Anomaly Detection + Forecasting Improvements: We have streamlined the experience so that you can view anomaly detection and forecasting functionality with fewer clicks. And more small improvement fixes! These fixes will be available in v186 and 187. If there are any specific issues that you want to follow up on, please use this thread. Otherwise, create a new thread for any issues so that we can track them accordingly. Thanks! The LogicMonitor Product teamWhy is there an option to focus on the datasource or instance level?
I noticed that there is a “plus” icon next to nearly everything in the new UI, from resources to logicmodules to instances. The plus icon focuses similar to the eyeball in UIv3. If I select the “plus” icon next to an instance or datasource, it focuses only on that and the rest of the modules/instances on the device are hidden. I can’t think of any use case for that, and I could see it causing users to get “lost”. I would rather see the focus option removed from the instance/datasource level, and only be an option on the device or group level like it was in UIv3.Single instance vs. multi-instance logicmodules
These used to behave differently in the tree. A single instance datasource (or configsource etc.) would not have any children. If you wanted to see the data associated with that module under a device, you simply selected the module. In UIv4, you have to expand the module to show the one, singular instance under it and then click again to select it. This adds an extra click when navigating. This extra click has been avoided in the past by LM as a matter of policy (how many modules are in the “ungrouped” group to avoid adding another click to get to the data?). Also, now that multi-instance and single instance modules both have to be expanded to show the children/child, the new distinctive icon that tells you a module is multi-instance (circle with the letter M in it) makes no sense. Essentially everything acts like a multi-instance datasource. Since that’s the case, why call out the difference? In one way (adding the click) LM removed the distinction between single and multi. In the other way, they added another distinction between the two. To what purpose? Also, by having multi-instance datasources show up with an M instead of a D, the distinction there is also lost. Is it a datasource or a module? Does the M stand for module? Why doesn’t it just show a D?
