Component schema

OperationPatternRuleAnnotations

object1 direct reference

Definition

Pattern Rules use hard delete and have no folder/sharing/versions-history concept, so only creation/update/last-matched timestamps are tracked here.

string

Timestamp when this Pattern Rule was created. Set by the server; read-only.

string

Timestamp of the last update to this Pattern Rule. Doubles as the optimistic-concurrency token (truncated to millisecond precision at write time): required on PUT for UI (Clerk session token) callers -- a missing or stale value there is rejected with 400 (SupersededVersion). Optional for machine-token/OAuth PUT callers, which skip the concurrency check entirely when it is omitted.

string

Read-only: a value supplied on write is always ignored, never rejected, so a normal GET -> edit spec -> PUT round trip doesn't need to strip it back out. Bumped to the current time by every successful PUT on this rule (an edit counts as "using" it), and separately by an out-of-band job based on real telemetry-matching activity, writing directly to the database -- the two sources are independent and can disagree. null on a freshly created rule that has neither been matched nor edited since.

Used by 1

These schemas and endpoints reference this type directly.

SchemaOperationPatternRuleMetadata

json

OpenAPI source1234567891011121314151617181920
{
  "description": "Pattern Rules use hard delete and have no folder/sharing/versions-history concept, so\nonly creation/update/last-matched timestamps are tracked here.\n",
  "properties": {
    "dash0.com/created-at": {
      "description": "Timestamp when this Pattern Rule was created. Set by the server; read-only.",
      "type": "string",
      "format": "date-time"
    },
    "dash0.com/updated-at": {
      "description": "Timestamp of the last update to this Pattern Rule. Doubles as the optimistic-concurrency token (truncated to millisecond precision at write time): required on `PUT` for UI (Clerk session token) callers -- a missing or stale value there is rejected with 400 (`SupersededVersion`). Optional for machine-token/OAuth `PUT` callers, which skip the concurrency check entirely when it is omitted.",
      "type": "string",
      "format": "date-time"
    },
    "dash0.com/last-matched-at": {
      "description": "Read-only: a value supplied on write is always ignored, never rejected, so a normal GET -> edit spec -> PUT round trip doesn't need to strip it back out. Bumped to the current time by every successful `PUT` on this rule (an edit counts as \"using\" it), and separately by an out-of-band job based on real telemetry-matching activity, writing directly to the database -- the two sources are independent and can disagree. `null` on a freshly created rule that has neither been matched nor edited since.",
      "type": "string",
      "format": "date-time"
    }
  }
}