Skip to main content

Remove useless logs

Feature RequestsLogs

We don’t want to see log messages like
```

[Ground Control] [2025-10-08T21:55:57.688306146Z] Workspace is GO [Ground Control] [2025-10-08T21:55:57.713268817Z] We're ready 01K72V1D00JASVRB85KQXY579H [Ground Control] [2025-10-08T21:55:57.713276695Z] Over to you 01K72V1D00JASVRB85KQXY579H, we'll see you on the other side [01K72V1D00JASVRB85KQXY579H] [2025-10-08T21:56:12.370730422Z] Mic check 1 2, is this thing on? [01K72V1D00JASVRB85KQXY579H] [2025-10-08T21:56:12.370790531Z] This is 01K72V1D00JASVRB85KQXY579H to Ground Control, I'm on
```
since they don’t have any discernible meaning to us. It would be great to prioritze real log messages.

Status: ⌛ Waiting for User6 comments

Log in to comment and vote

Comments6

  • Natalia Gazda

    Team•

    Jul 7

    @George Tzoganakis

    Thanks for the examples. One question before we dig in: have you tried Smart Sanitization on these stacks?

  • Beige Kangaroo

    •

    Nov 18, 2025

    how do I downvote this? I love these logs

    • Black Breeze

      •

      Nov 18, 2025

      I don’t think there’s a formal way of downvoting in Featurebase but I will consider your comment an informal downvote :)

  • Purple Teacup

    •

    Oct 9, 2025

    +1
    These logs are valuable but full of bloat, for example this could easily just be the following logs:

    Initializing Workspace 01K72V1D00JASVRB85KQXY579H
    Workspace ready 01K72V1D00JASVRB85KQXY579H

    also I don’t think anyone was pissed off, just giving feedback on the product.

    • Black Breeze

      •

      Oct 9, 2025

      The logs are a bit of an internal joke, a reference to the late David Bowie.

      Feedback well received. There’s a quite a few things we need to improve with logs. Off top of my head - timestamps, log levels, search, scrolling or deep-linking to individual lines. I think the original problem reported here is actually best addressed with log levels.

      Every now and then we need those logs. We like David Bowie, too. So these logs will stay. But we can make them disappear by default by emitting them with DEBUG level.

  • Black Breeze

    •

    Oct 9, 2025

    They may often be useless to you but they’re really invaluable for troubleshooting worker connectivity issues. The overall ratio of these messages to meaningful stuff is generally low, so it’s honestly the 1st time we’re hearing this as a complaint.

    But your point is taken, we need a better story for logs anyway, and I’ll add this to list of things to address. Perhaps we can manipulate log levels in a way that the logs are still there for when you need them, but don’t clutter the default view.