PHPackages                             bbrist/laravel-console-logger - 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 & Monitoring](/categories/logging)
4. /
5. bbrist/laravel-console-logger

ActiveLibrary[Logging & Monitoring](/categories/logging)

bbrist/laravel-console-logger
=============================

Log to console during artisan commands

0.1.1(3y ago)044MITPHPPHP >=8.0

Since Jun 20Pushed 3y ago1 watchersCompare

[ Source](https://github.com/bbrist/laravel-console-logger)[ Packagist](https://packagist.org/packages/bbrist/laravel-console-logger)[ Docs](https://github.com/bbrist/laravel-console-logger)[ RSS](/packages/bbrist-laravel-console-logger/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (2)Dependencies (4)Versions (3)Used By (0)

laravel-console-logger
======================

[](#laravel-console-logger)

The `laravel-console-logger` package is a helper package designed to allow for more in-depth console logging

By default, adding this package to your project will automatically (via the ServiceProvider) start diverting logs (i.e. `Log::info()` statements) to console output. The log level that is output can be changed using the verbosity flags for the Artisan console (i.e. `-v`, `-vv`, `-vvv`, `-q`).

With the default configuration, `-q` will output nothing, no verbosity args will output `error` and higher, `-v`will output `warning` and higher, `-vv` will output `info` and higher, and `-vvv` will output all logs to console.

The `config/logging.php` configuration can be used to alter the default configuration. By default, `notice`, `error`, `critical`, `alert`, and `emergency` levels are logged to the `laravel.log` file in addition to the console (even if `-q` is specified). To add/remove levels to include in the `laravel.log` file, just set/modify the `console.logMethods`value in the `config/logging.php` file.

To log all logs to file, regardless of whether they are logged to console, you can set/modify the `console.logToFile` value to `true` in the `config/logging.php` file.

### Force Log to File

[](#force-log-to-file)

The `Log::logToFile()` method will force any following logs to log to `laravel.log`. You can explicitly set this status to `true` or `false` by providing the value as a parameter (i.e. `Log::logToFile(false)`).

This can be useful when you want to ensure that a chunk of code is logged to `laravel.log` regardless of where/how it's executed (dependent on the value of `env('LOG_LEVEL')`).

For example:

```
public function mymethod() {

    Log::logToFile(true);   // enable force log-to-file

    ...

    Log::info("some message");  // This will always be logged to file (dependent on the LOG_LEVEL ENV value)

    ...

    Log::logToFile(false);  // disable force log-to-file

}
```

###  Health Score

22

—

LowBetter than 22% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity44

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 80% of commits — single point of failure

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 ~11 days

Total

2

Last Release

1410d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/c02d0b884eb82fba6a66f5d3ee92b6b0f70bf6392fd6590d53168a86ce46c441?d=identicon)[bbrist](/maintainers/bbrist)

---

Top Contributors

[![bbrist](https://avatars.githubusercontent.com/u/67707859?v=4)](https://github.com/bbrist "bbrist (4 commits)")[![3brettb](https://avatars.githubusercontent.com/u/22225439?v=4)](https://github.com/3brettb "3brettb (1 commits)")

---

Tags

asyncconsolelaravelloggingartisanloggerlaravel-console-loggerasync-softwareasync-solutionsasync-software-solutions

###  Code Quality

TestsPest

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/bbrist-laravel-console-logger/health.svg)

```
[![Health](https://phpackages.com/badges/bbrist-laravel-console-logger/health.svg)](https://phpackages.com/packages/bbrist-laravel-console-logger)
```

###  Alternatives

[amphp/log

Non-blocking logging for PHP based on Amp, Revolt, and Monolog.

402.6M70](/packages/amphp-log)[guanguans/laravel-exception-notify

Monitor exception and report to the notification channels(Log、Mail、AnPush、Bark、Chanify、DingTalk、Discord、Gitter、GoogleChat、IGot、Lark、Mattermost、MicrosoftTeams、NowPush、Ntfy、Push、Pushback、PushBullet、PushDeer、PushMe、Pushover、PushPlus、QQ、RocketChat、ServerChan、ShowdocPush、SimplePush、Slack、Telegram、WeWork、WPush、XiZhi、YiFengChuanHua、ZohoCliq、ZohoCliqWebHook、Zulip).

14642.7k1](/packages/guanguans-laravel-exception-notify)[illuminated/console-logger

Logging and Notifications for Laravel Console Commands.

8674.9k](/packages/illuminated-console-logger)

PHPackages © 2026

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