LogChannel

Get fallback log channel name.

Parse the string level into a Monolog constant.

Parse the action level from the given configuration.

Extract the log channel from the given configuration.

Bind the provided callback to the class instance.

Create a new Log manager instance.

Build an on-demand log channel.

Create a new, on-demand aggregate logger instance.

Get a log channel instance.

Get a log driver instance.

Attempt to get the log from the local cache.

Create a configured logger, optionally retaining a named channel.

Apply the configured taps for the logger.

Parse the given tap class string into a class name and arguments string.

Create an emergency log handler to avoid white screens of death.

Resolve the given log instance by name.

Call a custom driver creator.

Create a custom log driver instance.

Create an aggregate log driver instance.

Create an instance of the single file log driver.

Create an instance of the daily file log driver.

Create an instance of the Slack log driver.

Create an instance of the syslog log driver.

Create an instance of the "error log" log driver.

Create an instance of any handler available in Monolog.

Prepare the handlers for usage by Monolog.

Prepare the handler for usage by Monolog.

Get a Monolog formatter instance.

Create a wrapped context log processor.

Wrapping in ResolvedContextLogProcessor allows createStackDriver() to filter out context processors from constituent channels regardless of how the processor was bound (class, closure, or custom callable).

Share context across channels and stacks.

The context shared across channels and stacks.

Flush the log context on all currently resolved channels.

Flush the shared context.

Get the log connection configuration.

Get the default log driver name.

Set the default log driver name.

Boot-only. Mutates process-global config; per-request use races across coroutines.

Register a custom driver creator Closure.

Boot-only. The callback persists in the singleton's customCreators array for the worker lifetime and applies to every subsequent channel resolution.

Unset the given channel instance.

Boot or tests only. Mutates the singleton's channel cache; concurrent coroutines may already hold a reference to the channel and next resolution will rebuild with fresh handlers (file handles, etc.).

Parse the driver name.

Get all of the resolved log channels.

System is unusable.

Action must be taken immediately.

Example: Entire website down, database unavailable, etc. This should trigger the SMS alerts and wake you up.

Critical conditions.

Example: Application component unavailable, unexpected exception.

Runtime errors that do not require immediate action but should typically be logged and monitored.

Exceptional occurrences that are not errors.

Example: Use of deprecated APIs, poor use of an API, undesirable things that are not necessarily wrong.

Normal but significant events.

Interesting events.

Example: User logs in, SQL logs.

Detailed debug information.

Logs with an arbitrary level.

Set the application instance used by the manager.

Tests only. Swaps the singleton's Application reference; per-request use races across coroutines and breaks every concurrent request resolving services through this manager.

Dynamically call the default driver instance.

Create the Sentry logs channel.