AttributePatternRuleSpec

The telemetry attribute whose values this rule's patterns match, e.g. dash0.operation.name. Immutable after creation: an update whose value disagrees with the stored row is rejected with 400. Defaults to dash0.operation.name when omitted on create, which is what keeps callers written against the pre-generalization API working unchanged.

OpenTelemetry service.namespace resource attribute this Pattern Rule applies to. Empty string when the target service has no namespace (never omitted/null on a stored row). Immutable after creation: an update whose value disagrees with the stored row is rejected with 400. Omit when listing to scope the request organization/dataset-wide across every namespace instead of one.

OpenTelemetry service.name resource attribute this Pattern Rule applies to. Required on create. Immutable after creation: an update whose value disagrees with the stored row is rejected with 400. Omit when listing to scope the request organization/dataset-wide across every service instead of one.

Human-authored operation-name pattern using the placeholder DSL (e.g. /users/<userId>; << escapes a literal <) -- the named_pattern concept defined in the "Pattern Representation and Storage" ADR appendix, whose transformations internal/operationpatterncompiler implements. Required on create. Populated on every GET/List response by reconstructing it from the stored canonical representation -- including for auto_derived rows this API never compiled itself -- so it is always present on a read, not only for rows this API wrote.

Defaults to user_defined on create; the server ignores any client-supplied value there -- only the Operation Miner creates auto_derived rows. On update, only the auto_derived -> user_defined transition is accepted (this is how promoting a Miner-inferred rule works); attempting to set auto_derived is rejected with 400.

Required on both POST and PUT; there is no default. Omitting it could otherwise silently reactivate or deactivate a rule the caller did not intend to touch on PUT, so the same explicit requirement applies uniformly on create.

Computed by the server. Target-attribute-specific side-effect data; for dash0.operation.name it carries canonicalOperation, the literal value applied to every span this rule matches. A value supplied on write is ignored.

Computed by the server from pattern. The anchored regular expression the collector's Operation Processor compiles to match operation names against this rule. A value supplied on write is ignored.

Computed by the server from pattern. Placeholder names, in left-to-right occurrence order. A value supplied on write is ignored.

Ranks this rule for list ordering: GET/List responses are always sorted by priority descending first, so higher-priority rules (including manually-promoted ones) surface before lower-priority and auto_derived ones. 1 (Minor) through 5 (Major) are the user-facing levels, defaulting to 3 (Standard) when omitted on create; an update that omits it preserves the row's current value instead of resetting it. 0 is reserved for auto_derived rows the Operation Miner writes -- a client-supplied 0 is rejected with 400.