Automation and testing

Override recorded values

An override changes the value returned by an existing recorded OID while keeping the recording unchanged. Its type must match the recorded SNMP type. Overrides cannot create an object absent from the recording. An active override takes precedence over an SNMP SET to the same object.

{"dataContextId":"context-0", "values":[
  {"oid":".1.3.6.1.2.1.2.2.1.8.1",
   "type":"Integer", "value":"2"}
]}

For an agent with multiple recordings, specify dataContextId: context-0 identifies the first recording, context-1 the second, and so on. These automation IDs are different from community names and SNMPv3 context names. You may omit the context only when the agent has one recording. A PUT replaces the complete override set for that context. Send an empty values array, or DELETE the overrides resource, to clear it.

Type	JSON value encoding
Integer or Integer32	Signed 32-bit decimal string, for example "-1".
Counter32, Gauge32 or Unsigned32, TimeTicks	Unsigned 32-bit decimal string.
Counter64	Unsigned 64-bit decimal string. Keep it a string to preserve large values.
OctetString	Base64-encoded bytes. For example, "Um91dGVy" represents Router.
OID	Dotted numeric OID string.
IpAddress	IP address string.
Null	Use type "Null"; no payload value is required.

Automation type names are case-sensitive. The automation names Gauge32 and Unsigned32 differ from some legacy XML valueType names. Use the names in this table for JSON overrides.