-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[elastic-agent] Improve log messages #25372
Conversation
This PR improves the log messages to make them easier to consume by users. * Change unroll to unenroll, that is what we use in the UI too * Trigger unenroll only when the maxCounter is exceeded (nit) * Move Artifact has been built with security disable to info. This only happens for internal builds * Move log message around binary already exists to debug level as this is an expected behaviour * Be more specific about binary downloads * For state changes, move the message first. That is the most interesting part for a user
Pinging @elastic/agent (Team:Agent) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, one comment.
This PR improves the log messages to make them easier to consume by users. * Change unroll to unenroll, that is what we use in the UI too * Trigger unenroll only when the maxCounter is exceeded (nit) * Move Artifact has been built with security disable to info. This only happens for internal builds * Move log message around binary already exists to debug level as this is an expected behaviour * Be more specific about binary downloads * For state changes, move the message first. That is the most interesting part for a user (cherry picked from commit 89d2b36)
This PR improves the log messages to make them easier to consume by users. * Change unroll to unenroll, that is what we use in the UI too * Trigger unenroll only when the maxCounter is exceeded (nit) * Move Artifact has been built with security disable to info. This only happens for internal builds * Move log message around binary already exists to debug level as this is an expected behaviour * Be more specific about binary downloads * For state changes, move the message first. That is the most interesting part for a user (cherry picked from commit 89d2b36)
This PR improves the log messages to make them easier to consume by users. * Change unroll to unenroll, that is what we use in the UI too * Trigger unenroll only when the maxCounter is exceeded (nit) * Move Artifact has been built with security disable to info. This only happens for internal builds * Move log message around binary already exists to debug level as this is an expected behaviour * Be more specific about binary downloads * For state changes, move the message first. That is the most interesting part for a user (cherry picked from commit 89d2b36) Co-authored-by: Nicolas Ruflin <spam@ruflin.com>
This PR improves the log messages to make them easier to consume by users. * Change unroll to unenroll, that is what we use in the UI too * Trigger unenroll only when the maxCounter is exceeded (nit) * Move Artifact has been built with security disable to info. This only happens for internal builds * Move log message around binary already exists to debug level as this is an expected behaviour * Be more specific about binary downloads * For state changes, move the message first. That is the most interesting part for a user (cherry picked from commit 89d2b36) Co-authored-by: Nicolas Ruflin <spam@ruflin.com>
This PR improves the log messages to make them easier to consume by users.