mz-configure-loki-logging

Centralized logging for Flask apps uses Grafana Loki to collect structured logs from multiple services. Add the mazza-base dependency, place the CA certificate, update your Dockerfile, and call configure_logging() at the top of your main application file to enable automatic log shipping to Loki endpoints specified via environment variables.

Yes. Set DEBUG_LOCAL=true for local console logging or false for production Loki shipping. The same configure_logging call handles both modes automatically, eliminating the need for separate configurations while keeping local development logs readable.

You need the mazza-base library, a CA certificate file (mazza.vc_CA.pem), Loki endpoint credentials (MZ_LOKI_* environment variables), a LOG_LEVEL setting, and a Dockerfile update. The Skill handles the rest through a single function call in your application entry point.

Yes. Loki logging applies to both new Flask services and existing Python applications. Integration requires adding the mazza-base dependency and initializing configure_logging at the top of your main file; no architectural changes to your Flask code are needed.

Environment-driven logging lets you toggle between console output for local debugging and secure Loki shipping for production without code changes. Use DEBUG_LOCAL and LOG_LEVEL environment variables to control behavior across your Flask service's deployment lifecycle.

CA certificate-secured connections encrypt all log traffic from Python apps to Grafana Loki. The mazza-base library enforces this encryption by default, requiring the CA bundle path to establish authenticated, secure channels for centralized log collection.