Sem Conv Laravel Package

Product Decisions This Supports

• Standardizing telemetry data across services to ensure compatibility with OpenTelemetry-compatible observability tools (e.g., Jaeger, Prometheus, Datadog)
• Eliminating manual string management for attribute keys/values, reducing inconsistencies and bugs in instrumentation code
• Enabling cross-language observability consistency when integrating PHP services with other OpenTelemetry-supported ecosystems (e.g., Java, Python)
• Supporting vendor-neutral observability strategy by adopting CNCF-standardized conventions instead of proprietary solutions
• Accelerating onboarding for new engineers by providing pre-defined, documented constants for common telemetry scenarios (HTTP, database, error handling)

When to Consider This Package

• Adopt when building or enhancing OpenTelemetry instrumentation in PHP applications requiring standardized attribute naming
• Essential for teams with distributed systems where consistent telemetry data is critical for cross-service debugging and analytics
• Use when needing stable, production-ready semantic conventions for tracing/metrics (e.g., http.method, db.system)
• Avoid if your observability stack doesn’t use OpenTelemetry (e.g., legacy proprietary tools with incompatible data models)
• Not applicable for projects needing custom semantic conventions outside the OpenTelemetry specification (though such cases are rare and generally discouraged)

How to Pitch It (Stakeholders)

For executives: "This package eliminates manual string management for telemetry attributes, reducing debugging time and preventing costly inconsistencies across services. It ensures seamless compatibility with industry-standard observability tools like Datadog and Prometheus, eliminating vendor lock-in and accelerating time-to-insight. With zero runtime overhead and minimal integration cost, it’s a strategic investment in observability maturity that directly supports business-critical monitoring needs."

For engineering: "Provides type-safe, auto-complete-friendly constants for all OpenTelemetry semantic conventions—preventing typos and ensuring compliance out-of-the-box. Works seamlessly with existing OpenTelemetry SDKs, with versioned stability matching spec releases. No configuration needed: just install and use the constants for trace attributes, metrics, and error handling. Future-proofs your instrumentation as standards evolve without manual maintenance."