Zui is a powerful desktop application for exploring and working with data. The official front-end to the Zed lake.
Visit the Brim Data download page page to find the package for your platform.
files
events, the is_orig
value is now used to determine the tx_host
and rx_host
values in the Correlation view (#3004)/compile
endpoint of the Zed service rather than the JS Zed query parser (#2972, #3034)yield typeof({})
produced a stack trace (#2996)Visit the Brim Data download page page to find the package for your platform.
zed serve
process is tied to the parent Zui process (#2956, #2957)files
events (#2981)Visit the Brim Data download page page to find the package for your platform.
Visit the Brim Data download page page to find the package for your platform.
It's now possible to preview and shape your data as you load it into a Zed lake with Zui. For details, check out the video at the Zui docs site.
null
values were incorrectly rendered (#2875, #2876)Visit the Brim Data download page page to find the package for your platform.
Visit the Brim Data download page page to find the package for your platform.
The big change in this release is that Zui now uses the Monaco editor. This gives Zui a monospace font and basic syntax highlighting for easier editing of your Zed programs!
community_id
field was incorrectly being treated as a prerequisite to activating the Packets button (#2830)-version
option on the bundled zed
and brimcap
binaries was producing incorrect output (#2841)Visit the Brim Data download page page to find the package for your platform.
This change is relevant for users that have have additional Zed lake connections besides just the one to the default lake that starts behind Zui. You'll notice that now each time you switch connections Zui updates the tabs so only the ones for the current-selected lake are shown.
If you're familiar with Zui's history, you may know that its stacked bar chart was based on Zeek-style data such that it was hard-coded to expect a time field called ts
that would provide data for its X-axis and a field called _path
that was subject to count() by
to make the colored segments in the bars. With this release the chart is now generalized so that:
ts
, it will start out using that)count() by typeof(this)
now populates the stacked bars by default, but you can change this to use any other fieldts
and _path
are used by default as beforeFor an example of the new behavior in action, this video uses the prs.zng
GitHub test data from the zq
tutorial. This has a time field called created_at
so we use it as our pool key, then after observing the bars with the default count() by typeof(this)
we change the Color Field setting to login.user
so we can see stacked bars based on who opened Pull Requests. Try it yourself!
_path
& ts
fields) (#2785, #2794, #2805)Visit the Brim Data download page page to find the package for your platform.
Visit the Brim Data download page page to find the package for your platform.