cavaliba_api
Use case
Ships results back to Cavaliba’s app_cmt application - the counterpart to
fetching config from the same endpoint (see
Configuration and
CMT / app_cmt). This is what feeds app_cmt’s
raw/hourly/daily tables and its status dashboard.
Configuration
No type-specific fields: it POSTs to global.url using
global.client_id/client_secret/client_subidentity (the same identity
used to fetch config) and global.ssl_skipverify/timeout - so unlike the
other outputs, a working example needs the global: block too, not just the
outputs: entry:
global:
url: https://cavaliba.example.com/
client_id: key1
client_secret: xxxxxxxxx
outputs:
- name: cavaliba
type: cavaliba_apiOutput
Deliberately narrow, unlike the metrology outputs below - app_cmt only
tracks OK/KO plus duration and a short error string per check, not every
CheckItem:
| Field | Meaning |
|---|---|
checkname |
the check’s name (the _cmtcheck id, when config came from a remote fetch) |
status |
true if severity is none (OK) |
usec |
check duration, microseconds |
error |
the execution error, or the joined messages if the check ran but reported a non-none severity |
Example
cmt --report # send for real
cmt --report --dryrun --debug # preview the payload, send nothing