What's New in LogBlazer

LogBlazer started with a simple idea: logging should be straightforward. No sprawling configs, no week-long onboarding — just send your logs and get to work. That core hasn't changed, but the tool has grown. Here's a look at what's new.

Dashboards: See Your Logs, Don't Just Read Them

Logs are data. And data is easier to reason about when you can see it. LogBlazer now includes built-in dashboards that give you a visual overview of your log activity — volume trends, error spikes, breakdowns by source or level — without leaving the app or wiring up a separate visualization tool.

The goal here isn't to replace dedicated monitoring platforms. It's to give you a quick, useful picture of what's happening across your projects right now. If you're triaging an issue at 2 AM, a dashboard that shows error frequency by source is worth more than scrolling through raw entries.

Dashboards update as your logs come in, so the view stays current. No extra setup — if you're already sending logs, the data is there.

Source Management and Filtering

Most applications don't run as a single process. You've got web servers, background workers, cron jobs, maybe a queue consumer or two. LogBlazer has always supported source categorization, but we've improved how you manage and filter by source.

You can now organize sources more cleanly within each project, making it easier to isolate logs from a specific part of your stack. Combined with log level filtering — quickly narrowing down to just errors, warnings, or whatever you need — it's faster to find the signal in the noise.

Full-text search works across all of this. Search by keyword, filter by level, scope to a source — and you're looking at exactly the logs that matter. No query language to learn. Just type what you're looking for.

Team Collaboration

Logging isn't a solo activity. When something breaks, multiple people need to look at the same data. LogBlazer now supports inviting team members to shared projects, so everyone on your team can access the same logs, dashboards, and filters.

This matters more than it might seem. Developers spend a surprising amount of time context-switching between tools — some estimates put it at 50+ switches per day, each one costing a few minutes of focus. Having your logs accessible to the whole team in one place, without forwarding screenshots or copy-pasting stack traces, removes one more reason to break flow.

Permissions are straightforward. Add a teammate, they see the project. No role hierarchies or access matrices to configure.

What's Ahead

We're continuing to build based on what developers actually use and ask for. There's more coming — better alerting, richer integrations, and some ideas we're not quite ready to talk about yet. If you're already using LogBlazer, you'll see these roll out over time. If you haven't tried it yet, it takes about a minute to get started.