OpenVoiceOS / OpenVoiceOS/ovos-utils

ovos-logs feature request

Open
#228 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
6
Forks
13
Avg merge
1d 8m
Merged PRs (30d)
8

Description

Thanks for OVOS-logs @emphasize! It's much easier than having to navigate to the logs etc this way.
Many times I would like to see just the last / recents lines to get a sense what an error is. Now I get a full history etc. I understand I can narrow it down, but maybe a simple (extra) function would make it faster.

Would it be possible to add a function like "show only last x lines", something like:
ovos-logs show -l skills --recent x (show latest x lines of the skills log)
or maybe the recent of all logs?
ovos-logs show -l all --recent x
Edit: wait, I see now what the ovos-logs reduced option does. I can narrow it down to a lot less lines. I've tried reducing it to 10 lines for instance, but it shows more (but that's not a problem).

I like the lay-out of ovos-logs slice! I see you can filter on date/time, but would it be an option to just at the current day for instance via a simple paramater (something like: ovos-logs slice --current [ hour | day] or something without having to specify the exact date and/or time?

And maybe a strech feature request, but would it be possible to script a combined log of 'only the relevant logs after the last utterance'? So: to show only logs that are relevant for the last utterance spoken/typed by the user? Many times I would like to know info from different logs, like what is transcribed, what intent was triggered, what was the exact audio output etc. If it could be shown in the right order (time-wise) and in the style of slice it would be very nice! But maybe wishful thinking ;)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing ovos-logs show and slice command entry points, especially how reduced output and date/time filters are currently handled. The request contains several separate ideas—recent lines, current-day filtering, and combining logs after an utterance—so the scope and acceptance criteria need to be agreed before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.