Describes a logger instance.

The message MUST be a string or object implementing __toString().

The message MAY contain placeholders in the form: {foo} where foo
will be replaced by the context data in key "foo".

The context array can contain arbitrary data. The only assumption that
can be made by implementors is that if an Exception instance is given
to produce a stack trace, it MUST be in a key named "exception".

See https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md
for the full interface specification.

AbstractInterface
Methods
public abstract alert( $message, array $context = [])
 

Action must be taken immediately.

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

  • return void
public abstract critical( $message, array $context = [])
 

Critical conditions.

Example: Application component unavailable, unexpected exception.

  • return void
public abstract debug( $message, array $context = [])
 

Detailed debug information.

  • return void
public abstract emergency( $message, array $context = [])
 

System is unusable.

  • return void
public abstract error( $message, array $context = [])
 

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

  • return void
public abstract info( $message, array $context = [])
 

Interesting events.

Example: User logs in, SQL logs.

  • return void
public abstract log( $level, $message, array $context = [])
 

Logs with an arbitrary level.

public abstract notice( $message, array $context = [])
 

Normal but significant events.

  • return void
public abstract warning( $message, array $context = [])
 

Exceptional occurrences that are not errors.

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

  • return void
© 2020 Bruce Wells
Search Namespaces \ Classes
ConfigurationNumbers (0-9.) only