Why 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.
Matt Whitney
Posted 3 years ago·Last reply 3 years ago
16 comments
LM User
·3 years agoSo far, my feeling is: if you moved the magnifier over to the right hand side, it wouldn’t be an issue. Those who want to use it will find it and it won’t be in the way of those who don’t.
LM User
·3 years agoAnother general UIv4 frustration: cancel buttons. If the form is not dirty, I don’t need a scary message about losing stuff.
LM User
·3 years agoResizing columns is also pretty jerky. This causes me to have to slow down to wait for the display to catch up to the position of my mouse to make sure the column ends up the size i want.
LM User
·3 years agoWhen i use the focus feature, it’s to focus on a group because i need to do something with multiple things in the group and i don’t want to have to scroll through the tree to find the group that’s 5 levels down. Just makes it easier visually. Also once i do change something on a device in that group, it changes the focus to the one device. Hitting the back button in my browser brings me right back to the group i was looking at before it navigated away without me wanting it to.
The other time i use the focus feature is to focus on a single device because i’m showing someone from the NOC how to navigate and understand the data and i don’t want them distracted by the other stuff they’d see in my resource tree that they’d never see in theirs.
One time focusing on a datasource would be handy is after i’ve created the datasource, but before no instances are discovered. In UIv3, I have to navigate to an instance under an adjacent datasource and pound refresh on that page so that the resource tree is redrawn every time. This means i can see the instances when they show up instead having to refresh and drill down each time i refresh just to see that the instances aren’t there yet.
LM User
·3 years agoThe module toolbox is also pretty bad when waiting for a search result. 4-5 seconds for anything, and everything seems to get reloaded /refreshed whenever you do anything. No caching appears to happen at all.
LM User
·3 years agoI haven’t used any of the beta pages in quite a while, so my experience with slowness is mostly around the alerts page and the logs page.
The most common (and longest) latency has to do with switching between UIv3 and Uiv4. Like a whole new set of libraries has to be loaded and that has to happen before anything even gets displayed. This lag is not noticeable when going from a UIv4 page to a UIv4 page, so maybe it will resolve itself when there’s no more switching.
It seems like there’s no pre-fetching happening at all.
LM Logs is just slow because there appears to be a lot of waiting for data. The page loads quickly enough (if you came from a v4 page), but last hour of logs can take 4-5 seconds to load the header graph and then the actual logs themselves. Often I need to look at much larger timeframes (24 hours or a week), with specific filters, which takes 15-35 seconds to load. Adding parsing functions to that doesn’t seem to add any additional latency. It’s just waiting for the log data to actually get to my browser.
Sarah Luna
·3 years agoThanks for the feedback y’all!
A couple of questions -
1. do you use the focus functionality a lot?
2. if so, when do you use the focus as opposed to just having an item expanded in the tree?
Also for instances of slowness, can you describe what workflows? Like is it when interacting with the tree or with the graphs tab? We want to make sure that you have a comparable experience in the new UI so we want to resolve those issues if you’re still facing them.
David Bond
·3 years ago@Stuart Weenig - it feels like the YUI (V1 UI) to V2 UI all over again!
Here’s how it will go down:
LM User
·3 years agoWhatever demigod they’ve been taking their UI advice from clearly has never used our product. There are some things in that area that are changing though. I just wish the UIv4 focus was feature parity first, additional capabilities later. So much new capability is being stuffed into UIv4 before it’s even rolled out.
Matt Whitney
OP3 years agoAgreed, the placement of the focus icon is also much better in UIv3.
Have to agree with you. However, I doubt anything will be done. They will weigh “why don’t you just not click it” against “what code do we have to write to exclude it from having a focus option”. Guess which will win.
Hopefully that doesn’t end up being the case. So many things are different/strange about UIv4 where I can’t really use it for work unless I want to do things 10x slower.
LM User
·3 years agoDon’t get me started on the “you don’t need the magnifying glass if you throw your no-double-clicking rule out the window” argument.
Jared Meidal
·3 years agoI have already clicked this on instances inadvertently many times in the new UI. I think the slower response time contributes to this, and the proximity of the + icon to the name of the instance. The eyeball icon placed above the resources in the old UI was a separation which seemed to help prevent this.
LM User
·3 years agoHave to agree with you. However, I doubt anything will be done. They will weigh “why don’t you just not click it” against “what code do we have to write to exclude it from having a focus option”. Guess which will win.
Matt Whitney
OP3 years agoI also don’t like how when you focus on anything, the “Recently Deleted” and “Unmonitored Devices” tabs are visible. In UIv3 those tabs were only visible when the root folder was selected, and I think that was cleaner.
Matt Whitney
OP3 years agoIt doesn’t look like focusing on an instance gives you a different URL. Either way if you select an instance it gives you a URL that navigates back to the instance. Does the same in UIv3 as well, although the URL looks different and the UIv4 instance URL is easier to parse.
LM User
·3 years agoDoes focusing on the instance give you a unique link that will get you back to that same instance? Wonder if they’re trying to make it easier to share URLs that point to specific things.