Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically "follow" logs #139

Open
NoTuxNoBux opened this issue Apr 5, 2022 · 2 comments
Open

Automatically "follow" logs #139

NoTuxNoBux opened this issue Apr 5, 2022 · 2 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@NoTuxNoBux
Copy link

The recently added "Logs" tab is great! Would it be possible to make it automatically refresh or "follow" the logs? Alternatively, a refresh button could also work. I can use podman-compose logs -f <container> to follow the logs, but Pods doesn't update alongside with new output; even restarting Pods doesn't make the new logs show up, it seems.

A possible problem to take into account is that these logs can be huge. I have a web application that logs database queries during a synchronization operation and a single synchronization commonly logs about 30 MB of logs. Podman probably handles most of the actual logging, but I thought it might be important whilst designing the UX/UI for it to avoid slow scrolling performance or long lines or something.

@marhkb
Copy link
Owner

marhkb commented Apr 5, 2022

Thanks for your feedback. Hmm, I designed it to follow the logs. It's weird that it's not working for you.

.follow(true)

30 MB of logs

Oh yeah, good point. We should probably work with tail, since and until. In this way, we could fetch logs when scrolling up.
https://docs.podman.io/en/latest/_static/api.html?version=v3.4#operation/ContainerLogsLibpod

@marhkb marhkb added the enhancement New feature or request label Apr 5, 2022
@NoTuxNoBux
Copy link
Author

Thanks for your feedback. Hmm, I designed it to follow the logs. It's weird that it's not working for you.

Hmm, it seems this container is a special snowflake somehow. I have another image just using the Adminer image from Dockerhub that works fine, but this application is a NestJS application based on node:17-alpine. All I see is this:

> [email protected] start:dev
> nest start --watch "the-application"


 Info  Webpack is building your sources...

Normally if you make a change then, it adds more content, which does work with podman-compose logs -f, but it doesn't show up in Pods for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants