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

Fix logging #276

Open
3 of 11 tasks
Ghemechis opened this issue Jul 13, 2024 · 0 comments
Open
3 of 11 tasks

Fix logging #276

Ghemechis opened this issue Jul 13, 2024 · 0 comments
Assignees
Labels
sprint-12 Items assigned to sprint 12

Comments

@Ghemechis
Copy link

Ghemechis commented Jul 13, 2024

Item type: bug fix

Description: To improve log output readability and error traceability, this feature allows users to adjust the level of log outputs when running commands, such as scrapers. The entrepreneur user can switch between different log levels (ERROR, DEBUG, INFO) to view high-level activities or detailed error information for troubleshooting purposes.

please check the example provided by the IP below.
- how to change the level of detail in the log output, e.g. ERROR, DEBUG, INFO
- for example, the high level output could be
- scraping youtube channel-x episode-y
- scraping youtube channel-x episode-z
- ERROR: youtube channel-x episode-a
and provide the possibility to increae the output level to get more details about what goes wrong when running it
again for episode-a

User story

As an entrepreneur developer,
I want to have the ability to select the level of log output,
so that I can see high-level activities when running a command and also dive into detailed logs to troubleshoot errors.

Acceptance Criteria

  • the entrepreneur user can change the log output level (ERROR, DEBUG, INFO) for commands such as scrapers.
  • High-level log output should include basic activity information (e.g., "scraping YouTube channel-x episode-y").
  • When an error occurs (e.g., "ERROR: YouTube channel-x episode-a"), users can increase the log output level to view detailed logs for that specific command.
  • Detailed logs should provide specific information on errors to aid in troubleshooting.
  • Documentation is updated to include instructions on how to change log levels and interpret the logs.

Definition of Done

  • The feature has been fully implemented.
  • The feature has been manually tested and works as expected without critical bugs.
  • The feature code is documented with clear explanations of its functionality and usage.
  • The feature code has been reviewed and approved by at least one team member.
  • The feature branches have been merged into the main branch and closed.
  • The feature utility, function and usage have been documented in the respective project wiki on github.
@Ghemechis Ghemechis converted this from a draft issue Jul 13, 2024
@Ghemechis Ghemechis added the sprint-12 Items assigned to sprint 12 label Jul 13, 2024
@EnescuDavid EnescuDavid self-assigned this Jul 14, 2024
lukas-varga added a commit that referenced this issue Jul 14, 2024
Small fix for logging in youtube scrapers
@EnescuDavid EnescuDavid moved this from Product Backlog to Awaiting Review in amos2024ss06-feature-board Jul 15, 2024
@tubamos tubamos moved this from Awaiting Review to Item Archive in amos2024ss06-feature-board Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint-12 Items assigned to sprint 12
Projects
Status: Item Archive
Development

No branches or pull requests

3 participants