Operational Checklist
Use this checklist when rolling out Chirpier for OpenClaw in a real environment.
- verify the same bearer token works for logs and control-plane APIs
- emit canonical OpenClaw events
- confirm Chirpier auto-registers the event definitions
- create at least one valid chart per key signal
- create one reliability policy and one latency policy
- test destination delivery before depending on it
- inspect delivery history for both
testandalert - review event names for drift or one-off naming mistakes
- verify rollup queries use canonical periods:
minute,hour,day - verify invalid aggregate and semantic-class combinations are rejected
This catches most early integration errors before the setup becomes operationally important.
Last updated on