Welcome to Keeping up with Kibana! This is a series of posts on new developments in the Kibana project and related learning resources and events.

New Inspector replaces Spy panels

The visualization spy panels have been removed from Kibana and replaced by the new Inspector feature.

The Inspector shows more accurate data, such as all requests that have been made for a visualization. You can trigger the Inspector for visualizations from different places. For example, on dashboards you can find the trigger in the panel menu:

In the visualization editor, you can find the trigger in the top menu:

The most important changes are:

The data displayed is more accurate, showing the actual requests that have been made for the given visualization.

For visualizations that do multiple requests (currently if you enable "Other Bucket" on a terms aggregation), we now show all requests in the Requests view of the Inspector.

The new design is Kibana 7-aligned.

The Inspector can contain different views depending on what element you inspect. Currently, a Data view (tabular data) and Requests view are available for all classical charts. But because the available views depend on the inspected element, don't get confused if, in the future, some charts show views other than charts.

The Inspector is intended for temporary analysis of a visualization. Therefore, we no longer store any of it's open state in the URL.

The Inspector is no longer available in the Discovery tab. The data that was shown there was incorrect, so we removed it for now.

Other news

Design

It's been a busy week for the design team. We cleaned up and improved our fixed positioning service (note the position of the arrows over each hover) that we use to calculate positions of popovers, tooltips, and dropdowns. We also got a Super Select dropdown and new Range component lined up for EUI. Also, EUI is now at 1.0.0 and has a new release script tool.

Management

Platform

We have a backlog of PRs we’re reviewing, four of which encompass the last remaining tasks before we can push the new platform on the server. We had to adjust our plans a bit for rolling out the new platform in the UI to effectively handle legacy global plugin behaviors between the old and new platform.