Project

General

Profile

Actions

User story #8563

closed

Make the quicksearch bar in menu able to also search rule, group, directive, etc

Added by François ARMAND almost 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Suggestion strength:
User visibility:
Effort required:

Description

The current "quick search" bar is very limited, and only allows to search for nodes, by hostname. But of course we also want to search for all the directives using a given parameters, or touching a given path, or all the rules embeding a directive, etc - and of course, when an interesting item is found, we want to jump to its corresponding definition.

Contrary to usual rules, we proposed to build such quicksearch in Rudder 3.1 BUT behind a feature switch guard (disabled by default). The idea is that that feature is a major UX help but it does not touch any sensitive part of servers configuration, and is read-only on everything (contrary to the search used for group, for example) - it's just a new way to query information.

On the feature itself, we would like to keep it simple, what means, among other things, not be able to "and" or "or" things. In fact, the proposed quicksearch would be better view as big filter on Nodes, Groups, Directives, Parameters and Rules, we the whole query phrase is exactly looked for in the objects and only the one matching it are kept. That would also helps keep the response time low, and in such feature, it is much more important to be able to quickly iterate between queries to get what we are looking for than to be able to build the exact query matching the exact subset of elements we need.

For the same reason, only a subset of objects properties will be look for (typically, given the current state of Rudder, allowing to search on node by software would notably complexify the query engine and lower performance).

Queries can be refined by providing a subset of objects or attributes to look into. Attribute names used in REST API responses would be used for that.

For example, to only look for nodes with hostname containing "mysubdomain" you could write:

mysubdomain object:node attribute:hostname

And if you want to only get the rules and groups with "security policy" in their name or description, you could write:

security policy object:group object:rule attribute:displayName attribute:description attribute:longDescription attribute:shortDescription

Or more succintly:

security policy object:group,rule attribute:displayName,description,longDescription,shortDescription

All the object/attributes filters name case insensitive, and we will also configure aliases, so that you could write the previous request (yes, I tend to make object in their plural form):

security policy object:groups,rules attribute:name,description

Screenshot of the prototype is attached.

Some question:

- what are the correct names for filters? "object" feels okayish. Could be "type". "attribute" is quite long. "key" is short, but not very self-descriptive. Or perhaps just have a "filter" or "only" keyword, and the engine find by itself if it's an object or an attribute ?
- I'm pretty sure we want to limit the number of results by type, be have a chance to see the rules even if 5000 nodes matches. In the example, I limited to 3 for the example, but 50 or 100 seems better. What do you think ?
- as explained, I selected some attribute base on technical constraints (the list is below). Are you ok with the list ?
- what is the correct way to let an user discover what is searchable, and how? I'm thinking to two may ideas:

1/ have a query form UI displayed when the focus is on the input field, withe a tree clickable for each object, letting the user check what he wants for each (defaults: everything checked, clicking on an object select/unselect all its attributes). Of course, one would be able to also just write the filter by hand once he learned their name.

2/ just have a documentation openable near the field, with all attributes and their names and aliases.

In all case, it would be better to have completion on object/attribute names.

So, any feedback would be very welcomed!


Files


Subtasks 24 (0 open24 closed)

User story #8669: Remove old node search and feature switch in Rudder 3.3ReleasedVincent MEMBRÉ2016-10-05Actions
User story #9231: Remove migration script for (node properties, quicksearch) feature switch ReleasedBenoît PECCATTE2016-10-05Actions
Bug #10077: (old) Autocomplete jar is still presentReleasedVincent MEMBRÉActions
User story #9093: Document the new quick search barReleasedJonathan CLARKE2016-09-20Actions
User story #9102: Make the new Quicksearch UI beautifulReleasedVincent MEMBRÉ2016-09-22Actions
User story #9111: Adapt quicksearch for 4.0ReleasedFrançois ARMAND2016-09-22Actions
Bug #9117: Quicksearch test broken and attribute inconsistenciesReleasedVincent MEMBRÉ2016-09-25Actions
Bug #9121: Quicksearch is not looking for multiline inputsReleasedVincent MEMBRÉ2016-09-26Actions
Bug #9127: Quicksearch bar is broken in 3.2RejectedVincent MEMBRÉ2016-09-27Actions
Bug #9129: Bad title style for quicksearch activation in admin tabReleasedVincent MEMBRÉ2016-09-27Actions
Bug #9134: The link to the quicksearch doc is wrong in 3.1ReleasedVincent MEMBRÉ2016-09-27Actions
Bug #9136: The link to the quicksearch doc is wrong in 3.2ReleasedVincent MEMBRÉ2016-09-27Actions
Bug #9150: Repair quicksearch in 3.2ReleasedFrançois ARMAND2016-09-27Actions
Bug #9168: Empty page "Rudder -API settings"ReleasedFrançois ARMAND2016-09-28Actions
Bug #9170: Broken style on header bar in 3.2ReleasedVincent MEMBRÉ2016-09-28Actions
Bug #9183: quicksearch returns system rules/directives/groupsReleasedVincent MEMBRÉ2016-09-29Actions
Bug #9186: We must not use proprietary font "segoeui.ttf"ReleasedVincent MEMBRÉ2016-09-29Actions
Bug #9195: Quicksearch does not work on "is enable", directive name, and a lot of othersReleasedVincent MEMBRÉ2016-09-30Actions
Bug #9197: Quicksearch does not redirect to a rule when you are on the rule page. ReleasedVincent MEMBRÉ2016-09-30Actions
Bug #9210: The quicksearch "in" keyword is "enabled" and not "isenabled"ReleasedFrançois ARMAND2016-10-04Actions
Bug #9212: Quisearch does not show any nodesReleasedFrançois ARMAND2016-10-04Actions
Bug #9219: Searching on os type does not workReleasedNicolas CHARLES2016-10-04Actions
Bug #9221: When searching for a node "in:xxx", we see node id in place of node nameReleasedNicolas CHARLES2016-10-04Actions
Bug #9224: Quicksearch with in:parameter_[name,value] leads to error 500 on serverReleasedNicolas CHARLES2016-10-04Actions

Related issues

Has duplicate Rudder - User story #4294: Proposal: search function for rules and directivesRejected2013-12-30Actions
Actions

Also available in: Atom PDF