Component schema

SignalControlMeteringSettings

object1 direct reference

Definition

Per-organization control over edge billing metering enforcement. Set centrally by Dash0 and not customer-configurable.

Deliberately a sibling of signalControlEdge rather than a field inside it: that object is a pre-release entitlement gate that goes away at GA, and enforcement has to outlive it.

Every field is optional, and absence is meaningful — see enforce.

object

boolean

Whether edge collectors enforce billing metering for this organization.

true enforces: Signal Control components on edge stop acting on telemetry that no metering processor marked, so a capability cannot run on usage nothing metered.

false and an absent field both mean warn mode: the capabilities keep working on unmarked telemetry and the misconfiguration is only logged and reported. The two negatives are collapsed on purpose, so an organization can be returned to warn mode by writing false rather than by deleting a key, and an organization nobody has touched behaves identically to one explicitly parked.

The collector's compiled-in default is warn, permanently — enforcement is only ever something the server turns on. A collector that has never synced never enforces, but one that has been told to enforce keeps enforcing if it later loses contact.

Used by 1

These schemas and endpoints reference this type directly.

SchemaSettingsPerOrganizationAndDatasetInfo

json

OpenAPI source12345678910
{
  "description": "Per-organization control over edge billing metering enforcement. Set centrally by Dash0\nand not customer-configurable.\n\nDeliberately a sibling of `signalControlEdge` rather than a field inside it: that object\nis a pre-release entitlement gate that goes away at GA, and enforcement has to outlive it.\n\nEvery field is optional, and absence is meaningful — see `enforce`.\n",
  "type": "object",
  "properties": {
    "enforce": {
      "description": "Whether edge collectors enforce billing metering for this organization.\n\n`true` enforces: Signal Control components on edge stop acting on telemetry that no\nmetering processor marked, so a capability cannot run on usage nothing metered.\n\n`false` and an absent field both mean warn mode: the capabilities keep working on\nunmarked telemetry and the misconfiguration is only logged and reported. The two\nnegatives are collapsed on purpose, so an organization can be returned to warn mode by\nwriting `false` rather than by deleting a key, and an organization nobody has touched\nbehaves identically to one explicitly parked.\n\nThe collector's compiled-in default is warn, permanently — enforcement is only ever\nsomething the server turns on. A collector that has never synced never enforces, but\none that has been told to enforce keeps enforcing if it later loses contact.\n",
      "type": "boolean"
    }
  }
}