Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Make heroku logs help clearer for --ps and --source #1694

Open
edmorley opened this issue Aug 19, 2015 · 3 comments
Open

Make heroku logs help clearer for --ps and --source #1694

edmorley opened this issue Aug 19, 2015 · 3 comments

Comments

@edmorley
Copy link
Member

Currently:

[~/src]$ heroku logs --help
Usage: heroku logs

 display recent log output

 -n, --num NUM        # the number of lines to display
 -p, --ps PS          # only display logs from the given process
 -s, --source SOURCE  # only display logs from the given source
 -t, --tail           # continually stream logs
 --force-colors       # Force use of ANSI color characters (even on non-tty outputs)

Example:

 $ heroku logs
 2012-01-01T12:00:00+00:00 heroku[api]: Config add EXAMPLE by email@example.com
 2012-01-01T12:00:01+00:00 heroku[api]: Release v1 created by email@example.com

I can never remember the difference between ps and source, or what the strings are for heroku vs app vs api etc.

I know this is explained on https://devcenter.heroku.com/articles/logging , but it's a pain to have to open it each time, when the CLI help leaves me none the wiser :-)

@jdx
Copy link
Contributor

jdx commented Aug 19, 2015

@craigkerstiens @friism I've always felt this was confusing as well. Any ideas on how we could improve it?

@craigkerstiens
Copy link

Perhaps include an example of each within the help?

@edmorley
Copy link
Member Author

What I also find confusing is that the logs contain things like:
app[web.1]

So in my mind "app" and "web" (or "web.1") must map to one of "source" and "process" respectively.

Except they don't - "app" is "source" but "process" isn't the dyno name - and in fact apart from grepping (which doesn't help when only N lines are returned by default) I can't find a way to filter by dyno type at all.

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

No branches or pull requests

3 participants