Download the PHP package vmorozov/laravel-prometheus without Composer

Prometheus client for laravel framework

A Laravel package for integrating Prometheus metrics collection into your Laravel application.
This package makes it easy to collect and expose metrics for monitoring your application's performance and behavior.

Installation

1. Install the package via composer:

2. Publish vendor files:

Upgrading version

1. Update the package version in composer.json

2. Run

3. Run command to update configs:

4. Run clear stored metrics:

Usage

This package provides default metrics that allow you to monitor response times (divided into buckets and percentiles) and request counts.
It also allows you to create custom metrics and collectors for your specific needs.

To see the collected metrics, go to the /metrics endpoint of your application.
This endpoint returns metrics in the Prometheus exposition format, which can be scraped by a Prometheus server.

You can clear stored metrics using the built-in prometheus:clear_stored_metrics command: ``

Configuration

The package can be configured using the laravel-prometheus.php configuration file.
This file is published to your application's config directory when you run the vendor:publish command.

Key configuration options include:

• namespace: Prefix for all metrics (default: your APP_NAME env value)
• storage_type: How metrics data is stored (redis, in_memory, apcu)
• route_url: URL path for the metrics endpoint (default: /metrics)
• default_metrics_enabled: Whether default metrics are enabled (they are enabled by default)
• on_demand_metric_collectors: Collectors that run only when the metrics endpoint is accessed

For detailed configuration information, see the Configuration Documentation.

Default Metrics

The package includes two default metrics:

1. Request Duration Histogram: Measures the duration of HTTP requests.
2. Queue Size Gauge: Measures the size of Laravel queues (you have to configure which connections and queues to monitor).

For more information about the default metrics, see the Default Metrics Documentation.

Custom Metrics

You can create custom metrics to monitor specific aspects of your application. The package supports three types of metrics:

1. Counter: A cumulative metric that only increases (requests_processed, users_registered, etc.)
2. Gauge: A metric that can go up and down and represents current state of something (example: queue_size, cpu_load, etc.)
3. Histogram: A metric that samples observations and counts them in buckets (when you need to have quantiles of your metric values)

For information on creating and using custom metrics, see the Custom Metrics Documentation.

On-Demand Metrics Collectors

On-Demand Metrics Collectors are classes that collect metrics only when the metrics endpoint is accessed.
This is useful for metrics that are expensive to collect or that don't need to be updated on every request.

For information on creating and using custom On-Demand Metrics Collectors, see the On-Demand Metrics Collectors Documentation.

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Vladimir Morozov
• All Contributors

License

The MIT License (MIT). Please see License File for more information.