CLI history and alarm rules

What you need

A CLI identity with telemetry:read for history, config:read for rules and config:write for rule changes.

How to do it

1. Run history with the series ID, start and end times, resolution and a result limit.
2. If it returns a job, inspect it with history job --id JOB_UUID --wait 30s.
3. List rules before creating or changing them. Use a private request file and keep the same request ID for the same retry.

Good to know

Pause stops a rule's evaluation. Mute keeps evaluation running without notifications. A history job may need time before its results are ready.

If something goes wrong

Start a new query if results expired. Correct scope or validation errors instead of retrying them indefinitely.