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

buildkitd: add logs to track boot info #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

adityamaru
Copy link

@adityamaru adityamaru commented Dec 23, 2024

Important

Add logging to buildkitd to track boot process times for locks, listeners, controllers, and workers.

  • Logging Enhancements:
    • Add log statements in main.go to track time for acquiring lock, setting up listeners, and initializing controllers.
    • Add log statements in main_containerd_worker.go to track time for applying flags, setting up runtime, and initializing workers.
  • Specific Log Additions:
    • Log time before and after acquiring lock in main.go.
    • Log time before and after setting up listeners and controllers in main.go.
    • Log time before and after applying containerd flags, setting up runtime, and initializing worker options in main_containerd_worker.go.

This description was created by Ellipsis for fd13b85. It will automatically update as commits are pushed.

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

👍 Looks good to me! Reviewed everything up to fd13b85 in 15 seconds

More details
  • Looked at 147 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 drafted comments based on config settings.
1. cmd/buildkitd/main.go:258
  • Draft comment:
    Consider using Debug log level for the newly added log messages to avoid verbosity in production environments. This applies to all similar log messages in this PR.
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The log messages added in this PR are useful for tracking the time taken for various operations. However, the log level used for these messages is Info, which might not be appropriate for all environments. In production, these logs could be too verbose. A better approach would be to use the Debug log level for these messages, as they are primarily useful for debugging purposes.

Workflow ID: wflow_eeynw19YMPtiDp3Q


You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

@aayushshah15
Copy link

Do we plan on merging this still, or are we waiting to see if the version bump just fixes our issues?

@adityamaru
Copy link
Author

adityamaru commented Dec 25, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants