Download the PHP package kirschbaum-development/monitor without Composer

On this page you can find all versions of the php package kirschbaum-development/monitor. 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 monitor

Kirschbaum Monitor

Laravel Supported Versions Latest Version on Packagist Application Testing Static Analysis Code Style

Monitor gives a Laravel application control points: the operations where a failure matters, declared in code as a contract. A control point says what it is called, which domain it belongs to, which failures it expects and what to return instead, which policies bound it, which limits it should stay within, and who is told when something it did not expect gets out. Every run ends in one outcome, succeeded, recovered, escalated or refused, and every transition is written as a record with the same fields.

Because the declaration is data, the rest of the package can read it: monitor:points lists every point and checks the declarations in CI, Monitor::fake() asserts on outcomes by name, an optional store keeps outcomes queryable, and an MCP server lets an agent ask the application what its control points are and what happened at them. The same convention ships as guidelines for Laravel Boost, so an agent adding a critical operation is told once, by the package.

The declaration says what the operation tolerates, what it tries again, when it stops calling the gateway, what counts as success, and who is paged. It produces one log record per transition with point, domain, status, run_id and trace_id as fields.

Quick Start

Add the trace middleware so every request, and every job it dispatches, shares one trace id:

Declare a critical operation as a class:

Test it by name:

And prove in CI that every critical operation is declared and complete:

How It Works

A control point has a name (payment.charge), a domain derived from its class namespace, and a contract. The contract declares risks with their corrections (recover(): the handler's return value is the result), policies (Retry, Transaction, Breaker, composed in a fixed order), limits (within() records a slow run without failing it, attempts() caps retries, ensure() fails a run whose result is wrong), and an escalation for anything no correction covers.

Every run ends in exactly one outcome: succeeded, recovered, escalated, or refused by an open breaker. The outcome is what attempt() returns, what the events carry, what the fake records, what the log receives as one record per transition, and what the optional store keeps in a table.

Control points nest. A child carries its parent's run id, a child's escalation reaches the parent's corrections, and retries never compose across the stack. The trace id and the current point ride on Laravel's Context, so they reach queued jobs and every log line the application writes.

An inventory reads the codebase without running it: monitor:points lists every point with its contract, --check fails the build when a point has no escalation, a name is duplicated, or a class in a critical namespace is not a control point. The same rules are available as a Pest expectation and a PHPStan rule.

What It Covers

Documentation

The full documentation lives in docs/:

Page What it covers
Getting Started Installation, the inline form, the Outcome, a first class-form point, the trace middleware.
Control Points Naming, domains, the builder, the class form, nesting, Laravel Context.
Risks and Corrections recover() semantics, the catch-all, escalate(), the risks Monitor raises.
Policies and Limits Retry, Transaction, Breaker, pipeline order, the three limits, profiles.
Records The record schema, levels, redaction, NDJSON, Monitor::log(), events.
Tracing Trace ids, the middleware, Http::traced(), jobs, console.
Jobs Dispatching a point as a job, Horizon tags, WaitForBreaker, what a job inherits.
Breakers The state machine, the standalone API, the route middleware.
Store Enabling the outcome store, what is written and when, monitor:outcomes, pruning.
Inventory monitor:points, every rule, --check in CI, monitor:explain, make:control-point.
Testing Monitor::fake() and its assertions, the Pest expectations, the PHPStan rule, and the package's own tests.
Agents The Boost guideline and skill, the MCP server, its tools, resources and prompt.
Configuration Every key in config/monitor.php with its type, default and environment variable.
Extending Custom policies, escalations, inventory rules, event listeners.
Upgrading Every 0.1 surface and its 1.0 replacement.

Requirements

Testing

Changelog

See CHANGELOG.md for what changed in each release.

License

The MIT License (MIT). See LICENSE.md.


All versions of monitor with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3|^8.4|^8.5
illuminate/support Version ^12.0|^13.0
monolog/monolog Version ^3.0
symfony/finder Version ^7.0|^8.0
kirschbaum-development/redactor Version ^1.0
nikic/php-parser Version ^5.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 kirschbaum-development/monitor contains the following files

Loading the files please wait ...