Easily track metrics from Laravel events, or on your own

1.7 2023-03-23 16:57 UTC

This package is auto-updated.

Last update: 2023-03-23 16:58:34 UTC


Latest Version on Packagist Total Downloads Build Status Software License

This package makes it incredibly easy to ship app metrics to backends such as InfluxDB or CloudWatch.

There are two major components: a facade that lets you create metrics on your own, and an event listener to automatically send metrics for Laravel events.


You know the drill...

composer require stechstudio/laravel-metrics

Backend configuration


Add the following to your .env file:


# Only if you are not using the default 8086

# If you want to send metrics over UDP instead of TCP


First make sure you have AWS itself properly setup. That means composer install aws/aws-sdk-php and making sure you have your AWS credentials configured.

From there, you simply need to add:



NullDriver (for development)

If you need to disable metrics just set the backend to null:


This null driver will simply discard any metrics.

Sending an individual metric

You can create metric by using the facade like this:

        'source' => 'email-campaign',
        'user' => 54

The only required attribute is the name, everything else is optional.

Driver mapping

This is how we are mapping metric attributes in our backends.

Metric attribute InfluxDB CloudWatch
name measurement MetricName
value fields[value] Value
unit ignored Unit
resolution ignored StorageResolution
tags tags Dimensions
extra fields ignored
timestamp timestamp Timestamp

See the CloudWatch docs and InfluxDB docs for more information on their respective data formats. Note we only do minimal validation, you are expected to know what data types and formats your backend supports for a given metric attribute.

Sending metrics from Laravel events

The main motivation for this library was to send metrics automatically when certain events occur in a Laravel application. So this is where things really get fun!

Let's say you have a simple Laravel event called OrderReceived:

class OrderReceived {
    protected $order;
    public function __construct($order)
        $this->order = $order;

The first step is to implement an interface:

use STS\Metrics\Contracts\ShouldReportMetric;

class OrderReceived implements ShouldReportMetric {

This will tell the global event listener to send a metric for this event.

There are two different ways you can then provide the metric details.

1. Use the ProvidesMetric trait

You can also include a trait that helps with building this metric:

use STS\Metrics\Contracts\ShouldReportMetric;
use STS\Metrics\Traits\ProvidesMetric;

class OrderReceived implements ShouldReportMetric {
    use ProvidesMetric;

In this case, the trait will build a metric called order_received (taken from the class name) with a value of 1.

Customizing event metric data

If you decide to use the trait, you likely will want to customize the event metric data.

You can provide metric data with class attributes:

class OrderReceived implements ShouldReportMetric {
    use ProvidesMetric;
    protected $metricName = "new_order";
    protected $metricTags = ["category" => "revenue"];

Or if some of your metric data is dynamic you can use getter methods:

public function getMetricValue()
    return $this->order->total;

You can provide any of our metric attributes using these class attributes or getter methods.

2. Create the metric yourself

Depending on how much detail you need to provide for your metric, it may be simpler to just build it yourself. In this case you can ditch the trait and simply provide a public createMetric function that returns a new Metric instance:

use STS\Metrics\Contracts\ShouldReportMetric;
use STS\Metrics\Metric;

class OrderReceived implements ShouldReportMetric {
    protected $order;
    public function __construct($order)
        $this->order = $order;
    public function createMetric()
        return (new Metric('order_received'))