fix: enable logback logging for the driver

[tchow-zlai]

Summary

• Similar to: feat: enable slf4j logging to work with logback #76 let's enable logback config for the main spark apps.

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• New Features
  • Updated logging configuration to capture only error-level messages, improving focus on critical issues in the Spark application.
  • Maintained clear formatting for console log messages, aiding in debugging and monitoring processes.

[coderabbitai]

Walkthrough

This pull request modifies the Logback configuration file (logback.xml) for the Spark application. The root logger's level is changed from INFO to ERROR, which restricts logging to error-level messages and above. The console appender remains unchanged, still outputting log messages formatted with the specified pattern. The logger for the package ai.chronon continues to log at the INFO level, but overall application logging is now limited to error messages due to the new root logger configuration.

Changes

File Path	Change Summary
spark/src/main/resources/logback.xml	Modified Logback configuration to change root logger level from INFO to ERROR, affecting overall logging behavior.

Possibly related PRs

• feat: enable slf4j logging to work with logback #76: The changes in this PR involve modifications to the Logback configuration, which directly relates to the changes made in the main PR that also modifies the Logback configuration file (logback.xml).

Suggested reviewers

• piyush-zlai
• nikhil-zlai

Poem

In the land of Spark, where logs do play,
A new config blooms, brightening the day.
With messages clear, and levels set right,
The console now glows, a logging delight!
Hopping through code, with joy we take flight,
Cheers to the changes, all shiny and bright! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 28e7b67 and a05a9c1.

📒 Files selected for processing (1)

• spark/src/main/resources/logback.xml (1 hunks)

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

• spark/src/main/resources/logback.xml

---

🪧 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.

[tchow-zlai]

cc @nikhil-zlai | @piyush-zlai changing this to ERROR should silence any logs below this severity by default. Classes in the ai.chronon namespace will follow INFO level logging.

[tchow-zlai]

Closing in favor of: #99