Welcome to the final post of our Dashboard Improvements Series! Over the last three week we've introduced visibility upgrades in Builds, redesigned Deployments, and rolled out Environment Variables Tempaltes. This week, we’re turning our attention to a part of the dashboard you rely on when things break: Logs.

Logs have always been there to help. But as your app grows and the data piles up, finding the exact log entry you need hasn’t always been fast or easy. So we made it better.

The “Log Archaeology” Problem

It’s 3pm. A customer says their payment failed. You open the logs and start scrolling. And scrolling. And scrolling.

You try Cmd+F. You get 147 hits for “payment.” You start clicking through, hoping one of them is the one you need. By the time you find the relevant log line, if you even do, you’ve lost more than just 5 minutes and a chunk of your focus.

And then sharing it? You screenshot. Or copy-paste. Or try to describe what you saw in words.

This shouldn’t be the workflow. So we rebuilt it.

What We Built

We intordoduced updates to the Logs that will increase debuging speed and improve your workflow.

Instant Search with Highlighting

Type anything into the search bar and get results instantly. It checks every log entry, including messages, stack traces, and metadata. Matches are highlighted in yellow so they pop off the screen. The time to find what you need now is significantly reduced.

One-Click Copy

Every log line now has a copy button. Just hover, click, and the full entry is copied with perfect formatting.

Full context.Ready to paste it into Slack. Support tickets. Bug reports or documentation. Done. No screenshots, no manual formatting.Just click and paste

Log Export

Need to share logs with Stripe, AWS, or anyone external? Just click “Export Logs” and get a clean .txt file of your entire present on the screen logs.

File names are auto-generated (e.g., logs_error_2024-10-21.txt) so it’s always clear what you’re sending.

Perfect for:

Sharing with external support teams
Archiving for compliance backups
Offline debugging
Creating reports

Relative + Absolute Timestamps

Logs now show both absolute and relative time:

Relative time is easier to parse: "Oh, this error happened 5 days ago"
Absolute time is precise for sharing: "The error occurred at exactly 17:29:20 +02:00 on Oct 29, 2025."

You get precision for sharing, and quick insight for triaging automatically. Best of both worlds.

Color-Coded Log Badges

Visual cues help you scan faster:

🟩INFO - green badge

🟨WARN - yellow badge

🟥ERROR - red badge

When you’re scanning a long list, these badges guide your eyes right to what matters.

Real-World Example

In a secenario where a user reports: “Payment failed around 3pm.”, here is how your workflow goes before and after this release:

That’s not just a small improvement, that’s the kind of fix that makes your day better.

The Time Math

Let's say you debug 3 production issues per week, and this saves 5 minutes per issue.

Per week: 15 minutes saved
Per month: 1 hour saved
Per year: 12 hours saved

What would your team build with an extra 12 hours per year? New features? Better testing? Taking a real team lunch break every couple of months? We vote for all of the above.

Photo by Scott Graham on Unsplash

The Support Ticket Win

One customer told us: "We integrate with a bunch of third-party APIs. When something breaks, they always ask for logs. I used to take screenshots, crop them, paste them in tickets... it was a nightmare."

After this release's changes: "Now I search for the error, click copy, paste it in the ticket. Done. Our support response time improved because I can give them what they need in seconds instead of minutes."

Photo by Guillaume de Germain on Unsplash

That's the real value: You solve problems faster, which means your users get back to work faster, which means your business runs smoother.

Try It Now

This is already live for all SashiDo users:

👉 👉 Log in to SashiDo Dashboard → Go to any app → Core → Logs → Search Your Logs → Just type and go.

See how much faster things get when your tools work the way you do. Intuitively.

What’s Next?

Each one of the updates we released through this 4-week sprint solves a real problem we heard from you! We’re not stopping here. Want to help shape what comes next? Tell us what’s slowing you down - we’ll listen. And we’ll build.

Email us at support@sashido.io or open a ticket trough your dashbaord to share your feedback.

Because we earn your trust by improving your experience, not through lock-in, but by showing up every day and making things better.

Not using SashiDo yet?

We’re a serverless backend built on Parse Server. No vendor lock-in. No credit card. And a real-human support team that actually responds.

👉 Start your Free trial now

Happy Coding!