Laravel logger is an activity event logger for your Laravel or Lumen application

Related tags

Logging middleware logger logging activity request-logging request-logger activity-log activity-logger activity-log-laravel laravel-logger laravel-logging activity-logging activity-drilldown activity-dashboard logging-dashboard logger-dashboard
Overview

Laravel Logger

Laravel Activity Logger

Laravel logger is an activity event logger for your Laravel or Lumen application. It comes out the box with ready to use with dashboard to view your activity. Laravel logger can be added as a middleware or called through a trait. Easily have an Activity Log. This package is easily configurable and customizable. Supports Laravel 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6, and 7+

Latest Stable Version Total Downloads Travis-CI Build StyleCI Scrutinizer Code Quality License: MIT

Table of contents

Features

Laravel Activity Logger Features
Logs login page visits
Logs user logins
Logs user logouts
Routing Events can recording using middleware
Records activity timestamps
Records activity description
Records activity details (optional)
Records activity user type with crawler detection.
Records activity Method
Records activity Route
Records activity Ip Address
Records activity User Agent
Records activity Browser Language
Records activity referrer
Customizable activity model
Activity panel dashboard
Individual activity drilldown report dashboard
Activity Drilldown looks up Id Address meta information
Activity Drilldown shows user roles if enabled
Activity Drilldown shows associated user events
Activity log can be cleared, restored, and destroyed using eloquent softdeletes
Cleared activity logs can be viewed and have drilldown ability
Uses font awesome, cdn assets can be optionally called in configuration
Uses Geoplugin API for drilldown IP meta information
Uses Language localization files
Lots of configuration options

Requirements

Integrations

Laravel logger can work out the box with or without the following roles packages:

Laravel Installation Instructions

  1. From your projects root folder in terminal run:
    composer require jeremykenedy/laravel-logger
  1. Register the package

  • Laravel 5.5 and up Uses package auto discovery feature, no need to edit the config/app.php file.

  • Laravel 5.4 and below Register the package with laravel in config/app.php under providers with the following:

    'providers' => [
        jeremykenedy\LaravelLogger\LaravelLoggerServiceProvider::class,
    ];
  1. Run the migration to add the table to record the activities to:
    php artisan migrate
  • Note: If you want to specify a different table or connection make sure you update your .env file with the needed configuration variables.

  1. Optionally Update your .env file and associated settings (see Environment File section)

  2. Optionally publish the packages views, config file, assets, and language files by running the following from your projects root folder:

    php artisan vendor:publish --tag=LaravelLogger

Lumen Installation Instructions

This installs laravel-logger without the GUI
  1. From your projects root folder in terminal run:
    composer require jeremykenedy/laravel-logger
  1. Register the package

Register the package with laravel in bootstrap/app.php with the following:

    $app->register(\Jaybizzle\LaravelCrawlerDetect\LaravelCrawlerDetectServiceProvider::class);
    $app->configure('laravel-logger');
    $app->register(\jeremykenedy\LaravelLogger\LaravelLoggerServiceProvider::class);
    $app->routeMiddleware(['activity' => \jeremykenedy\LaravelLogger\App\Http\Middleware\LogActivity::class, ]);
  1. Copy the configuration file laravel-logger.php to your config/ directory
Set LARAVEL_LOGGER_DISABLE_ROUTES=true in your .env file!
  1. Run the migration to add the table to record the activities to:
    php artisan migrate
  • Note: If you want to specify a different table or connection make sure you update your .env file with the needed configuration variables.
  1. Optionally Update your .env file and associated settings (see Environment File section)

Configuration

Laravel Activity Logger can be configured in directly in /config/laravel-logger.php if you published the assets. Or you can variables to your .env file.

Environment File

Here are the .env file variables available:

LARAVEL_LOGGER_DATABASE_CONNECTION=mysql
LARAVEL_LOGGER_DATABASE_TABLE=laravel_logger_activity
LARAVEL_LOGGER_ROLES_ENABLED=true
LARAVEL_LOGGER_ROLES_MIDDLWARE=role:admin
LARAVEL_LOGGER_MIDDLEWARE_ENABLED=true
LARAVEL_LOGGER_MIDDLEWARE_EXCEPT=
LARAVEL_LOGGER_ACTIVITY_MODEL=jeremykenedy\LaravelLogger\App\Models\Activity
LARAVEL_LOGGER_USER_MODEL=App\User
LARAVEL_LOGGER_USER_ID_FIELD=id
LARAVEL_LOGGER_DISABLE_ROUTES=false
LARAVEL_LOGGER_PAGINATION_ENABLED=true
LARAVEL_LOGGER_PAGINATION_PER_PAGE=25
LARAVEL_LOGGER_DATATABLES_ENABLED=true
LARAVEL_LOGGER_ENABLE_SEARCH=true
LARAVEL_LOGGER_SEARCH_FIELDS=description,user,method,route,ip
LARAVEL_LOGGER_DASHBOARD_MENU_ENABLED=true
LARAVEL_LOGGER_DASHBOARD_DRILLABLE=true
LARAVEL_LOGGER_LOG_RECORD_FAILURES_TO_FILE=true
LARAVEL_LOGGER_FLASH_MESSAGE_BLADE_ENABLED=true
LARAVEL_LOGGER_LAYOUT=layouts.app
LARAVEL_LOGGER_BOOTSTRAP_VERSION=4
LARAVEL_LOGGER_BLADE_PLACEMENT=stack                    #option: yield or stack
LARAVEL_LOGGER_BLADE_PLACEMENT_CSS=css-header           #placement name
LARAVEL_LOGGER_BLADE_PLACEMENT_JS=scripts-footer        #placement name
LARAVEL_LOGGER_JQUERY_CDN_ENABLED=true
LARAVEL_LOGGER_JQUERY_CDN_URL=https://code.jquery.com/jquery-2.2.4.min.js
LARAVEL_LOGGER_BOOTSTRAP_CSS_CDN_ENABLED=true
LARAVEL_LOGGER_BOOTSTRAP_CSS_CDN_URL=https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css
LARAVEL_LOGGER_BOOTSTRAP_JS_CDN_ENABLED=true
LARAVEL_LOGGER_BOOTSTRAP_JS_CDN_URL=https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js
LARAVEL_LOGGER_POPPER_JS_CDN_ENABLED=true
LARAVEL_LOGGER_POPPER_JS_CDN_URL=https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js
LARAVEL_LOGGER_FONT_AWESOME_CDN_ENABLED=true
LARAVEL_LOGGER_FONT_AWESOME_CDN_URL=https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css

Usage

Middleware Usage

Events for laravel authentication scaffolding are listened for as providers and are enabled via middleware. You can add events to your routes and controllers via the middleware:

activity

Example to start recording page views using middlware in web.php:

Route::group(['middleware' => ['web', 'activity']], function () {
    Route::get('/', 'WelcomeController@welcome')->name('welcome');
});

This middlware can be enabled/disabled in the configuration settings.

Trait Usage

Events can be recorded directly by using the trait. When using the trait you can customize the event description.

To use the trait:

  1. Include the call in the head of your class file:

        use jeremykenedy\LaravelLogger\App\Http\Traits\ActivityLogger;

  2. Include the trait call in the opening of your class:

        use ActivityLogger;

  3. You can record the activity my calling the traits method:

        ActivityLogger::activity("Logging this activity.");

    Or as bellow to include extended activity details:

        ActivityLogger::activity("Logging this activity.", "Additional activity details.");

Routes

Laravel Activity Dashbaord Routes
  • /activity
  • /activity/cleared
  • /activity/log/{id}
  • /activity/cleared/log/{id}

Custom package routes

If you wish to change the route paths, names or other options you can disable the default routes in your .env file by setting

LARAVEL_LOGGER_DISABLE_ROUTES=true

If you are on an existing install, you will also need update your laravel-logger.php config file to add the config option:

'disableRoutes' => env('LARAVEL_LOGGER_DISABLE_ROUTES', false),

You can then add the routes directly to your application's routes/web.php file, and customise as required.

Route::group(['prefix' => 'activity', 'namespace' => 'jeremykenedy\LaravelLogger\App\Http\Controllers', 'middleware' => ['web', 'auth', 'activity']], function () {

    // Dashboards
    Route::get('/', 'LaravelLoggerController@showAccessLog')->name('activity');
    Route::get('/cleared', ['uses' => 'LaravelLoggerController@showClearedActivityLog'])->name('cleared');

    // Drill Downs
    Route::get('/log/{id}', 'LaravelLoggerController@showAccessLogEntry');
    Route::get('/cleared/log/{id}', 'LaravelLoggerController@showClearedAccessLogEntry');

    // Forms
    Route::delete('/clear-activity', ['uses' => 'LaravelLoggerController@clearActivityLog'])->name('clear-activity');
    Route::delete('/destroy-activity', ['uses' => 'LaravelLoggerController@destroyActivityLog'])->name('destroy-activity');
    Route::post('/restore-log', ['uses' => 'LaravelLoggerController@restoreClearedActivityLog'])->name('restore-activity');
});

Search

adding dynamic search fields (description , user, URL , method and ip address)

.env file

add these configurations to your .env file to control the logging search

LARAVEL_LOGGER_ENABLE_SEARCH=true
// you can customize your search using these options [description,user,method,route,ip]
LARAVEL_LOGGER_SEARCH_FIELDS=description,user,method,route,ip

by default all search fields are enabled when you enable the search with this one line configuration

LARAVEL_LOGGER_SEARCH_ENABLE=true

Screenshots

dashboard drilldown confirm-clear log-cleared-msg cleared-log confirm-restore confirm-destroy success-destroy success-restored cleared-drilldown

File Tree

β”œβ”€β”€ .env.travis
β”œβ”€β”€ .gitignore
β”œβ”€β”€ .travis.yml
β”œβ”€β”€ CODE_OF_CONDUCT.md
β”œβ”€β”€ LICENSE
β”œβ”€β”€ README.md
β”œβ”€β”€ composer.json
└── src
    β”œβ”€β”€ .env.example
    β”œβ”€β”€ LaravelLoggerServiceProvider.php
    β”œβ”€β”€ app
    β”‚Β Β  β”œβ”€β”€ Http
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ Controllers
    β”‚Β Β  β”‚Β Β  β”‚Β Β  └── LaravelLoggerController.php
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ Middleware
    β”‚Β Β  β”‚Β Β  β”‚Β Β  └── LogActivity.php
    β”‚Β Β  β”‚Β Β  └── Traits
    β”‚Β Β  β”‚Β Β      β”œβ”€β”€ ActivityLogger.php
    β”‚Β Β  β”‚Β Β      β”œβ”€β”€ IpAddressDetails.php
    β”‚Β Β  β”‚Β Β      └── UserAgentDetails.php
    β”‚Β Β  β”œβ”€β”€ Listeners
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ LogAuthenticated.php
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ LogAuthenticationAttempt.php
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ LogFailedLogin.php
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ LogLockout.php
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ LogPasswordReset.php
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ LogSuccessfulLogin.php
    β”‚Β Β  β”‚Β Β  └── LogSuccessfulLogout.php
    β”‚Β Β  β”œβ”€β”€ Logic
    β”‚Β Β  β”‚Β Β  └── helpers.php
    β”‚Β Β  └── Models
    β”‚Β Β      └── Activity.php
    β”œβ”€β”€ config
    β”‚Β Β  └── laravel-logger.php
    β”œβ”€β”€ database
    β”‚Β Β  └── migrations
    β”‚Β Β      └── 2017_11_04_103444_create_laravel_logger_activity_table.php
    β”œβ”€β”€ resources
    β”‚Β Β  β”œβ”€β”€ lang
    β”‚Β Β  β”‚Β Β  β”œβ”€β”€ de
    β”‚Β Β  β”‚Β Β  β”‚Β Β  └── laravel-logger.php
    β”‚Β Β  β”‚Β Β  └── en
    β”‚Β Β  β”‚Β Β      └── laravel-logger.php
    β”‚Β Β  └── views
    β”‚Β Β      β”œβ”€β”€ forms
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ clear-activity-log.blade.php
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ delete-activity-log.blade.php
    β”‚Β Β      β”‚Β Β  └── restore-activity-log.blade.php
    β”‚Β Β      β”œβ”€β”€ logger
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ activity-log-cleared.blade.php
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ activity-log-item.blade.php
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ activity-log.blade.php
    β”‚Β Β      β”‚Β Β  └── partials
    β”‚Β Β      β”‚Β Β      └── activity-table.blade.php
    β”‚Β Β      β”œβ”€β”€ modals
    β”‚Β Β      β”‚Β Β  └── confirm-modal.blade.php
    β”‚Β Β      β”œβ”€β”€ partials
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ form-search.blade.php
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ form-status.blade.php
    β”‚Β Β      β”‚Β Β  β”œβ”€β”€ scripts.blade.php
    β”‚Β Β      β”‚Β Β  └── styles.blade.php
    β”‚Β Β      └── scripts
    β”‚Β Β          β”œβ”€β”€ add-title-attribute.blade.php
    β”‚Β Β          β”œβ”€β”€ clickable-row.blade.php
    β”‚Β Β          β”œβ”€β”€ confirm-modal.blade.php
    β”‚Β Β          β”œβ”€β”€ datatables.blade.php
    β”‚Β Β          └── tooltip.blade.php
    └── routes
        └── web.php
  • Tree command can be installed using brew: brew install tree
  • File tree generated using command tree -a -I '.git|node_modules|vendor|storage|tests'

Opening an Issue

Before opening an issue there are a couple of considerations:

  • You are all awesome!
  • Read the instructions and make sure all steps were followed correctly.
  • Check that the issue is not specific to your development environment setup.
  • Provide duplication steps.
  • Attempt to look into the issue, and if you have a solution, make a pull request.
  • Show that you have made an attempt to look into the issue.
  • Check to see if the issue you are reporting is a duplicate of a previous reported issue.
  • Following these instructions show me that you have tried.
  • If you have a questions send me an email to [email protected]
  • Need some help, I can do my best on Slack: https://opensourcehelpgroup.slack.com
  • Please be considerate that this is an open source project that I provide to the community for FREE when opening an issue.

License

Laravel-logger is licensed under the MIT license. Enjoy!

Comments
  • Class name must be a valid object or a string

    Class name must be a valid object or a string

    am get the error Class name must be a valid object or a string when i try to Login, on this line

    `// Validation Instance

        $validator = Validator::make($data, config('laravel-logger.defaultActivityModel')::rules());

    `

    opened by Emmanavimex 8
  • The referer format is invalid

    The referer format is invalid

    [2018-10-01 17:46:26] production.ERROR: Failed to record activity event. Failed Validation: {"referer":["The referer format is invalid."]}
    [2018-10-02 22:00:08] production.ERROR: Failed to record activity event. Failed Validation: {"referer":["The referer format is invalid."]}
    [2018-10-02 22:00:27] production.ERROR: Failed to record activity event. Failed Validation: {"referer":["The referer format is invalid."]}
    [2018-10-02 23:07:16] production.ERROR: Failed to record activity event. Failed Validation: {"referer":["The referer format is invalid."]}
    [2018-10-02 23:10:11] production.ERROR: Failed to record activity event. Failed Validation: {"referer":["The referer format is invalid."]}

    any idea what causes this?

    opened by azorpax 8
  • Class App\Http\Controllers\jeremykenedy\LaravelLogger\App\Http\Controllers\LaravelLoggerController does not exist

    Class App\Http\Controllers\jeremykenedy\LaravelLogger\App\Http\Controllers\LaravelLoggerController does not exist

    Why i have exception like this "Class App\Http\Controllers\jeremykenedy\LaravelLogger\App\Http\Controllers\LaravelLoggerController does not exist" when i want to acces route /activity? @jeremykenedy

    opened by ahph37 7
  • Feature: Allow customisation of routes

    Feature: Allow customisation of routes

    I think this would be a good feature to add.

    I think the best way to do this would be similar to how the base laravel auth routes are registered.

    You would add LaravelLogger::routes() to your routes file for your app, and this would take an array of config options, such as:

    • route prefix
    • route name prefix
    • middleware
    • routes to disable etc

    This would be applied to the routes, which would then be added to the app's router routes. Obviously would have to make it backwards compatible.

    The other way would be to allow you to disable the routes with a config option, and then you could add them yourself to your routes file (using the full controller namespace + name)

    I'll try and get a PR up when I have a chance :)

    This is related to #17

    help wanted Feature Request 
    opened by atymic 7
  • Generating wrong url

    Generating wrong url

    https://github.com/jeremykenedy/laravel-logger/blob/a973d9026b25b10369e2ae51f9e9074098737620/src/resources/views/logger/partials/activity-table.blade.php#L137

    Hi, I am not sure if I'm the only one who encountered this bug or not bug? The URL is generating like this: mywebsite.com/http://mywebsite.com/xxxxx/xxx

    opened by azorpax 7
  • Where is the ipAddress cast defined?

    Where is the ipAddress cast defined?

    I was looking to upgrade to Laravel 8; however, one error that I began receiving was:

    Call to undefined cast [ipAddress] on column [ipAddress] in model [jeremykenedy\LaravelLogger\App\Models\Activity].

    I see that the cast type is ipAddress but I do not see any custom casts. https://laravel.com/docs/7.x/eloquent-mutators#custom-casts does not list that as a valid cast type. I will look a little deeper but figured I would share my experience.

    opened by arborrow 5
  • App/config is not over writing vendor/config

    App/config is not over writing vendor/config

    I was having trouble installing this package until I realized that the app/config file was not taking precedence over the package config file.

    I haven't had a chance to do a deeper discovery yet. I will report back if I find a solution.

    bug 
    opened by illuminate3 5
  • LaravelLoggerController.php on line 12:

    LaravelLoggerController.php on line 12: "App\Http\Controllers\Controller" hardcoded

    Just installed:

    PHP Fatal error: Class 'App\Http\Controllers\Controller' not found in /vendor/jeremykenedy/laravel-logger/src/app/Http/Controllers/LaravelLoggerController.php on line 12

    My application have app:name set.

    Is it possible to override

    Thank you.

    opened by peyobr 5
  • Laravel 9.x support - illuminate/view

    Laravel 9.x support - illuminate/view

    In preparation for the release of Laravel 9, I figured I would create this issue.

    Problem 1 - illuminate/view[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.0.15) does not satisfy that requirement. - illuminate/view[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.0.15) does not satisfy that requirement. - illuminate/view[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.0.15) does not satisfy that requirement. - Root composer.json requires jeremykenedy/laravel-logger ^6.0 -> satisfiable by jeremykenedy/laravel-logger[v6.0.0]. - Conclusion: don't install laravel/framework v9.0.0-beta.2 (conflict analysis result) - Conclusion: don't install laravel/framework v9.0.0-beta.3 (conflict analysis result) - Conclusion: don't install laravel/framework v9.0.0-beta.4 (conflict analysis result) - Conclusion: don't install laravel/framework v9.0.0-beta.1 (conflict analysis result) - jeremykenedy/laravel-logger v6.0.0 requires laravelcollective/html ^5.4|^5.5|^5.6|^5.7|^5.8|^6.0|^7.0|^8.0 -> satisfiable by laravelcollective/html[v6.2.0, v6.2.1, 6.x-dev]. - laravelcollective/html[v6.2.0, ..., 6.x-dev] require illuminate/view ^6.0|^7.0|^8.0 -> satisfiable by illuminate/view[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev]. - Only one of these can be installed: illuminate/view[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev], laravel/framework[v9.0.0-beta.1, ..., 9.x-dev]. laravel/framework replaces illuminate/view and thus cannot coexist with it. - Root composer.json requires laravel/framework ^9.0 -> satisfiable by laravel/framework[v9.0.0-beta.1, ..., 9.x-dev].

    enhancement help wanted 
    opened by arborrow 4
  • Class name must be a valid object or a string

    Class name must be a valid object or a string

    I am using laravel-logger 2.4 with laravel 5.7, but recently i have updated from laravel 5.7 to laravel 8.

    This time i installed laravel-logger 4

    laravel logger is not working and producing error.

    Screenshot_1

    opened by PositiveZahid 4
  • Add support for activity details.

    Add support for activity details.

    Although the Activity model holds a description field, this field is used in index and search. If it holds many detailed information about the activity being logged, it could break index layout and add additional stress upon search.

    To avoid that, a detail field is added. This new, optional field can hold any additional information required to better describe the activity. This is particularly useful to provide a fully functional auditing log as one can now add details for the entire data changed by the activity while keeping description as narrow as possible.

    As the field is optional, the ActivityLogger trait could be used as usual, or include a second parameter with all the desired details to be logged. No additional configuration is required for this to work.

    I'm not a native speaker of any of the supported languages in this package, but I've included translations for them. Fell free to change that as needed.

    I hope this PR find its way to master. Thanks again for the great package, @jeremykenedy.

    opened by denydias 4
  • Allow unauthenticated access to logger activity screens

    Allow unauthenticated access to logger activity screens

    Hello,

    This PR adds an option to the configuration to not have an authenticated user to access activity routes.

    Sometimes it is not appropriate to manage access to this data through an application user, even using a specific role for authorization.

    With this option, it will be possible to choose another mode of protection, I am thinking in particular of access rules in apache, nginx or iis directly.

    opened by dimer47 0
  • Call to undefined function jeremykenedy\LaravelLogger\config_path()

    Call to undefined function jeremykenedy\LaravelLogger\config_path()

    Hello. I followed the steps for lumen configuration but i am reciveing this error when i run: php artisan migrate. Call to undefined function jeremykenedy\LaravelLogger\config_path()

    image

    opened by astritshuli 0
  • URL is not working Properly

    URL is not working Properly

    They've diverted to the dashboard because the log activity URL isn't working. Then they routed me to the dashboard when I hit the activity URL. and When I go to the admin dashboard, it looks like that URL is not working properly It shows if I use the address provided in the documentation.

    opened by abdullahrishi 0
  • Log activity url not working

    Log activity url not working

    Log activity URL not working they have redirected to the dashboard.I m hit the activity URL then they have redirected to the dashboard When I open the admin dashboard.If I do a url given in the documentation, the show does not happen.I am following the ticket right documentation.Admin model and customer model are separate also my admin all route run routes/admin.php file

    image

    image

    image image

    image

    opened by zainawan99 0
  • Update for Laravel 8

    Update for Laravel 8

    You can update this link to get the pagination in separated buttons.

                {!! $activities->links('vendor.pagination.bootstrap-4') !!}

    https://github.com/jeremykenedy/laravel-logger/blob/5d230c17fd9765f856c4c2974a0a89c9bda2d2c4/src/resources/views/logger/partials/activity-table.blade.php#L259

    Also update the pagination to include Query string for the search.

                $activities = $activities->paginate(config('LaravelLogger.loggerPaginationPerPage'))->withQueryString();

    https://github.com/jeremykenedy/laravel-logger/blob/5d230c17fd9765f856c4c2974a0a89c9bda2d2c4/src/App/Http/Controllers/LaravelLoggerController.php#L75

    opened by fzhan 0
Releases(v6.0.0)
Owner
Jeremy Kenedy
Love programming everyday. Practice compassion and kindness to all. Striving to be a better person and father. Love giving back and helping others.
Jeremy Kenedy
GitHub
AcLog is a simple, zero-dependency PHP package to log activity to files

AcLog is a simple, zero-dependency PHP package to log activity to files. This is not meant for logging errors, this is can be used for logging c

null 2 Sep 9, 2022
123Solar is a set of PHP/JS files that make a web logger to monitor your photovoltaic inverter(s)

123Solar is a set of PHP/JS files that make a web logger to monitor your photovoltaic inverter(s). It just need a web server and PHP, no databases are even needed. The philosophy is: To keep it simple, fast, with a low foot print to run on cheap and low powered devices.

null 30 Jan 6, 2023
A simple database logger for all outgoing emails sent by Laravel website.

Laravel Email Database Log A simple database logger for all outgoing emails sent by Laravel website.

Shvets Group 136 Jan 4, 2023
πŸ“‘ Laravel HTTP Logger

Logging incoming HTTP requests

The Dragon Code 28 Nov 29, 2022
Simple PHP Logger. Composer package

Basic PHP Logger ?? Simple logger. Composer package.

null 1 Jan 28, 2022
Test Doubles for the PSR-3 Logger Interface

PSR Log Test Doubles Test Doubles for the PSR-3 Logger Interface Motivation In PHP world, most people create Test Doubles via PHPUnits mocking framewo

Jeroen De Dauw 2 Oct 7, 2022
temperature-pi: a simple Raspberry Pi based temperature logger using a DS18B20 1-Wire digital temperature sensor, & a local sqlite database

temperature-pi temperature-pi is a simple Raspberry Pi based temperature logger using a DS18B20 1-Wire digital temperature sensor, & a local sqlite da

Ronan Guilloux 23 Dec 27, 2020
Allows you to process logs using any PSR-3 compatible logger such as Monolog

Yii 2 PSR Log Target Allows you to process logs using any PSR-3 compatible logger such as Monolog

Alexander Makarov 67 Dec 14, 2022
ChromePhp - a PHP library for the Chrome Logger Google Chrome extension

ChromePhp - a PHP library for the Chrome Logger Google Chrome extension

Craig Campbell 1.4k Dec 30, 2022
Robust, composite logger with filtering, formatting, and PSR-3 support

laminas-log ???? Русским Π³Ρ€Π°ΠΆΠ΄Π°Π½Π°ΠΌ ΠœΡ‹, участники Laminas, Ρ€ΠΎΠ΄ΠΈΠ»ΠΈΡΡŒ ΠΈ ΠΆΠΈΠ²Π΅ΠΌ Π² Ρ€Π°Π·Π½Ρ‹Ρ… странах. Π£ ΠΌΠ½ΠΎΠ³ΠΈΡ… ΠΈΠ· нас Π΅ΡΡ‚ΡŒ Π΄Ρ€ΡƒΠ·ΡŒΡ, родствСнники ΠΈ ΠΊΠΎΠ»Π»Π΅Π³ΠΈ ΠΊΠ°ΠΊ Π²

Laminas Project 27 Nov 24, 2022
This package is for centralized logging of multiple Laravel application into one connection.

Laralogs This package is for centralized logging of multiple Laravel application into one connection. Installation You can install the package via com

Remon 4 Apr 26, 2022
Log Laravel application request and response with a unique ID for easy debugging

Flexible and extendable logging of Laravel application request and responses Zero configuration logging of Requests and Responses to database or custo

Bilfeldt 37 Nov 6, 2022
Keep your laravel logs small and tidy.

Logs can get quite out of hand. This package helps save server space and keep your Laravel log files small.

Accent Interactive 73 Nov 14, 2022
Sends your logs to files, sockets, inboxes, databases and various web services

Monolog - Logging for PHP Monolog sends your logs to files, sockets, inboxes, databases and various web services. See the complete list of handlers be

Jordi Boggiano 20.1k Jan 8, 2023
Clear all your logs in [linux/windows] servers πŸ›‘οΈ

Log-killer Log Killer is tool for [Linux/Windows] Servers This tool will delete all your logs just download the tool and run it on the server if your

Rizer 281 Nov 24, 2022
Sends your logs to files, sockets, inboxes, databases and various web services

Monolog - Logging for PHP ⚠ This is the documentation for Monolog 3.x, if you are using older releases see the documentation for Monolog 2.x or Monolo

Jordi Boggiano 20.1k Jan 7, 2023
Small package that can helps in debugging with API logs for Laravel Project.

Rest APIs Logger This is a small package that can helps in debugging with API logs. Installation Install the package via composer composer require tfs

Sunny Mahajan 7 Aug 31, 2022
A simple and beautiful laravel log reader

Laravel Log Reader A simple and beautiful laravel log reader Documentation Get full documentation of Laravel Log Reader Other Packages Laravel H - A h

Md.Harun-Ur-Rashid 356 Dec 30, 2022
Small laravel package for viewing api logs which can be used in debugging.

This is a small package that can helps in debugging api logs. It can log request method, url, duration, request payload, which models are retrieved, controller and method.

awt 334 Jan 6, 2023