TODO :

• Removing the Interface suffix from the Contracts interfaces.

My most often want when debugging is to see the newest entry in the newest (daily) log file.

I suggest the dashboard \log-viewer would put the entry on the very top.
Best solution would be automatic refresh if only a new entry would generate.

Outside of this lack, your viewer is great! Thank you!

Hi,

where is menu generated? I'm using my own routes,controller and views. I can't find where URL is added, because I have disabled routes for logviewer and now I get

Route [log-viewer::logs.filter] not defined in views/admin/logs/menu.blade.php

This is code for menu

@foreach($log->menu() as $level => $item)
    @if ($item['count'] === 0)
        <a href="#" class="list-group-item disabled">
            <span class="badge">
                {{ $item['count'] }}
            </span>
            {!! $item['icon'] !!} {{ $item['name'] }}
        </a>
    @else
        <a href="{{ $item['url'] }}" class="list-group-item {{ $level }}"> {{-- here is the issue --}}
            <span class="badge level-{{ $level }}">
                {{ $item['count'] }}
            </span>
            <span class="level level-{{ $level }}">
                {!! $item['icon'] !!} {{ $item['name'] }}
            </span>
        </a>
    @endif
@endforeach

Hello and thanks for your package.
I think it would be nice if you may add support for multiple filenames in log configuration (for example by allowing regex pattern for the prefix) because the current configuration seems too rigid imo.

To clarify I've an application where there some logs divided by their responsabilities (products-2016-07-01.log, storage-2016-07-01.log). As of now I can't support them both.

Thanks in advance for your attention.

I just tried this package in laravel 5.1 but I getting an error when I go to /log-viewer on my project:

InvalidArgumentException in FileViewFinder.php line 112: No hint path defined for [log-viewer].

in FileViewFinder.php line 112
at FileViewFinder->getNamespaceSegments('log-viewer::dashboard') in FileViewFinder.php line 90
at FileViewFinder->findNamedPathView('log-viewer::dashboard') in FileViewFinder.php line 76
at FileViewFinder->find('log-viewer::dashboard') in Factory.php line 151

I followed the steps given in the wiki and the command: php artisan route:list, list all routes:

GET|HEAD | log-viewer                      | log-viewer::dashboard     | Arcanedev\LogViewer\Http\Controllers\LogViewerController@index
GET|HEAD | log-viewer/logs                 | log-viewer::logs.list     | Arcanedev\LogViewer\Http\Controllers\LogViewerController@listLogs    |            |
DELETE   | log-viewer/logs/delete          | log-viewer::logs.delete   | Arcanedev\LogViewer\Http\Controllers\LogViewerController@delete      |            |
GET|HEAD | log-viewer/logs/{date}          | log-viewer::logs.show     | Arcanedev\LogViewer\Http\Controllers\LogViewerController@show        |            |
GET|HEAD | log-viewer/logs/{date}/download | log-viewer::logs.download | Arcanedev\LogViewer\Http\Controllers\LogViewerController@download    |            |
GET|HEAD | log-viewer/logs/{date}/{level}  | log-viewer::logs.filter   | Arcanedev\LogViewer\Http\Controllers\LogViewerController@showByLevel

I have package's version 3.7.9. Can someone help with this issue?

Hi,
I am using the Laravel 5 Boilerplate package. It has your package as one of the dependencies within the admin area.
As soon as the log file is empty (which should be a good thing) I get the following error:
local.ERROR: ErrorException: Division by zero in ../vendor/arcanedev/log-viewer/src/Http/Controllers/LogViewerController.php:186
I guess the $count variable is not checked as being zero or not and thus dividing by it does not make sense if it is a zero.

Minor issue, but can be a big problem.

I got the following error at the time of running the command composer update

Access level to Arcanedev\LogViewer\LogViewerServiceProvider::publishConfig() must be protected (as in class Arcanedev\Support\PackageServiceProvider) or weaker

Not sure if this is just my specific installation, but I did a composer update from arcanedev/support 3.6.10 to 3.7.1 and I now have the following error stopping my entire application from running:

Error Output: PHP Fatal error:  Declaration of Arcanedev\LogViewer\Providers\RouteS
  erviceProvider::map() must be compatible with Arcanedev\Support\Providers\RouteServ
  iceProvider::map(Illuminate\Contracts\Routing\Registrar $router) in /home/vagrant/C
  ode/GitHub/Larave5LargeScaleBP/vendor/arcanedev/log-viewer/src/Providers/RouteServi
  ceProvider.php on line 15

Any ideas?

This package looks well thought-through and organised - looking forward to trying it out.

Now, every single other log viewer package I've seen starts by loading an entire log file into memory, then parsing it from there. When the log files get big, then it blows the memory limits and fails. This can be a big problem at those times when you really need to be able to view the logs.

So, does this package load whole log files into memory (in parsed or raw form)? Or can it extract a portion of a log file direct from disk based on the page options (e.g. retrieve just log entries N to N+m from a file)?

It strikes me also that the start of each log entry could be indexed by byte position, so a position in a file can be seeked very quickly. Even if only every 10th or 100th log entry were indexed, it would provide some starting points.

Anyway - this is mainly a question (and I have not found the bit where you actually open the file for reading yet, so I don't know the answer).

Hi there!

Here is the problem:

I have a middleware enabled for LogViewer, which checks if the user has access to open and see LogViewer. This middleware runs 2 sql commands, one to load the user model, and another one to check if the user has the correct rule to view LogViewer. Since my application logs all sqls, these 2 sqls are fired for every new request and stored in laravel log file.

When serving my app In Windows 10 using XAMPP, if I try to delete the current log in LogViewer, it fails with the following exception:

I'm guessing the problem is LogViewer trying to delete the file, and Laravel trying to store new log right away. If I delete a log from yesterday, it works just fine.

Serving my app from Linux works just fine as well. The moment I delete the log file, the LogViewer page is refreshed with an already new log file with 2 info lines (those 2 sqls I said before).

This is not critical, but would be nice to work just like it works on linux (if possible 😄)

Thanks!

Removing arcanedev/support (3.7.0)
Installing arcanedev/support (3.7.2)
Since this is being loaded from the logviewer package, I can't roll back the version with out modifying the package. Can this issue be quickly resolved?

PHP Fatal error:  Declaration of Arcanedev\LogViewer\Providers\RouteServiceProvider::map(Illuminate\Routing\Router $router) must be compatible with Arcanedev\Support\Providers\RouteServiceProvider::map(Illuminate\Contracts\Routing\Registrar $router) in /home/vagrant/octo/vendor/arcanedev/log-viewer/src/Providers/RouteServiceProvider.php on line 14

  [Symfony\Component\Debug\Exception\FatalErrorException]                                                                                                                                                                                  
  Declaration of Arcanedev\LogViewer\Providers\RouteServiceProvider::map(Illuminate\Routing\Router $router) must be compatible with Arcanedev\Support\Providers\RouteServiceProvider::map(Illuminate\Contracts\Routing\Registrar $router)  

Hey there, first of all I love your library! Use it every day and it's just great the way it is!

I noticed there's a middleware configuration and I was wondering if I could use it to accomplish what I'm trying to do in a clean way.

On my dev environment I want to push all the error messages to a redis channel. There's probably some dirty ways I could accomplish this but was wondering if I could do it using your extension and the middleware config.

I just need a place to basically add my little redis logging function. I still want the errors to be written to the log files like usual but I want to also push them on redis. I've never used a middleware yet, could you possibly take a moment to show me how I might accomplish this please?

Let's say my function is LiveLog::pushLog($errorStr);

Thanks!!

Hi,
My I have protected access with middle ware however it is redirecting always even when someone is eligible.
How can I fix it?
Regards

Worth it or not ?

It would be cool if you could group by exception types, similar to Bugsnag. I find that to be more useful than grouping by emergency level. That way you can also gauge how many exceptions of a certain type there are.

Hi,

I want to add the jwt.auth midleware but this middleware wait for a token, don´t use the session. How can i integrate your package with jwt auth package to works in internall calls like http://localhost:5000/log-viewer/logs/2016-08-29

My Laravel server is primarily a RESTful API server. I use jwt tokens for stateless authentication. I like this log viewer a lot but can't figure out how to use it. I have a middleware that expects a token. I set an iframe that successfully loads the log viewer when I set the token on the src url. The problem is the subsequent requests from within the log viewer don't have the token and so they fail.

Is there a way to set a name/value pair on the requests the log viewer makes?

Recently, we faced permission issue for creating logs. So we created separate log file for cli. Our logs file names like laravel-cli-2016-05-19.log, laravel-fpm-fcgi-2016-05-14. Permission issue is resolve, but we are not able view these log files using LogViewer.

How to view those log files?

DONE :

• Set a custom storage log location (Issue #23 - PR #25).
• Refactoring (PR #27).

Hi there,
great plugin.
But with 7 logs 30M in total I got fail response with:

production.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes)' in /mnt/data/webhosting/ftp/azpneu/StudioV2/laravel/vendor/arcanedev/log-viewer/src/Utilities/LogParser.php:91

Is is possible to fix it please?

Regards
Jan

I am using "arcanedev/log-viewer": "~3.5" and tried to install via composer and got the following error. Then i changed the version to ~3.7 (got the suggestion on #41) and problem was same. Could you please tell me the steps to resolve this issue?

Error Output: PHP Fatal error:  Declaration of Arcanedev\LogViewer\Providers\RouteServiceProvider::map() must be compatible with Arcanedev\Sup  
  port\Providers\RouteServiceProvider::map(Illuminate\Contracts\Routing\Registrar $router) in /home/nasirkhan/.local/share/Trash/files/bsk-drh-m  
  is5/vendor/arcanedev/log-viewer/src/Providers/RouteServiceProvider.php on line 15 
`

Hi,
After doing the exact installation instructions I am getting:

  [Symfony\Component\Console\Exception\CommandNotFoundException]  
  There are no commands defined in the "log-viewer" namespace.   

this is my composer

"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
    "php": ">=5.5.9",
    "laravel/framework": "5.2.*",
    "torann/geoip": "0.2.*@dev",
    "arcanedev/log-viewer": "~3.0"
},
"require-dev": {
    "fzaninotto/faker": "~1.4",
    "mockery/mockery": "0.9.*",
    "phpunit/phpunit": "~4.0",
    "symfony/css-selector": "2.8.*|3.0.*",
    "symfony/dom-crawler": "2.8.*|3.0.*",
    "predis/predis": "~1.0",
    "guzzlehttp/guzzle": "~6.0"
},

this is the service provider:

Arcanedev\LogViewer\LogViewerServiceProvider::class,

Any idea?
Thanks

Is there is a way to add an alias for routes?

I want to have an easy way to make something like this: {{ route('admin.log-viewer') }}

When tried to install using :

composer require "arcanedev/log-viewer:~3.0"

I got :

[ErrorException]
  Declaration of Arcanedev\LogViewer\LogViewerServiceProvider::registerConfig() should be compatible with Arcanedev\Support\PackageServiceProvider::registerConfig($separator = '.')

Any idea?

I just tried this package in 2 laravel (5.1) installations (to be sure). I keep getting a 404 error when I go to /log-viewer on my project.

Steps I have done:

• Setup composer.json correcty
• Composer update
• Add provider to config/app.php
• Publish it through command
• Acces domain.com/log-viewer

Result 404 page

Am I missing something? Or is my routes blocking this feature?

I want to include your log viewer in my own theme, but the view share in AppServiceProvider is not working. In my nav I display the name of the user, but now i get the error: Trying to get property of non-object.

Hi.

I am looking for the solution on how to authenticate user by adding middleware to the config file. I have probably the same problem as #63 has. According to the laravel docs

if(Auth::check()){

}

should be true if the user is logged in. This is working for each route in my routes.php but not if I use it with the log-viewer config.

Hi, running composer update this morning, I am getting this fatal error.

[RuntimeException]
Error Output: PHP Fatal error: Declaration of Arcanedev\LogViewer\Providers\RouteServiceProvider::map() must be compatible with Arcanedev\Support\Providers\RouteServiceProvider::map(I
lluminate\Contracts\Routing\Registrar $router) in /home/vagrant/Code/www/vendor/arcanedev/log-viewer/src/Providers/RouteServiceProvider.php on line 15

Anyone could help?

Thank you

Hi there!

I have the following config in config/log-viewer.php:

'locale' => 'en',

But the LogViewer ignores this, and uses the default application locale, which is "pt-BR" in my case.

I would like to use "en" in LogViewer, to avoid label crashes like this one:

Even when publishing the lang files, the "en" locale is not loaded at all.

How to use "en" locale in LogViewer?

Best regards,
Rafael Pacheco.

Route [] not defined. (View: ../resources/views/vendor/log-viewer/_partials/menu.blade.php) (View: ../resources/views/vendor/log-viewer/_partials/menu.blade.php)

hi

when i access http://{my-project}/log-viewer, there is a error come out
"Allowed memory size of 67108864 bytes exhausted (tried to allocate 8388616 bytes) "
and it happened in "log-viewer/src/Helpers/LogParser.php:71 preg_match_all()".

i can edit my php.ini to increase memory for a while,
but in future if log files go to bigger then
i have to edit php.ini to increase memory again

can i not read all log files , for example , only read last 10 log files or last 7days log files?

Regards

The GLOB_BRACE flag is not available on some non GNU systems, like windows

code in \src\Utilities\Filesystem.php line 284

$files = $this->filesystem->glob( $this->storagePath.DS.$pattern, GLOB_BRACE );

GLOB_BRACE should be (defined('GLOB_BRACE') ? GLOB_BRACE : 0)

In logs.blade.php, the single quotes are missing in the selector $("a[href=#delete-log-modal]"). It should be $("a[href='#delete-log-modal']")

After installing the LogViewer with composer I wanted to publish the configs but I got the following error:

vagrant@homestead:~/projects/mt$ php artisan vendor:publish --provider="Arcanedev\LogViewer\LogViewerServiceProvider" --force
PHP Fatal error:  Access level to Arcanedev\LogViewer\LogViewerServiceProvider::registerConfig() must be protected (as in class Arcanedev\Support\Laravel\PackageServiceProvider) or weaker in /home/vagrant/projects/mt/vendor/arcanedev/log-viewer/src/LogViewerServiceProvider.php on line 12
PHP Stack trace:
PHP   1. {main}() /home/vagrant/projects/mt/artisan:0
PHP   2. Illuminate\Foundation\Console\Kernel->handle() /home/vagrant/projects/mt/artisan:36
PHP   3. Illuminate\Foundation\Console\Kernel->bootstrap() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:98
PHP   4. Illuminate\Foundation\Application->bootstrapWith() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:206
PHP   5. Illuminate\Foundation\Bootstrap\RegisterProviders->bootstrap() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:203
PHP   6. Illuminate\Foundation\Application->registerConfiguredProviders() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterProviders.php:17
PHP   7. Illuminate\Foundation\ProviderRepository->load() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:507
PHP   8. Illuminate\Foundation\ProviderRepository->compileManifest() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php:60
PHP   9. Illuminate\Foundation\ProviderRepository->createProvider() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php:114
PHP  10. spl_autoload_call() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php:146
PHP  11. Composer\Autoload\ClassLoader->loadClass() /home/vagrant/projects/mt/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php:146
PHP  12. Composer\Autoload\includeFile() /home/vagrant/projects/mt/vendor/composer/ClassLoader.php:301
PHP  13. include() /home/vagrant/projects/mt/vendor/composer/ClassLoader.php:412



  [Symfony\Component\Debug\Exception\FatalErrorException]
  Access level to Arcanedev\LogViewer\LogViewerServiceProvider::registerConfig() must be protected (as in class Arcanedev\Support\Laravel\PackageServiceProvider) or weaker

Setting the registerConfig function to protected fixed the issue.

add custom storage log location
or
read all file and folder log file

tnx 👍

I just ran an update through composer and it failed with the following message:

Declaration of Arcanedev\LogViewer\Providers\RouteServiceProvider::map() must be compatible with Arcanedev\Support\Providers\RouteServiceProvider::map(Illuminate\Contracts\Routing\Registrar $router)

BTW I'm using the LogViewer through @rappasoft's boilerplate if that's any help.

any config option not to load pre-included views?
because i want to use my own views (if possible controller, model aswell)

please look at laravel-messenger
they provide same model,view,controller its upto the user to user them or not.

its great package but most of the sites already will have an admin panel, so we should be able to integrate into it.

I my app.php I have providers like that:

Arcanedev\LogViewer\LogViewerServiceProvider::class,
App\MyServiceProvider::class,

My provider registers the following route:

$router->get('{slug}', function () { return view('app'); })->where('slug', '(.*)?');

The problem is that despite the fact that App\MyServiceProvider is registered second, the lowest priority is always taken by LogViewer routes.
You can clearly see it in dump:

// dd(\Route::getRoutes()->getRoutesByMethod()['GET']);
  "{slug}" => Route {#167 ▶}
  "log-viewer" => Route {#170 ▶}
  "log-viewer/logs" => Route {#172 ▶}
  "log-viewer/logs/{date}" => Route {#175 ▶}
  "log-viewer/logs/{date}/download" => Route {#176 ▶}
  "log-viewer/logs/{date}/{level}" => Route {#177 ▶}

Any information is much appreciated.

Hello,

I have updated my laravel application and now i get this issue?

http://cl.ly/0o0N3X0K1y04

Do you know what is wrong?

Hi!

I have this line in my logfile:

[2016-01-25 08:57:54] local.INFO: Important event date set to 2016-01-17 15:00:00

However in log viewer in the daily view, the time column shows 15:00:00 instead of 08:57:54. It could be a regex problem I guess.

Do not use aliases in the package.
This forces the user to include aliases in the app configuration, even if he does not use them in own application.

Moreover, you can get unpredictable behavior if the alias will refer to the other facade (not the default).

See: navigation.blade.php and also check other files, just in case.

Right now, the %context% %extra% are just displayed as part of the %message%.

It would be nice to be able to access this information in a similar way as the call stack.

Is there a way to get some detailed documentation about customizing the layout of the dashboard to incorporate it into our own template and on how to log models activities ?

Worth it or not ?

Hello

I updated today log viewer to v3.7.0 and the following error raises every time I'm going to view log from a date:

ErrorException in UrlGenerator.php line 306:
Route [] not defined. (View: /var/www/html/localhost.dev/resources/views/vendor/log-viewer/_partials/menu.blade.php) (View: /var/www/html/localhost.dev/resources/views/vendor/log-viewer/_partials/menu.blade.php)

I have middleware set in the config file, but is there anyway to set a redirect instead of just an Unauthorized message?

I used this great package in all my software.

Now i'm getting started with Laravel 5.3 so i installed a package with

composer require arcanedev/log-viewer

and composer give me a 3.10 version (not 4).

later I registered a service provider and published configuration.

I also executed check command, and all things seems Ok.

When i go in http://localhost/[my-folder]/public/log-viewer I'm getting a not found laravel exception:

Have you some help?

Hi,

I'm trying to add the package to my app, but all the commands that I run return that the class does not exists

[InvalidArgumentException]
There are no commands defined in the "log-viewer" namespace.

The composer install runs OK, the config/app.php is also.
I search over here and found nothing like that, so I think I am the first in with this.

Here some thinks that may help.

Env:

System: Windows 10 build 14267
PHP: 7.0.0
Mysql: 5.6

Laravel 5.1.30

// config/app.php:
'providers' => [

    /*
     * Development Service Providers...
     */
    Barryvdh\Debugbar\ServiceProvider::class,

    /*
     * Laravel Framework Service Providers...
     */
    Illuminate\Foundation\Providers\ArtisanServiceProvider::class,
    Illuminate\Auth\AuthServiceProvider::class,
    Illuminate\Broadcasting\BroadcastServiceProvider::class,
    Illuminate\Bus\BusServiceProvider::class,
    Illuminate\Cache\CacheServiceProvider::class,
    Illuminate\Foundation\Providers\ConsoleSupportServiceProvider::class,
    Illuminate\Routing\ControllerServiceProvider::class,
    Illuminate\Cookie\CookieServiceProvider::class,
    Illuminate\Database\DatabaseServiceProvider::class,
    Illuminate\Encryption\EncryptionServiceProvider::class,
    Illuminate\Filesystem\FilesystemServiceProvider::class,
    Illuminate\Foundation\Providers\FoundationServiceProvider::class,
    Illuminate\Hashing\HashServiceProvider::class,
    Illuminate\Mail\MailServiceProvider::class,
    Illuminate\Pagination\PaginationServiceProvider::class,
    Illuminate\Pipeline\PipelineServiceProvider::class,
    Illuminate\Queue\QueueServiceProvider::class,
    Illuminate\Redis\RedisServiceProvider::class,
    Illuminate\Auth\Passwords\PasswordResetServiceProvider::class,
    Illuminate\Session\SessionServiceProvider::class,
    Illuminate\Translation\TranslationServiceProvider::class,
    Illuminate\Validation\ValidationServiceProvider::class,
    Illuminate\View\ViewServiceProvider::class,
    Illuminate\Html\HtmlServiceProvider::class,

    /*
     * Application Service Providers...
     */
    App\Providers\AppServiceProvider::class,
    App\Providers\EventServiceProvider::class,
    App\Providers\RouteServiceProvider::class,

    /*
     * Custom Services Providers...
     */
    Arcanedev\LogViewer\LogViewerServiceProvider::class,
    Collective\Html\HtmlServiceProvider::class,
    Cviebrock\EloquentSluggable\SluggableServiceProvider::class,
    Vinkla\Pusher\PusherServiceProvider::class,
    Zizaco\Entrust\EntrustServiceProvider::class,
    Intervention\Image\ImageServiceProvider::class,
    MaddHatter\LaravelFullcalendar\ServiceProvider::class,
    Laravel\Socialite\SocialiteServiceProvider::class,
    Torann\GeoIP\GeoIPServiceProvider::class,
    Alexpechkarev\GoogleGeocoder\GoogleGeocoderServiceProvider::class,
    Dsdevbe\LdapConnector\LdapConnectorServiceProvider::class,
    Maatwebsite\Excel\ExcelServiceProvider::class,

    /*
     * Personalization Services Providers...
     */
    Aws\Laravel\AwsServiceProvider::class,

    /*
     * Automation Services Providers...
     */
    Orangehill\Iseed\IseedServiceProvider::class,

    /*
     * My Services Providers...
     */
    App\Providers\HelperServiceProvider::class,

],

Anything that may help is appreciate!

Regards, Leandro.

Hi,

I am making a dashboard with adminlte.

I wanted to show your views inside my dashboard instead of a separate kind of dashboard like it is shown now.

Is this possible somehow? Could you help me with it maybe or say how to do it please?

Hi,

My production server uses logrotate to compress and rotate my log files.

Is there any way to set up LogViewer to be able to view these? At the moment my storage log folder looks like this:

Thanks very much!