Data explorer

The explorer is not another register. It is the tool that asks one question of all of them — which is why it does not sit inside any one.

What you can ask about

Hosts · systems · databases · equipment · vulnerabilities · events · tasks · people, and beside them the infrastructure families: virtualization, storage, cloud, containers and backup. Entities are grouped into categories — infrastructure, business, data, security, operations and people.

The screen, in the order the work happens

1. The command bar — free-text search and the entity picker, with quick filters, the view picker and recent queries beside them. Every panel opens from its own button.
2. The query canvas — a condition tree with "and" and "or", and + condition at the end of each group.
3. The answer — a table or a chart, full width.

The canvas collapses to a one-line summary once the query is built, because what you look at after building a query is the answer.

Fields

The field picker groups fields by subject — identity, classification, hardware, state, updates and others — instead of presenting one long list. Custom fields are available here exactly as they are in any table.

What can be said about a field follows from its type. A free-text field gets no quick filter at all: a list of several hundred serial numbers is the column again, not a filter.

Relations — one hop

From	You can ask about
Host	Its system · the vulnerabilities found on it · its update events
System	The system's hosts
Vulnerability	The affected hosts

One hop only. Two hops turn a filter language into a join planner and stop it being teachable.

The expression

Every query has a text form, and it can be edited:

<entity>: <conditions> | by <field> | sort <field> asc | limit N

The expression is written in field keys rather than display labels, so rewording a label cannot break a stored query. Values are data, quoted, and may be Hebrew. A condition the visual builder cannot draw is kept as written and shown as a locked chip — nothing is dropped in either direction.

Beside the expression there is an In words view: the same condition tree, in prose.

Two windows, deliberately

The table fetches a window of rows and pages inside it. The chart fetches every matching row, projected to the columns it groups on — a chart drawn over the table's first page is a chart that lies silently. The "found X of Y" counter is exact in both cases, and when the window is shorter than the total the screen says so.

What the explorer does not do

• It is not saved as a saved view. A saved view is a map of filters and sorts, and it cannot express an "or" tree, a negation or a relation. Sharing is the link: Copy link carries the whole query — conditions, grouping, metric and chart type — and the browser's Back button restores it exactly.
• Recent queries are local to this browser. They are not shared and are not cleared on their own.
• Open in the table loses part of the query, and says so. The link to the entity's own page carries only top-level equality conditions; groups, negations and relations cannot be expressed in a table.

From the explorer to a board

Add to dashboard turns the result into a widget. The widget carries the expression itself and runs it on the server on every board load — see Widgets and queries.