@leaflow/sdk 0.0.0-dev.29.g8fe6a71 → 0.0.0-dev.293.g578f043

package/dist/monitoring/v1/generated/validators/getServerMetricParams.zod.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const getServerMetricParamsMaxPointsMin = 0;
+export declare const GetServerMetricParams: zod.ZodObject<{
+    item_key: zod.ZodOptional<zod.ZodString>;
+    item_id: zod.ZodOptional<zod.ZodString>;
+    from: zod.ZodOptional<zod.z.ZodISODateTime>;
+    to: zod.ZodOptional<zod.z.ZodISODateTime>;
+    max_points: zod.ZodOptional<zod.ZodInt>;
+    include_thresholds: zod.ZodOptional<zod.ZodBoolean>;
+}, zod.z.core.$strict>;
+export type GetServerMetricParams = zod.input<typeof GetServerMetricParams>;
+export type GetServerMetricParamsOutput = zod.output<typeof GetServerMetricParams>;

package/dist/monitoring/v1/generated/validators/getServerMetricParams.zod.js

@@ -0,0 +1,40 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const getServerMetricParamsMaxPointsMin = 0;
+export const GetServerMetricParams = zod.strictObject({
+    item_key: zod
+        .string()
+        .optional()
+        .describe("**Prefix match**: `vfs.fs.size` returns one series per mount point. Supply this or `item_id`"),
+    item_id: zod.string().optional(),
+    from: zod.iso.datetime({ offset: true }).optional().describe("Defaults to one hour ago"),
+    to: zod.iso.datetime({ offset: true }).optional(),
+    max_points: zod
+        .int()
+        .min(getServerMetricParamsMaxPointsMin)
+        .optional()
+        .describe("Number of downsampling buckets. 0 returns the collected data points unchanged"),
+    include_thresholds: zod
+        .boolean()
+        .optional()
+        .describe("Also return the thresholds currently in effect for these items"),
+});

package/dist/monitoring/v1/generated/validators/getSliReportParams.zod.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const getSliReportParamsPeriodsMin = 0;
+export declare const getSliReportParamsPeriodsMax = 100;
+export declare const GetSliReportParams: zod.ZodObject<{
+    from: zod.ZodOptional<zod.z.ZodISODateTime>;
+    to: zod.ZodOptional<zod.z.ZodISODateTime>;
+    periods: zod.ZodOptional<zod.ZodInt>;
+}, zod.z.core.$strict>;
+export type GetSliReportParams = zod.input<typeof GetSliReportParams>;
+export type GetSliReportParamsOutput = zod.output<typeof GetSliReportParams>;

package/dist/monitoring/v1/generated/validators/getSliReportParams.zod.js

@@ -0,0 +1,33 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const getSliReportParamsPeriodsMin = 0;
+export const getSliReportParamsPeriodsMax = 100;
+export const GetSliReportParams = zod.strictObject({
+    from: zod.iso.datetime({ offset: true }).optional(),
+    to: zod.iso.datetime({ offset: true }).optional(),
+    periods: zod
+        .int()
+        .min(getSliReportParamsPeriodsMin)
+        .max(getSliReportParamsPeriodsMax)
+        .optional()
+        .describe("Return the most recent N complete periods. Use this or from/to, not both"),
+});

package/dist/monitoring/v1/generated/validators/hostInterfaceResource.zod.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const HostInterfaceResource: zod.ZodObject<{
+    available: zod.ZodBoolean;
+    dns: zod.ZodString;
+    ip: zod.ZodString;
+    port: zod.ZodInt;
+    use_ip: zod.ZodBoolean;
+}, zod.z.core.$strict>;
+export type HostInterfaceResource = zod.input<typeof HostInterfaceResource>;
+export type HostInterfaceResourceOutput = zod.output<typeof HostInterfaceResource>;

package/dist/monitoring/v1/generated/validators/hostInterfaceResource.zod.js

@@ -0,0 +1,28 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const HostInterfaceResource = zod.strictObject({
+    available: zod.boolean(),
+    dns: zod.string(),
+    ip: zod.string(),
+    port: zod.int(),
+    use_ip: zod.boolean(),
+});

package/dist/monitoring/v1/generated/validators/incidentActivityResource.zod.d.ts

@@ -0,0 +1,51 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const IncidentActivityResource: zod.ZodObject<{
+    activity_type: zod.ZodEnum<{
+        CLOSED: "CLOSED";
+        RECOVERED: "RECOVERED";
+        OPENED: "OPENED";
+        ACKNOWLEDGED: "ACKNOWLEDGED";
+        ASSIGNED: "ASSIGNED";
+        UNASSIGNED: "UNASSIGNED";
+        FOLLOWER_ADDED: "FOLLOWER_ADDED";
+        FOLLOWER_REMOVED: "FOLLOWER_REMOVED";
+        COMMENT: "COMMENT";
+        REOPENED: "REOPENED";
+    }>;
+    actor_display_name: zod.ZodString;
+    actor_user_id: zod.ZodString;
+    close_reason: zod.ZodString;
+    id: zod.ZodUUID;
+    incident_id: zod.ZodUUID;
+    message: zod.ZodString;
+    occurred_at: zod.z.ZodISODateTime;
+    source: zod.ZodEnum<{
+        SYSTEM: "SYSTEM";
+        OPERATOR: "OPERATOR";
+        ZABBIX: "ZABBIX";
+    }>;
+    subject_display_name: zod.ZodString;
+    subject_user_id: zod.ZodString;
+}, zod.z.core.$strict>;
+export type IncidentActivityResource = zod.input<typeof IncidentActivityResource>;
+export type IncidentActivityResourceOutput = zod.output<typeof IncidentActivityResource>;

package/dist/monitoring/v1/generated/validators/incidentActivityResource.zod.js

@@ -0,0 +1,47 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const IncidentActivityResource = zod.strictObject({
+    activity_type: zod.enum([
+        "OPENED",
+        "RECOVERED",
+        "ACKNOWLEDGED",
+        "ASSIGNED",
+        "UNASSIGNED",
+        "FOLLOWER_ADDED",
+        "FOLLOWER_REMOVED",
+        "COMMENT",
+        "CLOSED",
+        "REOPENED",
+    ]),
+    actor_display_name: zod.string(),
+    actor_user_id: zod.string().describe("The operator. Empty when the source is SYSTEM or ZABBIX"),
+    close_reason: zod.string(),
+    id: zod.uuid(),
+    incident_id: zod.uuid(),
+    message: zod.string(),
+    occurred_at: zod.iso.datetime({ offset: true }),
+    source: zod.enum(["SYSTEM", "OPERATOR", "ZABBIX"]),
+    subject_display_name: zod.string(),
+    subject_user_id: zod
+        .string()
+        .describe("The user who was assigned, or removed from the followers"),
+});

package/dist/monitoring/v1/generated/validators/incidentFollowerResource.zod.d.ts

@@ -0,0 +1,28 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const IncidentFollowerResource: zod.ZodObject<{
+    display_name: zod.ZodString;
+    followed_at: zod.z.ZodISODateTime;
+    user_id: zod.ZodString;
+}, zod.z.core.$strict>;
+export type IncidentFollowerResource = zod.input<typeof IncidentFollowerResource>;
+export type IncidentFollowerResourceOutput = zod.output<typeof IncidentFollowerResource>;

package/dist/monitoring/v1/generated/validators/incidentFollowerResource.zod.js

@@ -0,0 +1,26 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export const IncidentFollowerResource = zod.strictObject({
+    display_name: zod.string(),
+    followed_at: zod.iso.datetime({ offset: true }),
+    user_id: zod.string(),
+});

package/dist/monitoring/v1/generated/validators/incidentResource.zod.d.ts

@@ -0,0 +1,85 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const IncidentResource: zod.ZodObject<{
+    acknowledge_message: zod.ZodString;
+    acknowledged: zod.ZodBoolean;
+    acknowledged_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    acknowledged_by_display_name: zod.ZodString;
+    acknowledged_by_user_id: zod.ZodString;
+    assigned_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    assignee_display_name: zod.ZodString;
+    assignee_user_id: zod.ZodString;
+    close_message: zod.ZodString;
+    close_reason: zod.ZodString;
+    closed_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    closed_by_display_name: zod.ZodString;
+    closed_by_user_id: zod.ZodString;
+    duration_seconds: zod.ZodInt;
+    followers: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        display_name: zod.ZodString;
+        followed_at: zod.z.ZodISODateTime;
+        user_id: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    host_connection: zod.ZodString;
+    host_display_name: zod.ZodString;
+    id: zod.ZodUUID;
+    incident_status: zod.ZodEnum<{
+        PROBLEM: "PROBLEM";
+        RESOLVED: "RESOLVED";
+    }>;
+    items: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        aggregation_function: zod.ZodString;
+        evaluation_window_seconds: zod.ZodInt;
+        item_id: zod.ZodString;
+        key: zod.ZodString;
+        name: zod.ZodString;
+        operator: zod.ZodString;
+        threshold: zod.ZodNullable<zod.ZodNumber>;
+        threshold_status: zod.ZodString;
+        value: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    name: zod.ZodString;
+    operational_data: zod.ZodString;
+    project_id: zod.ZodUUID;
+    resolved_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    resolved_trigger_expression: zod.ZodString;
+    server_id: zod.ZodNullable<zod.ZodUUID>;
+    server_name: zod.ZodString;
+    severity: zod.ZodEnum<{
+        NOT_CLASSIFIED: "NOT_CLASSIFIED";
+        INFORMATION: "INFORMATION";
+        WARNING: "WARNING";
+        AVERAGE: "AVERAGE";
+        HIGH: "HIGH";
+        DISASTER: "DISASTER";
+    }>;
+    started_at: zod.z.ZodISODateTime;
+    tags: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        tag: zod.ZodString;
+        value: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    trigger_expression: zod.ZodString;
+    web_check_id: zod.ZodNullable<zod.ZodUUID>;
+    zabbix_event_id: zod.ZodString;
+}, zod.z.core.$strict>;
+export type IncidentResource = zod.input<typeof IncidentResource>;
+export type IncidentResourceOutput = zod.output<typeof IncidentResource>;

package/dist/monitoring/v1/generated/validators/incidentResource.zod.js

@@ -0,0 +1,67 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { IncidentFollowerResource } from "./incidentFollowerResource.zod.js";
+import { MonitoringItemResource } from "./monitoringItemResource.zod.js";
+import { TagResource } from "./tagResource.zod.js";
+export const IncidentResource = zod.strictObject({
+    acknowledge_message: zod.string(),
+    acknowledged: zod.boolean(),
+    acknowledged_at: zod.iso.datetime({ offset: true }).nullable(),
+    acknowledged_by_display_name: zod.string(),
+    acknowledged_by_user_id: zod.string(),
+    assigned_at: zod.iso.datetime({ offset: true }).nullable(),
+    assignee_display_name: zod.string(),
+    assignee_user_id: zod.string(),
+    close_message: zod.string(),
+    close_reason: zod.string(),
+    closed_at: zod.iso.datetime({ offset: true }).nullable(),
+    closed_by_display_name: zod.string(),
+    closed_by_user_id: zod.string(),
+    duration_seconds: zod.int(),
+    followers: zod.array(IncidentFollowerResource).nullable(),
+    host_connection: zod.string(),
+    host_display_name: zod.string(),
+    id: zod.uuid(),
+    incident_status: zod
+        .enum(["PROBLEM", "RESOLVED"])
+        .describe("Whether monitoring considers the problem recovered. Independent of whether anyone has closed the incident"),
+    items: zod.array(MonitoringItemResource).nullable(),
+    name: zod.string(),
+    operational_data: zod.string().describe("The operational data line configured on the trigger"),
+    project_id: zod.uuid(),
+    resolved_at: zod.iso.datetime({ offset: true }).nullable(),
+    resolved_trigger_expression: zod.string(),
+    server_id: zod
+        .uuid()
+        .nullable()
+        .describe("The machine this alert is about. Null when the alert is not about a machine"),
+    server_name: zod.string().describe("Empty when server_id is null"),
+    severity: zod.enum(["NOT_CLASSIFIED", "INFORMATION", "WARNING", "AVERAGE", "HIGH", "DISASTER"]),
+    started_at: zod.iso.datetime({ offset: true }),
+    tags: zod.array(TagResource).nullable(),
+    trigger_expression: zod.string(),
+    web_check_id: zod
+        .uuid()
+        .nullable()
+        .describe("The web check that reported this alert. Null when the alert did not come from a web check. Both this and server_id are set when the check runs on one of your machines"),
+    zabbix_event_id: zod.string(),
+});

package/dist/monitoring/v1/generated/validators/itemListResponseBody.zod.d.ts

@@ -0,0 +1,44 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const ItemListResponseBody: zod.ZodObject<{
+    items: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        item_id: zod.ZodString;
+        key: zod.ZodString;
+        last_collected_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+        last_value: zod.ZodString;
+        name: zod.ZodString;
+        tags: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+            tag: zod.ZodString;
+            value: zod.ZodString;
+        }, zod.z.core.$strict>>>;
+        units: zod.ZodString;
+        value_type: zod.ZodEnum<{
+            FLOAT: "FLOAT";
+            CHARACTER: "CHARACTER";
+            LOG: "LOG";
+            UNSIGNED: "UNSIGNED";
+            TEXT: "TEXT";
+        }>;
+    }, zod.z.core.$strict>>>;
+}, zod.z.core.$strict>;
+export type ItemListResponseBody = zod.input<typeof ItemListResponseBody>;
+export type ItemListResponseBodyOutput = zod.output<typeof ItemListResponseBody>;

package/dist/monitoring/v1/generated/validators/itemListResponseBody.zod.js

@@ -0,0 +1,25 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { ItemResource } from "./itemResource.zod.js";
+export const ItemListResponseBody = zod.strictObject({
+    items: zod.array(ItemResource).nullable(),
+});

package/dist/monitoring/v1/generated/validators/itemResource.zod.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+export declare const ItemResource: zod.ZodObject<{
+    item_id: zod.ZodString;
+    key: zod.ZodString;
+    last_collected_at: zod.ZodNullable<zod.z.ZodISODateTime>;
+    last_value: zod.ZodString;
+    name: zod.ZodString;
+    tags: zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
+        tag: zod.ZodString;
+        value: zod.ZodString;
+    }, zod.z.core.$strict>>>;
+    units: zod.ZodString;
+    value_type: zod.ZodEnum<{
+        FLOAT: "FLOAT";
+        CHARACTER: "CHARACTER";
+        LOG: "LOG";
+        UNSIGNED: "UNSIGNED";
+        TEXT: "TEXT";
+    }>;
+}, zod.z.core.$strict>;
+export type ItemResource = zod.input<typeof ItemResource>;
+export type ItemResourceOutput = zod.output<typeof ItemResource>;

package/dist/monitoring/v1/generated/validators/itemResource.zod.js

@@ -0,0 +1,32 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Monitoring API
+ * Monitoring for your own project: enroll machines, read metrics, work through incidents, schedule maintenance windows, and set availability targets.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * ## Two distinctions worth keeping straight
+ *
+ * - **Disabling is not deleting.** `POST /servers/{id}/disable` is reversible and preserves all history. `DELETE /servers/{id}` also removes the monitored host, its history and every incident recorded against it, and cannot be undone.
+ * - **Recovery is not closure.** `incident_status` reports whether monitoring considers the problem recovered; `closed_at` reports whether someone has finished handling it. An incident that has not recovered may still be closed as an accepted risk.
+ *
+ * ## The PSK is returned once
+ *
+ * Enrollment and rotation responses include `tls_psk`. No other endpoint will return it again, so store it immediately. If it is lost, rotate once more — at the cost of updating the agent configuration on the monitored machine.
+ * OpenAPI spec version: 1.0.0
+ */
+import * as zod from "zod";
+import { TagResource } from "./tagResource.zod.js";
+export const ItemResource = zod.strictObject({
+    item_id: zod.string(),
+    key: zod.string(),
+    last_collected_at: zod.iso.datetime({ offset: true }).nullable(),
+    last_value: zod.string(),
+    name: zod.string(),
+    tags: zod.array(TagResource).nullable(),
+    units: zod.string(),
+    value_type: zod.enum(["FLOAT", "CHARACTER", "LOG", "UNSIGNED", "TEXT"]),
+});