8000 Can't follow starting from a particular time of day · Issue #24 · knes1/elktail · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Can't follow starting from a particular time of day #24

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.

Sign up for GitHub

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

Jump to bottom
Open
jlee-made opened this issue Apr 20, 2017 · 0 comments
Open

Can't follow starting from a particular time of day #24

jlee-made opened this issue Apr 20, 2017 · 0 comments

Comments

@jlee-made
Copy link

This is documented behaviour but seems to leave an important use case unsupported:

There seems to be no way to follow (tail) logs, skipping over a certain time period, because say you had a million errors from some bug and you can't/don't want to tail through all those:

  • Trigger a lot of logs somehow

  • Stop triggering lots of logs

  • elktail --url elasticsearch.example.com -f '%@timestamp %@message' -- '+@message:"error"'
    -> All the errors (for today's date, I guess?) are printed

  • elktail --url elasticsearch.example.com -a '2017-04-20T11:20:00' -f '%@timestamp %@message' -- '+@message:"error"'
    Expect:
    -> elktail does not print all the errors
    -> elktail tails forever
    Got:
    -> elktail does not print all the errors
    -> elktail exits

So it would be nice if when there's an -a (but no -b), elktail could tail (either always or when an extra flag is given).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jlee-made
0