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

core: be more selective about what we log #8773

Closed
eckter opened this issue Sep 5, 2024 · 0 comments · Fixed by #10345
Closed

core: be more selective about what we log #8773

eckter opened this issue Sep 5, 2024 · 0 comments · Fixed by #10345
Assignees
Labels
area:core Work on Core Service difficulty:good first issue Good for newcomers kind:refacto-task Task related to Refactorization Epic

Comments

@eckter
Copy link
Contributor

eckter commented Sep 5, 2024

The logs generated by core can be flooded by a few things, which makes log less readable (and increase costs in prod)

The main thing to focus on is warnings when loading an infra. It can generate a large amount of log entries (2k2) and they're mostly ignored in normal workflows.

We may also look into warnings that are raised during simulations and stdcm requests (mostly margin related), though it's not necessarily excessive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core Work on Core Service difficulty:good first issue Good for newcomers kind:refacto-task Task related to Refactorization Epic
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant