Weave Code
Sem Conv Laravel Package
open-telemetry/sem-conv
PHP constants for OpenTelemetry semantic conventions, generated from official releases. Provides stable attribute and metric names plus incubating/experimental ones, so instrumentation code can reference standard keys without hardcoding strings.
Semantic conventions for OpenTelemetry PHP.
Frequently asked questions about Sem Conv
- What is open-telemetry/sem-conv used for in Laravel?
- It supplies generated PHP constants for OpenTelemetry semantic conventions, so Laravel instrumentation can reference stable attribute and metric names instead of hard-coded strings. It contains no service provider, config, middleware, or runtime logic; it is just a constants dependency used by OpenTelemetry SDK instrumentation.
- How do I install open-telemetry/sem-conv in a Laravel app?
- Run composer require open-telemetry/sem-conv for greenfield adoption, then reference the generated constants in your instrumentation code. For existing apps, do not treat a routine composer update as safe: inspect the resolved version and pin exactly until you have audited removed and renamed attributes.
- Does open-telemetry/sem-conv support Laravel 10 and PHP 8.0?
- The sem-conv package itself is framework-agnostic and does not declare Laravel version support. Laravel 10 and PHP 8.0 compatibility depend on the open-telemetry/sdk version you install alongside it, so verify that SDK's Composer constraints before upgrading.
- Is open-telemetry/sem-conv 1.44.0 a breaking change from 1.38.0?
- Yes. The assessment treats 1.44.0 as a breaking upgrade from 1.38.0 because it adopts semantic convention schemas 1.39 through 1.44 in one release, including removals, renames, and incubating attribute migration. The 1.x version line does not guarantee backward compatibility for deprecated conventions.
- Why did my Laravel app fail with undefined constant after composer update?
- The package removes deprecated semantic convention attributes immediately after deprecation and gives no backwards compatibility guarantee. A jump from 1.38.0 to 1.44.0 can therefore leave code referencing constants or classes that no longer exist, producing undefined constant or class-not-found errors at runtime. Audit all instrumentation references and run tests before deploying.
- What is the difference between stable and incubating semantic conventions in sem-conv?
- Stable conventions under the Attributes and Metrics namespaces are considered safe for production use. Incubating conventions include both stable and experimental elements and are explicitly less stable; the 1.44.0 changelog calls out incubating attribute migration, making that namespace the highest-risk area for breakage.
- How should I pin open-telemetry/sem-conv in composer.json?
- For services that have not completed an attribute audit, replace caret constraints such as ^1.38.0 with an exact pin like 1.38.0. A caret constraint can silently resolve to 1.44.0 on the next composer update, turning a routine refresh into an unannounced breaking change. After auditing and testing, pin the chosen upgraded version exactly as well.
- Will upgrading sem-conv break dashboards or alerts even if there is no code error?
- Yes. Renamed attributes do not always throw an error; spans can silently start emitting new attribute keys while dashboards, alerts, and SLO queries still filter on the old names. Treat telemetry-level breakage as a production risk and diff your emitted span and metric attributes, not just your PHP code.
- Does sem-conv 1.44.0 require a matching open-telemetry/sdk version?
- The sem-conv version tracks an upstream semantic-conventions release, and the assessment explicitly flags whether 1.44.0 requires a matching open-telemetry/sdk 1.44.x bump as an open question. Do not assume compatibility; check the SDK's Composer constraints and test PHP 8.0 and Laravel 10 support before upgrading.
- What is the safest alternative to hard-coded OpenTelemetry attribute strings in Laravel?
- Use the package's stable constants as the single source of truth instead of scattering hard-coded semantic convention strings through Laravel middleware, jobs, and console commands. If you cannot upgrade yet, keep an exact pin and centralize attribute names so a future codemod can replace removed or renamed conventions safely. There is no runtime alternative inside sem-conv because it is only a constants provider.
Weaver
How can I help you explore Laravel packages today?