NodeVerdict: a browser-based viewer for TracingChannel diagnostic data

Open
#687 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
node.js
Domain
observability

Research direction

Review the linked NodeVerdict repository and its examples/ directory, then try the live demo with the supplied sample data. The issue asks for feedback, roadmap alignment, and possible inclusion in the diagnostics projects list, but it does not define an implementation target or completion criteria.

Written by the indexing model from the issue text.

Description

I've been working on a tool called NodeVerdict that might be of interest to this group.

Repo: https://github.com/SnowLeopard-io/NodeVerdict
Live demo: https://snowleopard-io.github.io/NodeVerdict/

It's a browser-based viewer for diagnostics_channel.TracingChannel events. You upload a JSON export of events (or OTel JSON, or a .ndv binary file), and it renders them as a timeline, waterfall chart, CPU flame graph, heap snapshot analysis, etc. All processing happens locally in the browser.

Image

Why I'm posting here

As more libraries add TracingChannel support (mysql2, ioredis, pg, Express — some merged, some in PR), there's a growing need for tools that can consume and visualize this data. NodeVerdict is an attempt to fill that gap on the "consumer" side.

The tool also happens to exercise the diagnostic APIs in ways that might surface rough edges or missing pieces. I've already run into a few things while building it that I plan to document separately.

What it supports

  • TracingChannel event timeline with channel filtering
  • Waterfall chart for async operation chains
  • CPU profile flame graph (.cpuprofile)
  • Heap snapshot analysis and diff (.heapsnapshot)
  • Live monitoring via WebSocket agent
  • OpenTelemetry JSON import
  • Large file streaming via Web Worker (no blocking)

What I'm looking for

  • Feedback from WG members on whether the direction is useful
  • Awareness of any WG roadmap items that NodeVerdict could align with
  • If there's interest, I'd be happy to contribute the tool to the WG's list of diagnostic projects

The repo has examples/ directory with sample data you can drop in to test.

Happy to answer questions or adapt the tool if it helps inform the WG's work.

Thanks.

Dominant language
No language data
Stars
550
Forks
69
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/diagnostics

All issues in nodejs/diagnostics

Similar issues

More Observability & SRE issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.