dcloud monitoring metrics
CPU, disk and network of every machine, and database volume usage
- resourcesList the resources that record metrics, and the apps that ship logs
- listList the metrics of one resource and when each was last recorded
- get-dataDatapoints of up to eight metrics of one resource, one per period
dcloud monitoring custom-metrics
Series an application publishes itself, charted and alarmed on like built-ins
- putPublish datapoints to custom metrics (CloudWatch PutMetricData)
- listList custom series: namespace, metric name, dimensions, last datapoint
- get-dataDatapoints of one custom series, one per period
dcloud monitoring alarms
Thresholds on a metric that notify by email or webhook
- listList alarms, those in ALARM first
- getDescribe one alarm and its current state
- createCreate an alarm on one metric of one resource
- updateChange an alarm; changing what it measures resets it to INSUFFICIENT_DATA
- deleteDelete an alarm and its history
- historyThe state changes of an alarm, newest first, and who was notified
dcloud monitoring checks
Uptime checks: a URL requested on a schedule, with response times and outages
- listList uptime checks, those that are down first
- getDescribe one uptime check: its settings, state and why, and its last result
- createCreate an uptime check
- updateChange an uptime check; changing what it requests starts it over as pending
- deleteDelete an uptime check with its results and outages
- pauseStop running a check; an open outage is closed without a notification
- resumeRun a paused check again, from pending
- resultsUptime %, response times per period, and the latest raw results of a check
- outagesThe outage log of a check, newest first, with who was notified
- locationsWhere checks run from: the control plane and each probe location, its health and the addresses to allowlist
dcloud monitoring logs
What a deployed app printed, shipped by the agent on its machine
- filterSearch an app’s log lines, newest first
dcloud monitoring status-pages
Public status pages at {slug}.status.{root}, built from uptime checks
- listList the organization’s status pages and their public URLs
- createPublish a status page at {slug}.status.{root}
- getDescribe a status page: its components, their current state, subscriber count
- updateChange a status page’s title, description or address
- deleteDelete a status page, its incidents and its subscribers
- put-componentsReplace the page’s components with this ordered list
dcloud monitoring incidents
Incidents posted on a status page, with their timeline of updates
- listOpen incidents, and those resolved in the last `days` days, newest first
- createPost an incident; the page’s confirmed subscribers are emailed and webhooks called
- updatePost an update to an incident; status resolved closes it. Subscribers are told
- deleteRemove an incident and its updates from the page (nobody is told)
dcloud monitoring subscribers
Who a status page emails or calls about incidents and components going down
- listList a page’s subscribers and whether each has confirmed
- addAdd a webhook, or invite an email address (it confirms by link first)
- removeRemove a subscriber
Generated from the API description, the same one the API checks requests against and the CLI is built from.