History: server load, memory and disks are also kept as hourly (four months) and daily (over two years) averages with lowest and highest; endpoint answers as hourly (four months) beside the daily figures. Charts ask for 24 hours to a year and are drawn from whichever is fine enough. A disk that two weeks call flat is looked at again over ninety days for the forecast. Built once from what is kept. One chart: TimeChart replaces the sparkline and the multi-line chart: hover and arrow-key readout, a lowest/highest band, gaps shown as gaps, the same ranges everywhere and the choice remembered. Used for server trends, comparing servers, a check's availability and answer times (Endpoints > History) and a server's availability. Read API: /api/v1 (servers, metrics, alerts, incidents, inventory, network, endpoints and their history, maintenance) with personal read-only tokens made under the user menu: shown once, hashed, 30/90/365 days or none, ten at most, removed with their owner. GET only. Documented in API.md. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
25 lines
810 B
SQL
25 lines
810 B
SQL
CREATE TABLE `endpoint_hourly` (
|
|
`check_id` integer NOT NULL,
|
|
`hour` text NOT NULL,
|
|
`total` integer DEFAULT 0 NOT NULL,
|
|
`ok` integer DEFAULT 0 NOT NULL,
|
|
`ms_sum` integer DEFAULT 0 NOT NULL,
|
|
`ms_count` integer DEFAULT 0 NOT NULL,
|
|
`ms_max` integer DEFAULT 0 NOT NULL,
|
|
PRIMARY KEY(`check_id`, `hour`),
|
|
FOREIGN KEY (`check_id`) REFERENCES `endpoint_checks`(`id`) ON UPDATE no action ON DELETE cascade
|
|
);
|
|
--> statement-breakpoint
|
|
CREATE TABLE `server_metrics_rollup` (
|
|
`server_id` integer NOT NULL,
|
|
`metric` text NOT NULL,
|
|
`grain` text NOT NULL,
|
|
`at` text NOT NULL,
|
|
`sum` real NOT NULL,
|
|
`n` integer NOT NULL,
|
|
`min` real NOT NULL,
|
|
`max` real NOT NULL,
|
|
PRIMARY KEY(`server_id`, `metric`, `grain`, `at`),
|
|
FOREIGN KEY (`server_id`) REFERENCES `servers`(`id`) ON UPDATE no action ON DELETE cascade
|
|
);
|