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

FR: Allow a user to specify the exact number of lines they wish to have returned from kurtosis service logs #1260

Closed
leeederek opened this issue Sep 7, 2023 · 2 comments
Assignees
Labels
feature request logging for FRs/bugs relating to logging nice to have Nice to have feature

Comments

@leeederek
Copy link
Contributor

Background & motivation

Currently, there is no way to print a specified number of log lines using kurtosis service logs. It's either all (via kurtosis dump, --f or with the fix for #1218) or the first 200 lines by default.

The current workaround is to use the --f flag and wait for all the logs to stream through before parsing/scrolling through the most recent lines or do a kurtosis dump and inspecting the logs in a separate text editor.

Desired behaviour

As a user, I can specify the number of log lines to be printed with the kurtosis service logs similar to the -n flag for docker compose logs command.

Ideally, it should be the n most recent lines. So if n = 100, then I should expect to get the 100 most recent log lines from the point in time that I use the command.

How important is this to you?

Nice to have; this feature would make using Kurtosis more enjoyable.

@github-actions github-actions bot added the nice to have Nice to have feature label Sep 7, 2023
@leeederek
Copy link
Contributor Author

@leeederek leeederek added the logging for FRs/bugs relating to logging label Sep 8, 2023
@leeederek
Copy link
Contributor Author

Closed by #1341

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request logging for FRs/bugs relating to logging nice to have Nice to have feature
Projects
None yet
Development

No branches or pull requests

2 participants