Skip to content

Releases: kmdreko/venator

v1.0.3

12 Feb 03:17
Compare
Choose a tag to compare

Improvements:

  • improved performance of table with large numbers of rows
  • improved docs for OpenTelemetry (#14, thanks xmo-odoo)
  • improved UI in trace view by adding a collapse/expand all toggle (#11)

Fixes:

  • fixed issue causing NaN timeframe under certain circumstances
  • fixed table flickering when scrolled and following real-time events (#10)
  • fixed table sometimes not loading enough rows on resize or timeframe changes

v1.0.2

01 Feb 18:06
Compare
Choose a tag to compare

Fixes:

  • fixed issue affecting querying spans by parent attributes (when using OpenTelemetry)
  • fixed issue affecting querying spans by their own attributes if they were updated (when using Tracing)

This will require re-indexing so it may take some time when launching the app with a prior dataset.

v1.0.1

28 Jan 15:54
Compare
Choose a tag to compare

Small improvements and fixes primarily around the spans screen.

Improvements:

  • improved the spans screen performance by falling back to an aggregate count graph (like is shown for events) when there are too many spans
  • improved graph dragging
  • improved support for older versions of tracing

Fixes:

  • fixed regex/wildcard filters on #name
  • fixed table sometimes showing spans outside the current timespan
  • fixed table sometimes not showing all spans in the current timespan
  • fixed table sometimes showing duplicate spans
  • fixed the graph cursor being drawn behind elements
  • fixed the app not exiting when backlogged with incoming data

v1.0.0

15 Jan 00:03
Compare
Choose a tag to compare

The initial stable release of Venator!

Venator is a telemetry tool I've designed specifically for rapid local development. View events and spans in real-time with ease in a fast and responsive UI. It supports OpenTelemetry and the Rust tracing ecosystem.

Venator is written in Rust using Tauri + SolidJS for the UI.

screenshot-demo

I've been working on it for the last six months of nights and weekends and am really happy with how it has turned out. It is finally at a point I can call stable, though I still have plans for more features.

I started developing it because I was dissatisfied with existing solutions. Plenty of cloud-hosted services are great, but for local tools I found many lacking. They either:

  • were clunky or complicated to install (Venator is a single executable)
  • focused on logs or traces but not both (Venator presents both in equal light)
  • had slow or poor UIs (Venator is snappy and clear)
  • did not present data in real-time (Venator is instant)
  • could not find logs based on parent span attributes (Venator supports this by default)

You can start using it today by downloading prebuilt binaries here or install it from source using cargo install venator-app.