Laravel Structured Logging and Queue Analytics

Implementation evidence

Laravel Structured Logging and Queue Analytics: from boundary to verified row

Use Laravel Structured Logging and Queue Analytics at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

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

Before you start

Prerequisites and boundaries

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.

1Prepare one reusable server-side delivery client with bounded network behavior.
2Add the outcome event at the success, failure, retry, or timeout boundary.
3Send controlled fixtures 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

Http::withToken(config('services.telemetry.key'))
    ->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'),
        ],
    ]);

Event contract

route_name or job_name, status, and duration_ms

attempt, queue_name, error_type, and release

request_id plus safe account identifiers

Implementation checkpoints

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.

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 logging Laravel queues

Production boundary

Keep the outcome event small and recoverable

This pattern provides

A bounded, SQL-ready outcome beside the upstream workflow.
Stable fields for dashboards, alerts, and cross-event correlation.
A fixture-driven path for validating success, failure, retry, and timeout behavior.

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

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

Revenue operations9 fields