🔧(backend) backport logging configuration from docs

[FloChehab]

Backport the logging configuration from docs to LaSuite Meet after discussion with @lunika.

Add a proper base logging setup to restore usable logs in production. The initial repository bootstrap lacked a complete logging configuration, resulting in limited operational visibility.

Note that I have explicitely set the output to stdout to make sure it shows up in Grafana.

Summary by CodeRabbit

• Chores
  • Enhanced logging configuration to improve system diagnostics and monitoring capabilities with configurable log levels for better visibility into application behavior.

[coderabbitai]

Warning

Review limit reached

@FloChehab, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 32 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8925e37f-f804-4d2f-8c83-96d658059cf8

📥 Commits

Reviewing files that changed from the base of the PR and between 3a07464 and 9ac99e9.

📒 Files selected for processing (1)

• src/backend/dictaphone/settings.py

📝 Walkthrough

Walkthrough

A LOGGING configuration dictionary is added to the Base Django settings class. It defines a console formatter for JSON output, a StreamHandler routing to stdout, the root logger configured to that handler with an environment-variable log level, and a separate core logger with its own configurable level and propagation disabled.

Changes

Logging Configuration

Layer / File(s)	Summary
Console and core logger configuration src/backend/dictaphone/settings.py	LOGGING configuration sets up console formatting, root logger output to stdout with DJANGO_LOG_LEVEL, and a core logger with CORE_LOG_LEVEL and propagate: False.

---

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: adding logging configuration to the backend from documentation, matching the changeset which adds a LOGGING configuration block to settings.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}