@luckys_luis/nuxt-laravelize-observability-queue

Espanol | English

Semantic queue tracing and metrics bridge

Install

pnpm add @luckys_luis/nuxt-laravelize-observability-queue

Package-specific usage

Instrument selected queue jobs

Install the bridge with explicit job and queue allowlists. It propagates traceparent only by default, creates consumer spans, and maps queue releases, failures, and completions to bounded metrics.

import { installQueueObservability } from '@luckys_luis/nuxt-laravelize-observability-queue'

installQueueObservability(admissionContributors, runner, observability, {
  jobs: ['billing.invoice.process.v1'],
  queues: ['billing'],
  trustTraceContext: false,
})

Public entrypoints

Use only these public entrypoints. Paths not listed here are internals and may change without notice.

| Entrypoint | Use | |---|---| | package root | Public entrypoint for this package. |

Observability and OpenTelemetry

@luckys_luis/nuxt-laravelize-observability is included in the preset as a zero-cost no-op foundation. Its runtime contracts do not depend on H3. Application providers may override observabilityToken; register the override after module providers. @luckys_luis/nuxt-laravelize-observability-otel and @luckys_luis/nuxt-laravelize-observability-queue remain opt-in. The OTel adapter uses only @opentelemetry/api at runtime and never installs globals, an SDK, or exporters.

Incoming HTTP trace trust is disabled by default. Baggage is always discarded. Built-in integrations never capture payloads, bodies, raw URLs/query, secrets, arbitrary headers, IPs, error messages/stacks, or actor/tenant/workflow/message/job IDs as metric labels. IDs are not captured by default. Metric dimensions are fixed; job and queue names require explicit allowlists and otherwise become other.

Queue consumers also start root spans by default. Set trustTraceContext: true only for trusted queue carriers when remote parenting is intended. Queue metadata persists only traceparent; tracestate requires propagateTracestate: true, and baggage is never persisted. Terminal job failure callbacks are not process spans. When execution-context propagation is installed too, observability replaces only trace/span correlation and preserves the worker execution identity and provenance.

Nitro lifecycle hooks reliably start and finish request spans. The request-scoped observability token binds Laravelize services, useObservability(event), observe(), and queue producer injection to that server span. This is not global handler ALS: arbitrary external auto-instrumentation that bypasses the token is not parented by this mechanism.

Compatibility and boundaries

Respect the at-least-once delivery, durability, authorization, tenant isolation, and secret-handling warnings in the reference section. Examples do not replace server-side authentication, authorization, or validation.

The shared API and security reference lives in the module guide. This page summarizes this package's contract and keeps copy-pasteable examples.

Related packages

@luckys_luis/nuxt-laravelize-observability, @luckys_luis/nuxt-laravelize-queue, @luckys_luis/nuxt-laravelize-execution-context-queue.