You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see logs emitted by a job in a pane in the UI alongside the errors and so on.
I think this could be implemented by storing a slog logger in the context and providing a helper to retrive it. Of course this would only work with applications structured around an explicit non-global logger. Probably you'd also want to limit the max log size to avoid disk space issues?
I'm aware this would be a bunch of work and isn't essential but I think it'd be useful.
The text was updated successfully, but these errors were encountered:
Spoke to @bgentry about this one. I think we're both on board in that this would be a cool feature, but we want to make sure it's flexible enough to cover all kinds of set ups, and that's a little non-trivial. For example, especially for a larger operation, it's not a particularly good idea to store logs directly in the database, so we'd want to have some way for those users to specify some kind of "fetch hook" that'd be able to reach out and pull logs for a job from the right place to show them inline with the UI.
There should probably be a simple version too that provides an option to put logs into metadata or something for easy out-of-the-box use.
I would like to see logs emitted by a job in a pane in the UI alongside the errors and so on.
I think this could be implemented by storing a slog logger in the context and providing a helper to retrive it. Of course this would only work with applications structured around an explicit non-global logger. Probably you'd also want to limit the max log size to avoid disk space issues?
I'm aware this would be a bunch of work and isn't essential but I think it'd be useful.
The text was updated successfully, but these errors were encountered: