API ReferenceNew CentralGuidesMRT APIConfiguration API
GithubAirheads Developer Community
API Reference

Update db-observer-rules by name

List of Database observer rules.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length ≤ 9999

Name used to identify each rule.

Query Params
string

LOCAL - To update local objects. SHARED - To update shared objects. Default - Defaults to SHARED if not provided

string

Scope at which local object needs to be updated. Mandatory if object-type = LOCAL. Should not be provided for object-type = SHARED.

string

Device function for which the local object needs to be updated. Mandatory if object_type = LOCAL. Should not be provided for object_type = SHARED.

Body Params

db-observer-rulesbody object

column-names
array of objects
length ≤ 2147483647

Name of the columns from the database table to monitor. This
value can be empty. If this value is left empty, the rule will
not be activated and an error will be generated.

column-names
boolean
Defaults to false

Enable the Database observer rule.

filter-condition
array of objects
length ≤ 2147483647

Condition to filter the operation results. This value can be empty.
Filter conditions are not mandatory, if they are not added, no filters
will be applied to the rule.

filter-condition
int32
1 to 4096
Defaults to 10

Number of changes to be stored in the monitor type 'LAST_N'.

string
required
length between 1 and 256

Name used to identify each rule.

operations
array of objects
length ≤ 2147483647

Operation types to be monitored. This value can be empty. If
this value is left empty, the rule will not be activated and
an error will be generated.

operations
string
length between 1 and 256

Name of the database table to monitor. This value can be empty.
If this value is left empty, the rule will not be activated and
an error will be generated.

string
enum

Monitor type. This value can be empty. If this value is left
empty, the rule will not be activated and an error will be
generated.

Show Details
COUNTMake a count of the number of operations going to the database.
JOURNALRegister all the operations going to the database in a buffer. The content can be dumped in a file later.
LAST_NKeep track of the last N transactions going to the database. Unlike 'JOURNAL', this just keeps a finite, well-known number of transactions.
Allowed:
Responses

Language
Credentials
OAuth2
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json