Statamic Telemetry Laravel Package

Product Decisions This Supports

• Instrumentation for Statamic Stache warm operations, emitting statamic.stache.warm duration metrics through cboxdk/laravel-telemetry. This supports visibility into cache warm latency during content publishing, deploys, and cache rebuilds.
• v3.1.0 adds a content audit log: every content change emits one statamic.content.change event with the item, action, changed field handles (not values), actor, source, and edit link. This supports compliance/audit readiness, editorial accountability, content governance, and incident forensics without building custom audit plumbing.
• Audit coverage spans entries, terms, assets, collections, taxonomies, blueprints, fieldsets, navigations and trees, global sets and variables, users, roles, groups, forms, sites, and revisions. It records actions such as created, updated, published, unpublished, deleted, uploaded, replaced, and revision states, with source context (cp, api, web, console + command).
• Privacy and data-governance decisions are supported by design: the audit log records field handles but never values, records user.id and optionally user.name (never email), and can be switched off with STATAMIC_TELEMETRY_CONTENT_AUDIT=false. Teams must still decide retention, access, and whether actor names should be enabled.
• Performance and reliability decisions remain supported: setting SLOs/alert thresholds for Stache warm time, capacity planning, incident triage, and evaluating whether cache warm latency is degrading user or editorial experience.
• Build vs buy: adopt this package instead of maintaining custom Statamic cache-warm instrumentation and custom content-audit logging, provided the team can absorb the telemetry dependency and metric migration.
• v3.1.0 improves Stache warm histogram accuracy: statamic.stache.warm_duration now has its own buckets (0.05 s–300 s) instead of telemetry.default_buckets. Hosts with pre-3.0 config carrying millisecond buckets should see meaningful percentiles again; expect a transient first window as old bucket counts are read against new bounds.
• v3.1.0 changes statamic.content.change span detail: statamic.content.action now reflects what the save did (created, updated, etc.) rather than the counter’s label. The statamic.content.changes counter is unchanged, so dashboards and alerts on the counter keep working; trace queries using the old span attribute need review.
• v3.0.0 remains a product-relevant breaking change for anyone coming from 2.x: statamic.stache.warm records seconds instead of milliseconds. Dashboards, alerts, and recording rules must divide thresholds by 1000. There is no runtime warning because the smaller value is still a valid duration.
• Roadmap implication: approve v3.1.0 as a minor upgrade with observability and data-governance review: validate audit-log scope/retention, confirm laravel-telemetry-ui 3.1 for the CP audit view, audit statamic.content.action span consumers, and confirm Stache warm dashboards survive the bucket change.

When to Consider This Package

• Consider it when the product runs Statamic and needs either Stache warm latency visibility or a content-change audit trail for editorial governance, compliance, or incident investigation, and the team already uses or is ready to adopt cboxdk/laravel-telemetry ^3.0.
• It is a good fit when standardized duration metrics, vendor-supported audit events, consistent semantic conventions, and a built-in CP audit view are more valuable than bespoke metrics or audit code.
• The audit log is compelling when stakeholders need to answer “who changed what, where, and how” across content, users, sites, forms, and configuration without storing field values or email addresses.
• Adopt v3.1.0 if you can review audit settings (STATAMIC_TELEMETRY_CONTENT_AUDIT, audit.actor_name), update any trace queries on statamic.content.action, and accept the transient Stache warm histogram window after deploy.
• If upgrading from 2.x, adopt v3.0.0+ only with a full observability migration: update every consumer of statamic.stache.warm at the same time, including dashboards, alerts, anomaly detection, recording rules, and capacity models.
• Look elsewhere or defer if the application still emits 2.x telemetry, is pinned to cboxdk/laravel-telemetry below ^3.0, cannot migrate millisecond-based thresholds, or needs a mixed-version compatibility window. v3.0.0+ will not resolve alongside 2.x emitters.
• Look elsewhere if the product does not use Statamic/Stache warm operations or content workflows, has no telemetry backend, or needs audit records that include field values, email addresses, or immutable/WORM-style retention that this package does not provide.
• Also defer if you need the audit UI and cannot run laravel-telemetry-ui 3.1; the events still emit, but the Statamic → Content listing depends on the newer UI.

How to Pitch It (Stakeholders)

• Executives: This package now gives us two capabilities: standardized visibility into Statamic cache warm latency and a built-in content audit trail for editorial accountability and compliance. v3.1.0 is a minor upgrade that adds audit records without breaking the existing change counter, but it changes some trace detail and Stache warm histogram buckets. Approve with a short review of audit retention, access, and dashboard validation rather than a blind upgrade.
• Engineering: Upgrade to cboxdk/laravel-telemetry ^3.0 and this package v3.1.0 together. Decide audit settings: whether STATAMIC_TELEMETRY_CONTENT_AUDIT is enabled, whether audit.actor_name is on, and what retention applies. Review trace queries that use statamic.content.action, because the span attribute now carries the save action rather than the counter label; the statamic.content.changes counter remains compatible. Validate the new statamic.stache.warm_duration buckets in staging and expect a transient first window as old bucket counts meet new bounds. If coming from 2.x, still treat the seconds-vs-milliseconds change as a release gate.
• Product/Operations: Use the Statamic → Content audit view in laravel-telemetry-ui 3.1 to support editorial questions and investigations. Update runbooks and alert ownership for the Stache warm bucket change and the restored Telemetry CP nav item. If latency SLOs or audit obligations depend on this package, include dashboard validation, retention review, and metric-unit communication in the release checklist.