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

chore(slo): replace error log level with debug #212975

Merged
merged 5 commits into from
Mar 4, 2025

Conversation

kdelemme
Copy link
Contributor

@kdelemme kdelemme commented Mar 3, 2025

Summary

Resolves #212972

This PR replaces the info and error log levels with debug since most of these errors are for developers or users. Not operations.

@kdelemme kdelemme added release_note:skip Skip the PR/issue when compiling release notes Team:obs-ux-management Observability Management User Experience Team v9.1.0 backport:skip This commit does not require backporting labels Mar 3, 2025
Copy link
Member

@maryam-saeidi maryam-saeidi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing the info logs.

For the cases in which we catch an error and we don't throw it, how would the user know something is wrong? Maybe we can add a comment for such cases and indicate why that error is not important or how it was handled.

@@ -87,7 +87,7 @@ export class TempSummaryCleanupTask {
params: {},
});
} catch (e) {
this.logger.error(`Error scheduling task, error: ${e}`);
this.logger.debug(`Error scheduling task, error: ${e}`);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, what is the implication of such an error? Does the user need to know about this error, or do we handle it in a meaningful way?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not sure about this one actually, maybe since it's a task, it is better to keep it as an error.

@kdelemme kdelemme self-assigned this Mar 4, 2025
@kdelemme kdelemme marked this pull request as ready for review March 4, 2025 17:46
@kdelemme kdelemme requested a review from a team as a code owner March 4, 2025 17:46
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@kdelemme kdelemme enabled auto-merge (squash) March 4, 2025 17:46
@kdelemme kdelemme requested a review from maryam-saeidi March 4, 2025 19:34
@kdelemme
Copy link
Contributor Author

kdelemme commented Mar 4, 2025

@maryam-saeidi had to re-request a review from you since you've done it before I opened the PR ;)

@kdelemme kdelemme merged commit d744538 into elastic:main Mar 4, 2025
9 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @kdelemme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:obs-ux-management Observability Management User Experience Team v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[SLO] Audit current logger level usage
3 participants