Parsed representation of OTEL_SEMCONV_STABILITY_OPT_IN.

This is opaque: use lookupStability with any signal key (e.g. "http", "database", "messaging") to query whether stable, old, or both conventions should be emitted. Well-known accessors httpOption and databaseOption are provided for convenience; third-party instrumentation libraries can query arbitrary keys without modifying this module.

Since: 0.4.0.0

Stability setting for a particular semantic convention area.

• Stable: emit only the new stable conventions.
• StableAndOld: emit both old and stable conventions (migration/dup mode).
• Old: emit only the legacy conventions (default when unset).

Since: 0.4.0.0

Backward-compatible alias.

Since: 0.4.0.0

Look up the stability setting for an arbitrary signal key.

Given a key like "http", "database", "messaging", etc., returns:

• StableAndOld if <key>/dup is present in the env var
• Stable if <key> is present
• Old otherwise

opts <- getSemanticsOptions
case lookupStability "messaging" opts of
  Stable      -> emitStableAttrs
  StableAndOld -> emitStableAttrs >> emitOldAttrs
  Old         -> emitOldAttrs

Since: 0.4.0.0

Stability setting for HTTP semantic conventions ("http" / "http/dup").

Since: 0.4.0.0

Stability setting for database semantic conventions ("database" / "database/dup").

Since: 0.4.0.0

Stability setting for code source-location conventions ("code" / "code/dup").

Controls whether code.function.name, code.file.path, code.line.number (stable) or code.function, code.namespace, code.filepath, code.lineno (legacy) are emitted.

Since: 0.5.0.0

Retrieves OTEL_SEMCONV_STABILITY_OPT_IN and parses it into SemanticsOptions.

This uses the global IORef trick to memoize the settings for efficiency. Note that getSemanticsOptions stores and returns the value of the first time it was called and will not change when OTEL_SEMCONV_STABILITY_OPT_IN is updated. Use getSemanticsOptions' to read the env var every time the function is called.

Since: 0.4.0.0

Version of getSemanticsOptions that is not memoized. It is recommended to use getSemanticsOptions for efficiency purposes unless it is necessary to retrieve the value of OTEL_SEMCONV_STABILITY_OPT_IN every time getSemanticsOptions' is called.

Since: 0.4.0.0