PHPackages                             blackbricksoftware/civicrm-container-logs - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Logging &amp; Monitoring](/categories/logging)
4. /
5. blackbricksoftware/civicrm-container-logs

ActiveCivicrm-ext[Logging &amp; Monitoring](/categories/logging)

blackbricksoftware/civicrm-container-logs
=========================================

Write CiviCRM Logs to stderr. Useful for running CiviCRM inside a Docker container.

v1.0.7(3mo ago)152AGPL-3.0PHPPHP ^8.1

Since Aug 9Pushed 3mo agoCompare

[ Source](https://github.com/blackbricksoftware/civicrm-container-logs)[ Packagist](https://packagist.org/packages/blackbricksoftware/civicrm-container-logs)[ RSS](/packages/blackbricksoftware-civicrm-container-logs/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (5)Dependencies (1)Versions (8)Used By (0)

CiviCRM Extension: Container Logging
====================================

[](#civicrm-extension-container-logging)

This extension replaces the default CiviCRM log channels to send all logs to `stderr` (currently). This is especially useful when running CiviCRM inside a Docker container, as it allows logs to be consolidated and managed by the container runtime.

Features
--------

[](#features)

- Redirects all CiviCRM logs to `stderr`
- Simplifies log management in containerized environments

Usage
-----

[](#usage)

1. Install the extension in your CiviCRM installation.
2. Enable the extension from the CiviCRM admin interface.
3. Logs will now appear in the container's standard error output.

Configuration
-------------

[](#configuration)

### Log Level Configuration

[](#log-level-configuration)

You can control the minimum log level emitted by this extension using the `CIVICRM_CONTAINER_LOGS_LEVEL` constant. Set this constant in your environment or configuration to filter logs according to severity. The log level defaults to `debug`;

This constant accepts any value supported by [`\Monolog\Level`](https://seldaek.github.io/monolog/doc/01-usage.html#log-levels). Monolog supports the logging levels described by [RFC 5424](https://datatracker.ietf.org/doc/html/rfc5424).

- **DEBUG (100):** Detailed debug information.
- **INFO (200):** Interesting events. Examples: User logs in, SQL logs.
- **NOTICE (250):** Normal but significant events.
- **WARNING (300):** Exceptional occurrences that are not errors. Examples: Use of deprecated APIs, poor use of an API, undesirable things that are not necessarily wrong.
- **ERROR (400):** Runtime errors that do not require immediate action but should typically be logged and monitored.
- **CRITICAL (500):** Critical conditions. Example: Application component unavailable, unexpected exception.
- **ALERT (550):** Action must be taken immediately. Example: Entire website down, database unavailable, etc. This should trigger the SMS alerts and wake you up.
- **EMERGENCY (600):** Emergency: system is unusable.

**Example usage:**

```
define('CIVICRM_CONTAINER_LOGS_LEVEL', 'warning');
```

This will ensure only warnings and more severe messages are logged.

Requirements
------------

[](#requirements)

- PHP8.1 or newer
- CiviCRM installation
- Docker container environment (recommended)

References
----------

[](#references)

- [Replace core logging with Monolog](https://lab.civicrm.org/extensions/monolog)
- [CiviCRM Developer Guide: Logging](https://docs.civicrm.org/dev/en/latest/framework/logging/)

###  Health Score

39

—

LowBetter than 85% of packages

Maintenance84

Actively maintained with recent releases

Popularity11

Limited adoption so far

Community2

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~27 days

Recently: every ~6 days

Total

7

Last Release

113d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/49ef798c46472a4224ac686d224ee867915858ae5325a60f5feee5c1cb833928?d=identicon)[redbeanbananas](/maintainers/redbeanbananas)

### Embed Badge

![Health badge](/badges/blackbricksoftware-civicrm-container-logs/health.svg)

```
[![Health](https://phpackages.com/badges/blackbricksoftware-civicrm-container-logs/health.svg)](https://phpackages.com/packages/blackbricksoftware-civicrm-container-logs)
```

###  Alternatives

[symfony/monolog-bridge

Provides integration for Monolog with various Symfony components

2.6k189.7M257](/packages/symfony-monolog-bridge)[rollbar/rollbar

Monitors errors and exceptions and reports them to Rollbar

33723.7M81](/packages/rollbar-rollbar)[illuminate/log

The Illuminate Log package.

6224.3M517](/packages/illuminate-log)[honeybadger-io/honeybadger-php

Honeybadger PHP library

381.5M4](/packages/honeybadger-io-honeybadger-php)[graycore/magento2-stdlogging

A Magento 2 module that changes all logging handlers to stdout

2382.6k](/packages/graycore-magento2-stdlogging)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
