Download the PHP package aurorawebsoftware/logiaudit without Composer

LogiAudit

LogiAudit is a Laravel package designed for structured logging with support for job-based log storage, pruning, and customizable log levels.

Features

• Queue-Based Logging: Logs are stored asynchronously using Laravel jobs.
• Contextual Logging: Supports logging with model associations, trace IDs, and additional metadata.
• Automatic Pruning: Logs marked as deletable can be automatically removed.
• Monolog Integration: Works seamlessly with Laravel's logging system.
• IP Tracking: Logs IP addresses for traceability.
• Configurable Cleanup: Define log retention periods.

Installation

You can install the package via Composer:

Running Migrations

After installation, run the migration command to create the necessary database table:

Log Usage

Logging Events

You can log messages using the provided addLog helper function:

addLog Helper Function Details

The addLog function allows for flexible logging with optional parameters:

• level (string, required): Log level (e.g., info, error, warning).
• message (string, required): The log message.
• options (array, optional): Additional context for the log entry.
  • model_id (int, nullable): The ID of the related model (if applicable).
  • model_type (string, nullable): The model's class name.
  • trace_id (string, nullable): A unique identifier for tracing logs across multiple services.
  • context (array, nullable): Any extra contextual data.
  • ip_address (string, nullable): The IP address of the request.
  • deletable (bool, default: true): Determines if the log can be pruned.
  • delete_after_days (int, nullable): Number of days before the log should be automatically deleted (if deletable is true).

Using LogiAudit with Laravel's Logging System

You can also log messages using Laravel's built-in logging channels:

To configure Laravel to use this handler, update config/logging.php:

Running the Log Pruning Command

To remove logs marked as deletable, run the following command:

Alternatively, you can schedule this command in your app/Console/Kernel.php:

History Usage

History Log is simple to use. When you call HistoryableTrait into your model classes whose history you want to monitor, History Log will start to keep history for your model.

If you want to exclude some columns from this, add this variable to your model class globally and write the column names as an array.

If you don't want to keep history in some model events, add the following variable. Currently, this version only keeps the history of create, update and delete events.

Running the History Pruning Command

To delete old history records based on their created_at timestamp, you can run the following Artisan command:

Replace {days} with the number of days you want to retain. For example, to delete all history records older than 30 days:

Running the Queue Worker

Since logs and history are queued using onQueue('logiaudit'), you need to run a dedicated queue worker:

To run the queue worker in the background and ensure it stays active, consider using supervisor or systemd.

License

The LogiAudit package is open-sourced software licensed under the MIT License.