fix: use beeai_log_level variable

[xjacka]

Which issue(s) does this pull-request address?

Closes: #

Description

Checklist

General

• [x] I have read the appropriate contributor guide: Python / TypeScript
• [x] I have signed off on my commit: Python instructions / TypeScript instructions
• [x] Commit messages and PR title follow conventional commits
• [x] Appropriate label(s) added to PR: Python for Python changes, TypeScript for TypeScript changes

Code quality checks

• [x] Code quality checks pass: mise check (mise fix to auto-fix)

Testing

• [x] Unit tests pass: mise test:unit
• [ ] E2E tests pass: mise test:e2e
• [ ] Tests are included (for bug fixes or new features)

Documentation

• [x] Documentation is updated
• [x] Embedme embeds code examples in docs. To update after edits, run: Python mise docs:fix

[gemini-code-assist[bot]]

Summary of Changes

Hello @xjacka, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a significant improvement to the beeai-framework's logging configuration by allowing the default log level to be controlled via an environment variable. This change enhances the flexibility and deployability of applications built with the framework, enabling easier adjustment of logging verbosity across different environments. Additionally, it includes targeted refactoring of logger imports within utility modules to ensure proper configuration loading and improve code modularity.

Highlights

• Environment Variable for Log Level: The application's default log level can now be configured using the BEEAI_LOG_LEVEL environment variable, falling back to 'INFO' if not specified.
• Logger Instantiation Refactoring: The Logger instance in python/beeai_framework/utils/models.py and python/beeai_framework/utils/schema.py has been refactored to be imported and instantiated locally within the functions where it is used, rather than globally at the module level.
• Documentation and Example Updates: The documentation and example code for logger usage have been updated to reflect the new behavior, showing how the logger can be initialized without explicitly passing a level parameter.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.