...
opStatus Data saves information about the jobs performed on the queue and the result of the operation. This jobs are internal to NMIS9, related to the health and system maintenance, and it is not always related with a node. Contrary to status data, that save information related to a node.
Schema
This is the schema of for the opstatus collection:
...
- Activity:
...
- collect
...
- -
...
- escalations
...
- -
...
- metrics
...
- -
...
- selftest
...
- Context:
...
- node_uuid
...
- queue_id
...
- queue_tag
...
- worker_progress
...
- Details:
...
- Detail
...
- of
...
- the
...
- operation;
...
- completed
...
- successfully
...
- -
...
- failed:
...
- loading
...
- failed…
...
- -
...
- Can’t
...
- call
...
- method…
...
- expire_at
...
- Stats:
...
- Time
- Status:
...
- ok
...
- -
...
- error
...
- Time
...
- Type:
...
- completed
...
- -
...
- exception
Example
| Code Block |
|---|
{"_id":"5cbdb0fd2b1813502c414c52",
"time":1555935485.269778,
"stats":
{"time":0.1784820556640625},
"context":
{"queue_tag":null,
"worker_process":20524,
"queue_id":"5cbdb0fd2b1813500c414988"},
"type":"completed",
"expire_at":"2019-06-21T12:18:05.269Z",
"details":"completed successfully, backup saved as /usr/local/nmis9/backups/nmis-config-backup-2019-04-22-2218.tar.gz",
"status":"ok",
"activity":"configbackup"} |
...