Issue with threshold permissions in new UI
Starting with portal v207, there are some updates to the "Settings > Users and Roles" page of the new UI. These changes include a new permission for modifying group-level thresholds. This new permission can be found within the role configuration in section "Permissions > Modules > Access Groups > Resources: Group Threshold". This permission did not previously exist for roles before portal v207. When the portal upgrades to v207, any custom roles which previously had permissions to modify thresholds will no longer be able to do so. I confirmed with LM support that this is expected. This affects ALL threshold changes, not just group-level thresholds like the name of the permission suggests. So FYI for other LM admins out there, once you update to portal v207 you may need to manually update any roles which should have access to modify thresholds so that they include the permission I mentioned above.Solved168Views11likes2Comments- 117Views8likes2Comments
Issue with time-based thresholds in UIv4
In UIv4, I am unable to set time-based thresholds which were possible in UIv3. Time-based thresholds are still supported by UIv4, but are much more limited. For example, lets say I want to exclude the time window of 08:00 - 09:00 from alerting for a certain threshold. I could use a time range of "09:00 to 08:00", which would effectively exclude 08:00 - 09:00 from alerting without needing to set SDT. In UIv4 setting that time-based threshold is not possible. If I select 09:00 as the starting-time for the threshold, the only options available as the end-time are 09:15 and later. Which means setting a threshold of "From 09:00 to 08:00" is not possible unless I switch back to UIv3.60Views5likes1CommentUIv4 Alert Tuning
UIv4 alert tuning is a great improvement over UIv3 because of the ability to filter by DS name. It's the only piece of UIv4 that I choose to use over UIv3. However, there is still a big problem with it: DS name != DS name. Every DS has two names, the name and the display name. The name must be unique and usually is one word (though interestingly doesn't have to be). The display name does not have to be unique. This is a good thing because some DSs while having different names and gathering data differently represent the same family of data. Count how many DSs are for CPU. It's nice that they can all share the same name (though because of development happening across years/decades with different developers it isn't consistently done. I'm ranting; back on topic...) When you search for a datasource, you cannot search by unique name, but only by display name. So if you want to modify a threshold for one datasource and there are two others with the same display name, it can be really difficult to tell which datasource you're editing. Consider this case: I need to modify the thresholds for VMware_vCenter_VMSnapshots. Which one is it? Hint: the other is "VMware_vSphere_VMSnapshots". Can you tell which is which? LM: Give us the option to display the module's unique name in the table Give us a checkbox that will turn on display of the module's unique name in the search results. Those who don't care won't turn it on, but for those who do we can turn it on and not have to guess which module we're customizing thresholds for.98Views8likes5CommentsIssues with new dynamic filtering feature of UIv4 Dashboards
I really like the new dynamic filtering feature in the UIv4 Dashboards page, I think it really adds a lot more usability/flexibility to dashboards and its probably my favorite thing so far about Uiv4. Having said that, I did notice a few issues after playing around with it: only System and Auto properties are available for filtering. Would be great to allow custom properties to be available as well Would like to be able to save filter “Views” across multiple dashboards, instead of having them need to be created for each dashboard Would like to have saved filter Views available to all users once created, not just the user which created the filter View Internal Websites are being shown on the dashboards, even when filters are set for properties which do not exist on those internal website checks filtering works fine for Resources, but unintended Website checks are being included Only seems to be including Internal Website checks, not External checksSolved125Views4likes4CommentsSLA Widget instance limit in UIv4 Dashboards - no error message when exceeded
The SLA widget (unfortunately) has a 2000-instance limit. In UIv3, when the limit is exceeded the widget will show an error message saying “instance limit of 2000 is exceeded”. So this at least tells me what the issue is. In UIv4, when the instance limit is exceeded for an SLA widget it just says “NaN” with no specific error message. It should at least show the same error message as before so users know why the widget is not populating.80Views7likes0Comments