I personally had a pain point with... logs, i never understood the complicated UIs, all the charts, all the metrics, everything the premium tools throw at me and you. I still had to install an SDK mostly. I still needed to learn some arcane query syntax just to filter logs. Debugging should be easy, we already break our heads with writing code, making it understandable by others, dealing with deadlines. The last thing I want is to read docs when something breaks on my production, or worse, on a client's production.

That's why I built Loguro.

1. My debugging partner should understand English, almost as if I was talking to myself. - level:error|critical message:"database timeout" @today

2. I don't like noise, i might have 1k logs from an error, this means a lot of rows in a table i need to scroll - Loguro transforms this patterns into groups, so i see 20x and can expand them directly.

3. I need to see how it happened. There are tools that replay UI interactions, but what about the backend? Server started hiccuping, then something else happened, then dead. Normally I end up hunting traces and timestamps across 10 tabs. - from:"1 hour ago" to:"5 minutes ago" --replay — renders a widget, I watch my logs come back in sequence like a time machine. No tabs, no traces, just the story.

4. I have the error. I know how it happened. Now I need to create a task. Normally I open Jira or Linear, navigate to the right project, create the issue, switch tab, copy the log message, paste it as the title, go back for context, go back again, submit, copy the URL, open Slack, post to the team channel... you see where this is going. - --task:jira --send:slack#team — in Loguro I add the relevant logs to context, hit the command or type it in the same query bar, press cmd+enter. That's it. Task created, Slack notified with the link and details. I can go to sleep. ** And that log? It lives forever now, even if the retention is 24 hours, a log that becomes a task never gets deleted and i can see it back with --memory.

5. Months have passed. I consider myself a decent developer, but that goddamn error is back — and it brought friends. Normally I go hunting. Search through thousands of issues, hope it sounds familiar, spend minutes or hours finding the first occurrence. Then switch back to the logging tool, compare, check if it's the same pattern, check if the old fix still applies... - In Loguro, when a log was tasked, it remembers. New logs matching the same pattern are automatically marked as "seen before." I click it, see the original task, the comments, the context, the smart dude who "fixed" it last time — and decide what to do next. No hunting, no tab switching, no déjà vu.

One more thing - as a good dev, I sometimes send logs with stringified JSON inside the message field. Perfectly normal, yea? Loguro handles it with --separate::message, pulls that JSON out of the message and puts it where it belongs — in the context. Clean log, no noise.

Everything shall and it is managed from a command palette, from my account, billing, usage, to api keys, notification channels and integrations. Loguro is packed with a handful of features which i hope, it makes it stand out and provide value on the already saturated market.

I would love some feedback on it, even on the landing page and docs. On the footer i have a link with the discord server, i am there and anywhere in case of something. Also once inside the app use --feedback to provide feedback directly from anywhere.