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

Adding heroku logs --follow/-f as an alias to heroku logs --tail/-f #1912

Open
chancancode opened this issue Jan 5, 2022 · 3 comments
Open

Comments

@chancancode
Copy link

Do you want to request a feature or report a bug?

Feature!

What is the current behavior?

  • heroku logs --tail/-t is used to stream the latest logs, while heroku logs --follow/-f is not recognized

What is the expected behavior?

  • heroku logs --follow/-f can be used to stream the latest logs

Background

Sorry for being so pedantic 🥲 This keeps tripping me up so I thought I would open an issue, seems more productive than complaining on Twitter!

I think calling this mode --tail is a bit of a misnomer. While it is commonly accepted to call this operation "tailing the logs", the tail command itself only shows the last N lines of a file and has little to do with this "live streaming of logs". It's really the --follow flag in tail that enables this mode, so it seems more appropriate to call it the "follow mode" instead of the "tail mode".

Because the --follow/-f flag is what you normally passes to the tail command when trying to do this, I almost always end up typing heroku logs -f which doesn't work. Since the flag isn't otherwise taken, would it be possible to add that as an additional alias?

@michael-gratton
Copy link

As a long time unix and linux user this trips me up basically 100% of the time.

@michael-gratton
Copy link

FWIW, systemd also uses -f/--follow for journalctl, which is the primary way people interact with logs on modern Linux computers from the command line.

@zwhitfield3
Copy link
Contributor

zwhitfield3 commented May 24, 2024

Thank you both for bringing this to our attention! We are looking into it. Thank you for your continued support! Internal Ticket W-15841241

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants