Laravel structured logging and queue analytics

Test the integration

Send and verify events with Laravel structured logging and queue analytics

Use Laravel structured logging and queue analytics where your app knows the final result. Collect only the fields you need, then verify a test event before building charts.

1
Choose the outcome
Laravel API reliability
2
Define the contract
route_name or job_name, status, and duration_ms
3
Log the final result
Use route names rather than raw URLs and never send request input wholesale.
4
Check the stored event
Exercise a known fixture, then inspect job_completed for one correctly typed terminal row.

Before you start

A server-side TELEMETRY_API_KEY
Laravel HTTP client timeouts configured
Named routes and queue jobs

Delivery setup

Install and initialize server-side

Use Laravel's shared HTTP client or PHP cURL with a server-side key plus explicit connection and request timeouts. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

1Create one reusable server-side client. Set its timeout and retry limit.
2Log an event when the operation succeeds, fails, retries, or times out.
3Send test events with known results and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

laravel

Laravel structured logging and queue analytics event

php

use Illuminate\Support\Facades\Http;

// Existing job work has completed; $job and numeric $durationMs come from your worker.
try {
    $response = Http::withHeaders([
        'Authorization' => config('services.telemetry.key'),
    ])
        ->connectTimeout(1)
        ->timeout(2)
        ->post('https://api.telemetry.sh/log', [
            'table' => 'job_completed',
            'data' => [
                'job_name' => get_class($job),
                'queue_name' => $job->queue,
                'status' => 'success',
                'attempt' => $job->attempts(),
                'duration_ms' => $durationMs,
                'release' => config('app.release'),
            ],
        ]);

    if (!$response->successful()) {
        error_log('Telemetry delivery failed (non-2xx response).');
    }
} catch (\Throwable $error) {
    error_log('Telemetry delivery failed (transport or configuration error).');
}
// Continue with the original job result; do not retry the job because this send failed.

Event schema

route_name or job_name, status, and duration_ms

attempt, queue_name, error_type, and release

request_id plus safe account identifiers

Check your setup

Checkpoint 1

Use route names rather than raw URLs and never send request input wholesale.

Checkpoint 2

Record queue attempts with the logical job ID preserved across retries.

Checkpoint 3

Catch telemetry delivery failures without replacing a completed application response.

Checkpoint 4

This example runs after a successful queue attempt. Keep the original job result and failure handling; an attempt event does not prove downstream delivery or logical job completion.

Checkpoint 5

Use bounded connection and request timeouts, inspect non-2xx responses, and report delivery failure locally without logging the key, response body, or exception text. This example does not retry or guarantee delivery.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

laravel-verification

Laravel structured logging and queue analytics verification query

sql

SELECT *
FROM job_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

PHP HTTP guide Data types and nullability Laravel HTTP client Laravel logging Laravel queues

Where to log

Keep the outcome event small and recoverable

This pattern provides

Record the outcome as an event you can query with SQL.
Stable fields for dashboards, alerts, and cross-event correlation.
Test events for checking success, failure, retries, and timeouts.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Revenue operations9 fields