Skip to main content

Since the new resources status pages, it became very difficult and no user-friendly to filter the results.

Before, with the deprecated pages, it had different search fields "hosts”, “services”, “ouptut”, ..." and different selection fields. This was simple for any user, it was fast and efficient...

 

… But today with this new single search field all research becomes too complicated.

 

I have been an experienced Centreon user for 10 years, we have a 1000 hosts business version, but I am saddened to see that Centreon has become no user-firendly. In fact, all my users tell me that they can no longer find anything with this new single search bar.

 

  • Today my users must to write long and unclear filters themselves, whereas they didn't have to worry about that before. They often don't know how to do it, they don't know if something is missing, they don't understand, it's too complicated for them and for an experienced users.
  • Today my users must know the directives "s.description:, h.name:, information:, ...." whereas they did not have to worry about this before. Which is mission impossible for a normal user who has neither work nor time to waste, or not the desire to know all the subtleties of Centreon .
  • Today my users must know the regex syntax. for example when they simply look for a network interface, otherwise they get error "Bad regex format 'HundredGigE0/1/1/0'". it is necessary to explain to them they must escape the regex with characters \. It's too complicated for a standard users and so annoying for an experienced users. Before they didn't have to worry about that.
  • Since upgrade 22.04 to 23.04 it is no longer possible to search for results in the "long_output" tables even with the "information:" directive. Obviously this search function, although essential, was deliberately removed,  probably to prevent possible performance problems of the few customers who have very gigantic databases. Although it worked correctly for most centreon customers. I had no performance problem when we used this search on our database with more of 500 GB for 25k services. 

 

proposals :

  1. Return of multiple search fields by default as in deprecated pages for simple use.
    1. And add an unfold button to access the expert search field corresponding to the new the single field.
  2. Have a possibility to activate or deactivate the search in the "long_output" fields. By default activate and have the possibility of deactivating it for who want this, like large clients with performance problems.

 

Thank a lot

 

HI @jstager we are developing a new UX to filter resources in “Resources Status” menu.

Do you want a presentation of this one?

Regards,

Hi @Laurent , I am interested in your proposal.

presentation in French?

Thank a lot

New→Discussion ongoing
Discussion ongoing→Planned

I’ll add: Fix the reorder custom filters issue and the “impossible to select again the last selected custom filter”, so one can go back to the corresponding selection after an edition in the search bar. And no, sorry, it doesn’t break any user workflow a Centreon employee answered me here. Simply because as it is, clicking on the selected filter just does nothing.

And please: If you plan to redesign the configuration part of the UI (or any other part of it), introduce it the right way: mark the new pages as beta and keep the current ones by default. Do not deprecate some pages while making unfinished pages the default (it was not just “unpolished” at this level…). Doing such for the monitoring part of the UI was nothing less than a plain third finger waved at your oldest users and customers. Even if not intended as is, it surely was.

In 23.04, is it still possible to DoS the program for any user who may access the Administration > Logs page by simply selecting the last entry in the “logs per page” selector? Will it still be the case in 23.10? In 24.04? I must not be the only user who would rather see that kind of issue addressed before any eye-candy shit or arguable ergonomic enhancements…

I’ve been told 23.10 has fixed some of the performance issues introduced in 22.04 (or some version before, but compared to a 20.04, a 22.04 or a 22.10 is just hugely slower at every level (using the GUI or CLAPI)). I hope it’s true, and I hope there won’t be new bad surprise like this in 24.04 and next releases.

@Stéphane sorry but your comments here are very inappropriate.

1- You might disagree with how we prioritize our product backlog and we do value your feedback but the tone/terms you use are extremely agressive for a product team that does its best every day to satisfy the broadest group of users

2- You are commenting on an idea that has nothing to do with your list of complaints (which by the way you have expressed in other threads already...)

3- Your comments are too vague for anyone uninformed to understand (thankfully I’ve been following your threads so I do understand part of it)

I am only going to answer your 2nd point here. With 23.10 we are introducing Centreon Dashboards in beta. We are not removing Custom Views as we know Dashboards are still far from having all of the features you are used to. However these beta tests allow us to get feedback early from our users, instead of pretending we know what they need, and going in a long development tunnel just to realize it does not hit the mark.

@jstager thanks for the detailed idea. With 23.10 we are introducing filters which should cover your first ask. With regards to the 2nd (searching long_output) we are looking for ways to re-introduce it.

I’ll add: Fix the reorder custom filters issue and the “impossible to select again the last selected custom filter”, so one can go back to the corresponding selection after an edition in the search bar. And no, sorry, it doesn’t break any user workflow a Centreon employee answered me here. Simply because as it is, clicking on the selected filter just does nothing.

And please: If you plan to redesign the configuration part of the UI (or any other part of it), introduce it the right way: mark the new pages as beta and keep the current ones by default. Do not deprecate some pages while making unfinished pages the default (it was not just “unpolished” at this level…). Doing such for the monitoring part of the UI was nothing less than a plain third finger waved at your oldest users and customers. Even if not intended as is, it surely was.

In 23.04, is it still possible to DoS the program for any user who may access the Administration > Logs page by simply selecting the last entry in the “logs per page” selector? Will it still be the case in 23.10? In 24.04? I must not be the only user who would rather see that kind of issue addressed before any eye-candy shit or arguable ergonomic enhancements…

I’ve been told 23.10 has fixed some of the performance issues introduced in 22.04 (or some version before, but compared to a 20.04, a 22.04 or a 22.10 is just hugely slower at every level (using the GUI or CLAPI)). I hope it’s true, and I hope there won’t be new bad surprise like this in 24.04 and next releases.

 

Hi @Stéphane,

I'm sorry to hear that your experience is not meeting your expectations. However, it's important to note that there is an appropriate way to express this, and this is not the first time I've mentioned it to you. You have access to our support, as well as The Watch, and if you wish, you can even send a direct message to any Centreon employee here (CPO, PMs, etc).

I kindly request that you familiarize yourself with the code of conduct on The Watch because if this situation repeats for a third time, your account may be subject to sanctions.

In the meantime, I will connect you with a product manager with whom you can discuss your concerns.

Thank you for your understanding.

Planned→Released

New filters have been released in 23.10. Check the release note.

Hello,

Can you keep the old status page please ?

My coworkers don’t accept this new design at all, old page was perfect.

Please.

Please note that the issue is not all this “ressources status” page. There is part of it that are very nice and handy.

When you click on something, the pop up pane on right side is excellent.

The issue is how this page allow you to search : way too complex compared to the old good search fields with drop down select box.

 

Just add an option to choose between “request using query langage” and “old school menu”, this one : 

 

Everyone will be happy.

Thanks

Terms & ConditionsCookie settings