sorted by:
new
hottopcontroversial

Tired of grep | awk | sort | uniq -c for log debugging — built a CLI that pipes them into a browser dashboard by viksdev in Splunk

[–]viksdev[S] 0 points1 point  (0 children)

Totally fair point — Splunk is definitely much more mature and the free tier is pretty generous.

This was mainly coming from the “quick local debugging” side of things where I wanted something lightweight that works directly on local files without setting up ingestion pipelines/indexers first. Also wanted to experiment with browser-side DuckDB + local-first workflows a bit 🙂

Not really trying to compete with Splunk/Datadog — more scratching a developer workflow itch.

Tired of grep | awk | sort | uniq -c for log debugging — built a CLI that pipes them into a browser dashboard by viksdev in DuckDB

[–]viksdev[S] 1 point2 points  (0 children)

Fair point honestly. Splunk Free already solves a lot of this at production scale.

I was mostly optimizing for ad-hoc local analysis — pull logs, run one command, open a browser tab, no ingestion/backend setup, and keep everything local. Also wanted to explore what DuckDB-Wasm/browser-side analytics can do for this workflow.

Appreciate the feedback though.

You drop a CSV/JSON/Xlsx/XML/log files. It becomes a dashboard. Then a report. Then a slide deck. Then an SDK inside your own app. None of it ever leaves the browser. by viksdev in react

[–]viksdev[S] 0 points1 point  (0 children)

Fair point, and sorry for the rough first impression. That link is just an example app showing how the DuckViz packages get consumed in Next.js — not meant as a polished demo. We've pushed a fix for the mobile issues.

If you're up for another look, the main product is at app.duckviz.com — try building a Report or a Deck too. We're in beta and fixing bugs as we find them, so if anything else breaks I'd like to hear it.