Download the PHP package amjadiqbal/laravel-logpulse without Composer

On this page you can find all versions of the php package amjadiqbal/laravel-logpulse. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package laravel-logpulse

# ๐Ÿซ€ Laravel LogPulse **Proactive Log Health Monitoring & Intelligent Alerting for Laravel** [![Latest Version on Packagist](https://img.shields.io/packagist/v/amjadiqbal/laravel-logpulse.svg?style=flat-square)](https://packagist.org/packages/amjadiqbal/laravel-logpulse) [![Total Downloads](https://img.shields.io/packagist/dt/amjadiqbal/laravel-logpulse.svg?style=flat-square)](https://packagist.org/packages/amjadiqbal/laravel-logpulse) [![License](https://img.shields.io/packagist/l/amjadiqbal/laravel-logpulse.svg?style=flat-square)](LICENSE.md) [![Tests](https://img.shields.io/github/actions/workflow/status/AmjadIqbal/laravel-logpulse/run-tests.yml?branch=main&label=tests&style=flat-square)](https://github.com/AmjadIqbal/laravel-logpulse/actions) [![PHPStan](https://img.shields.io/badge/PHPStan-level%205-brightgreen.svg?style=flat-square)](https://phpstan.org/)

Installation โ€ข Configuration โ€ข Usage โ€ข How it works


๐Ÿค” The Problem

Your production app is silently failing. A webhook endpoint returns 500 errors 200 times per hour. Your disk fills with logs. Your database connections exhaust. And you don't know until a customer complains.

Traditional log viewers are reactive โ€” you only see problems when you manually check.


โœจ The Solution

LogPulse acts as a heartbeat monitor for your Laravel application. It listens to your logging engine in real-time, detects abnormal error patterns, and alerts you before your customers notice.


๐Ÿš€ Features


๐Ÿ“ฆ Installation

Guided setup (recommended):

Or non-interactively (CI/scripted installs):

Publish the config manually instead, if you'd rather configure by hand:

โš™๏ธ Configuration

Everything lives in config/logpulse.php, driven by environment variables:

๐Ÿ–ฅ๏ธ Usage

LogPulse listens to Laravel's own MessageLogged event automatically once installed โ€” no extra wiring needed for Log::error()/Log::critical() calls to start feeding the dashboard and alert pipeline.

๐Ÿ›ก๏ธ How alerting works

  1. Every logged error is aggregated by (exception_class, route) into a logpulse_events row, with an occurrence_count rather than one row per occurrence.
  2. FrequencyAnalyzer checks the rolling count against your configured thresholds.
  3. PatternMatcher looks for higher-level patterns across recent events โ€” cascade failures (many different exceptions in a burst), retry storms (exponentially shortening intervals), dependency outages, resource exhaustion, and degraded performance.
  4. A triggered alert goes out over your configured channels โ€” unless the circuit breaker for that channel is open, which caps how many alerts can fire per minute so a real incident doesn't also turn into an alert flood.

๐Ÿ“„ License

MIT License. See LICENSE.md.

Changelog

See CHANGELOG.md.

Author

Amjad Iqbal โ€” amjad.com.pk ยท GitHub


All versions of laravel-logpulse with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0|^8.1|^8.2|^8.3
laravel/framework Version ^9.0|^10.0|^11.0
laravel/prompts Version ^0.1.15
guzzlehttp/guzzle Version ^7.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package amjadiqbal/laravel-logpulse contains the following files

Loading the files please wait ...