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

Logger: lkrg-logctl: Add more features #317

Open
solardiz opened this issue Feb 25, 2024 · 0 comments
Open

Logger: lkrg-logctl: Add more features #317

solardiz opened this issue Feb 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@solardiz
Copy link
Contributor

Nov 10 to Nov 24, 2022:

Add a tool that would read a log and present it differently, including possibly/optionally (as requested):

  1. With human-friendly timestamps (e.g., an ISO format). Most importantly, with inferred timestamps of when the events occurred. These can be inferred as: send attempt real timestamp - (send attempt uptime - kmsg uptime).
  2. With control characters escaped or replaced.
  3. Starting from a previously-recorded "cursor", updating it (which it'd maintain in per-log cursor files).
  4. Wait for data (akin to tail -f and journalctl -f).
  5. With filtering by message type (LKRG only vs. LKRG+kernel only vs. all including userspace-injected).
  6. With filtering by syslog severity.

Maybe the tool should also be able to read/follow multiple logs at once and combine them into one output stream, or/and we need this functionality in the logger. Either way, the final messages would need to include end system IDs (perhaps as first field).

Item 1 above is now implemented in a basic form - we might still want to add command-line options to choose which timestamps are reported. Items 2 to 6 are unimplemented.

@solardiz solardiz added the enhancement New feature or request label Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant