Change default log level to info

[Akagi201]

Summary by CodeRabbit

• Improvements
  • Enhanced logging functionality to filter messages at the INFO level or higher, improving the clarity of log outputs.
  • Introduced better management of logging resources for improved performance.

[coderabbitai]

Walkthrough

The changes in this pull request involve modifications to the logging configuration within the run function of the main.rs file. The logging setup is updated to filter messages at the INFO level or higher, enhancing the logging functionality. Additionally, a new variable _guard is introduced to manage logging resources effectively, although its initialization is conditional based on the logging configuration.

Changes

File	Change Summary
crates/cmd/src/main.rs	Updated logging configuration to filter messages at the INFO level; introduced _guard variable for managing logging resources.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant Logger
    participant FileAppender

    App->>Logger: Initialize logging
    Logger->>Logger: Set log level to INFO
    Logger->>FileAppender: Configure file logging
    FileAppender-->>Logger: Return guard
    Logger->>App: Logging initialized

Loading

🐇 "In the code where logs do play,
We set the level, bright as day.
INFO shines, the noise is tamed,
With guards in place, our logs are named.
Hopping through logs, clear and bright,
Our changes bring a joyful light!" 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 323509d and 5664951.

📒 Files selected for processing (1)

• crates/cmd/src/main.rs (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• crates/cmd/src/main.rs

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Akagi201]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 84839d7 and 323509d.

📒 Files selected for processing (1)

• crates/cmd/src/main.rs (2 hunks)

🧰 Additional context used

🔇 Additional comments (3)

crates/cmd/src/main.rs (3)

4-4: LGTM: Appropriate import added

The import of LevelFilter is correctly added and is necessary for the changes made to the logging configuration.

---

19-20: LGTM: Console logging configuration updated correctly

The changes to the console logging configuration are well-implemented:

1. The filter_layer now includes LevelFilter::INFO, which aligns with the PR objective.
2. The implementation is consistent with Rust logging best practices.
3. The added empty line improves code readability.

These changes effectively set the default log level to INFO for console logging.

---

27-27: LGTM: File logging configuration updated consistently

The changes to the file logging configuration are well-implemented and consistent with the console logging changes:

1. The filter_layer now includes LevelFilter::INFO, which aligns with the PR objective.
2. The implementation ensures that both console and file logging use the same log level filter.

This change effectively sets the default log level to INFO for file logging, maintaining consistency across logging methods.