Hi,

I'm running Slim 2.2.0 and now encounter this error when declaring a new MonologWriter:

Fatal error:  Undefined class constant 'Slim\Log::EMERGENCY'

I get this error for all the new log levels added as part of: 00c4e3b872fbb2250c97bf7fefad326949902686

If I revert the changes everything works again.

Monolog, as of 1.15.0, tries to create a dir on every log action and raises an exception: https://github.com/Seldaek/monolog/blob/6dd76b944d42d7b27bb3d09cd0f6fa88a80817f5/src/Monolog/Handler/StreamHandler.php#L51

Slim-Monolog creates an unused monolog instance with an invalid log dir in its constructor: https://github.com/Flynsarmy/Slim-Monolog/blob/master/Log/MonologWriter.php#L108

So applications with Monolog 1.15.0 and Slim-Monolog won't work now, I think.

There is a hard-coded log location at line 110: https://github.com/Flynsarmy/Slim-Monolog/blob/master/Log/MonologWriter.php#L110

new \Monolog\Handler\StreamHandler('./logs/'.date('y-m-d').'.log'),

Since this hard coded location merges into the other locations array, it could easily cause a lot of problems in light-weight situations (like docker containers) which have virtually no disk space and do all their logging remotely. It also destroys one of the most valuable things about Monolog, that you have fine, granular control over where the logs go.

It really should be 'handlers' => array(),

Worse yet, because this merge is silent & undocumented, it took me about 3 hours to track this down as I didn't have a directory in "." called "logs".....

adds a public method to retrieve the instanced \Monolog\Logger object, to access its methods.

This is because, since Monolog#658, it's possible to configure the Logger instance to avoid using microsecond resolution timestamps, saving a few milliseconds on a middle sized PHP app.

So that I can atleast include a version number in my composer.json file rather then dev-master, because if a breaking change was to be made in dev-master, my code would be broken at that point.

Monolog, as of 1.15.0, tries to create a dir on every log action and raises an exception. Slim-Monolog creates an unused monolog instance with an invalid log dir in its constructor.

Are the installation instructions missing something or am I? Shouldn't the install be:

composer require flynsarmy/slim-monolog

The installation instructions in the README shows usage, not installing.

I did the composer require as shown above, as I assume that this was assumed? But then I get the following error:

Fatal error: Uncaught Error: Class 'Slim\Log' not found in /var/www/server/public/index.php:10 Stack trace: #0 {main} thrown in /var/www/server/public/index.php on line 10

I would think there should be clear install instructions and then clear usage instructions. Code that I could drop into a route and it would just work.

Does this library support Slim v3?

It doesn't mention any version requirement in README.md and I'm getting an error that Slim\Log colud not be found.

I looked in Slim's source, and v2 has a \Slim\Log, while 3v does not.

The newest commit for monolog 1.15.0 breaks my logging:

$config['app']['log.writer'] = new \Flynsarmy\SlimMonolog\Log\MonologWriter(array(
    'handlers' => array(
        new \Monolog\Handler\StreamHandler(
            realpath(__DIR__ . '/logs')
                .'/'.$_ENV['SLIM_MODE'] . '_' .date('Y-m-d').'.log'
        ),
    ),
));

I get this error:

Fatal error: Uncaught exception 'UnexpectedValueException' with message 'There is no existing directory at "./logs" and its not buildable: Permission denied'

When I output the $stream in StreamHandler->construct() i get:

mylocalhost/mysite/logs/development_2015-07-17.log./logs/15-07-17.log

It seems like the path concatenation is somehow off.

Is it possible to pass context information to Monolog?

Slim's logging overview mentions the ability to pass mixed information but I haven't been able to sort out any way to pass context information through slim-monolog to Monolog.