fix: transport (#17)

* feat: support custom transport for edge runtimes, export service descriptors

* feat: switch default transport to connect-web (drop connect-node)

Author: finxol

deno.json

@@ -20,7 +20,7 @@
   "imports": {
     "@bufbuild/protobuf": "npm:@bufbuild/protobuf@^2.11.0",
     "@connectrpc/connect": "npm:@connectrpc/connect@^2.1.1",
-    "@connectrpc/connect-node": "npm:@connectrpc/connect-node@^2.1.1"
+    "@connectrpc/connect-web": "npm:@connectrpc/connect-web@^2.1.1"
   },
   "compilerOptions": {
     "strict": true,

deno.lock

@@ -63,11 +63,49 @@ console.log(`Found ${totalSize} monitors`);
 
 ## Runtime Support
 
-| Runtime | Version | Module Format |
-| ------- | ------- | ------------- |
-| Node.js | >= 18   | ESM and CJS   |
-| Deno    | >= 2    | ESM (native)  |
-| Bun     | Latest  | ESM           |
+The SDK talks to the API over a fetch-based Connect transport
+(`@connectrpc/connect-web`), so it runs on any runtime with a global `fetch` —
+no HTTP/2 or `node:*` modules required:
+
+| Runtime            | Version | Module Format |
+| ------------------ | ------- | ------------- |
+| Node.js            | >= 18   | ESM and CJS   |
+| Deno               | >= 2    | ESM (native)  |
+| Bun                | Latest  | ESM           |
+| Cloudflare Workers | —       | ESM (edge)    |
+
+### Cloudflare Workers and edge runtimes
+
+The default client works on the edge as-is. The one caveat is that
+`@connectrpc/connect-web` issues requests with `redirect: "error"`, which
+`workerd` doesn't implement. If you hit
+`The redirect mode 'error' is not supported`, pass a transport with a
+redirect-tolerant `fetch` (the SDK re-exports `createAuthInterceptor` and the
+service descriptors for this):
+
+```typescript
+import { createConnectTransport } from "@connectrpc/connect-web";
+import {
+  createAuthInterceptor,
+  createOpenStatusClient,
+} from "@openstatus/sdk-node";
+
+const client = createOpenStatusClient({
+  transport: createConnectTransport({
+    baseUrl: "https://api.openstatus.dev/rpc",
+    interceptors: [createAuthInterceptor(env.OPENSTATUS_API_KEY)],
+    // workerd doesn't implement fetch's `redirect: "error"`; normalise it.
+    fetch: (input, init) =>
+      fetch(
+        input,
+        init?.redirect === "error" ? { ...init, redirect: "manual" } : init,
+      ),
+  }),
+});
+```
+
+When you pass a `transport`, the `apiKey` and `baseUrl` options are ignored —
+configure authentication on the transport via `createAuthInterceptor`.
 
 ## Full Workflow Example
 

docs/getting-started.md

@@ -2,7 +2,7 @@
 
 # Monitor Service
 
-Manage HTTP, TCP, and DNS monitors. The Monitor Service provides 14 RPC methods
+Manage HTTP, TCP, and DNS monitors. The Monitor Service provides 15 RPC methods
 for creating, updating, listing, triggering, deleting, querying monitor status
 and metrics, and inspecting HTTP response logs.
 
@@ -80,7 +80,7 @@ Updates are partial — only include the fields you want to change.
 
 ```typescript
 const { monitor } = await client.monitor.v1.MonitorService.updateHTTPMonitor({
-  id: "mon_123",
+  id: "123456",
   monitor: {
     name: "Updated API Monitor",
     active: false,
@@ -141,7 +141,7 @@ const { monitor } = await client.monitor.v1.MonitorService.createTCPMonitor({
 
 ```typescript
 const { monitor } = await client.monitor.v1.MonitorService.updateTCPMonitor({
-  id: "mon_123",
+  id: "123456",
   monitor: {
     name: "Updated Database Monitor",
   },
@@ -207,7 +207,7 @@ const { monitor } = await client.monitor.v1.MonitorService.createDNSMonitor({
 
 ```typescript
 const { monitor } = await client.monitor.v1.MonitorService.updateDNSMonitor({
-  id: "mon_123",
+  id: "123456",
   monitor: {
     name: "Updated DNS Check",
   },
@@ -263,7 +263,7 @@ contains one of HTTP, TCP, or DNS configuration.
 
 ```typescript
 const { monitor } = await client.monitor.v1.MonitorService.getMonitor({
-  id: "mon_123",
+  id: "123456",
 });
 
 if (monitor?.config.case === "http") {
@@ -287,7 +287,7 @@ Trigger an immediate check for a monitor.
 
 ```typescript
 const { success } = await client.monitor.v1.MonitorService.triggerMonitor({
-  id: "mon_123",
+  id: "123456",
 });
 
 console.log(`Trigger successful: ${success}`);
@@ -297,7 +297,7 @@ console.log(`Trigger successful: ${success}`);
 
 ```typescript
 const { success } = await client.monitor.v1.MonitorService.deleteMonitor({
-  id: "mon_123",
+  id: "123456",
 });
 ```
 
@@ -317,7 +317,7 @@ const client = createOpenStatusClient({
 });
 
 const { id, regions } = await client.monitor.v1.MonitorService.getMonitorStatus(
-  { id: "mon_123" },
+  { id: "123456" },
 );
 
 for (const { region, status } of regions) {
@@ -337,7 +337,7 @@ const client = createOpenStatusClient({
 });
 
 const summary = await client.monitor.v1.MonitorService.getMonitorSummary({
-  id: "mon_123",
+  id: "123456",
   timeRange: TimeRange.TIME_RANGE_7D,
   regions: [],
 });
@@ -358,11 +358,61 @@ The latency fields (`p50`, `p75`, `p90`, `p95`, `p99`) and count fields
 `regions` parameter is optional — pass an empty array to get metrics across all
 regions.
 
+`getMonitorSummary` returns a single aggregate over the window and `TimeRange`
+caps at 14 days. For a per-day series (e.g. to render status bars), use
+`getMonitorDailySummary` below.
+
+## Get Monitor Daily Summary
+
+Get per-day status buckets for one or more monitors over the last N days (max
+45). Each bucket is tagged with its `monitorId`, so you can render a status bar
+per monitor.
+
+```typescript
+import { createOpenStatusClient } from "@openstatus/sdk-node";
+
+const client = createOpenStatusClient({
+  apiKey: process.env.OPENSTATUS_API_KEY,
+});
+
+const { dailyStats } = await client.monitor.v1.MonitorService
+  .getMonitorDailySummary({
+    monitorIds: ["123456", "123457"],
+    days: 45,
+  });
+
+for (const stat of dailyStats) {
+  console.log(
+    `[${stat.monitorId}] ${stat.day}: ` +
+      `${stat.ok}/${stat.count} ok, ${stat.degraded} degraded, ${stat.error} error`,
+  );
+}
+```
+
+Request parameters:
+
+| Parameter    | Type              | Description                                          |
+| ------------ | ----------------- | ---------------------------------------------------- |
+| `monitorIds` | string[]          | One or more monitor IDs (1–50, required)             |
+| `days`       | number (optional) | Days to return (1–45, default 45; values >45 reject) |
+
+Each `MonitorDailyStat` has `monitorId`, `day` (RFC 3339, UTC midnight), and the
+`bigint` counts `count`, `ok`, `degraded`, `error`. Days with no checks are
+omitted — fill gaps client-side. Daily data is retained for 45 days.
+
+> The REST endpoint `GET /v1/monitor/{id}/summary` also returns a daily series,
+> but only `{ ok, count, day }` for a single monitor. Prefer
+> `getMonitorDailySummary` — it is multi-monitor and includes
+> `degraded`/`error`.
+
 ## List Monitor HTTP Response Logs
 
 List HTTP response logs for a monitor within the 14-day retention window.
 Supports time-window filtering and offset-based pagination.
 
+> Response logs are a paid feature. On the free plan these methods return
+> `permission_denied` ("Upgrade for response logs").
+
 ```typescript
 import {
   createOpenStatusClient,
@@ -377,7 +427,7 @@ const client = createOpenStatusClient({
 
 const { logs, pagination } = await client.monitor.v1.MonitorService
   .listMonitorHTTPResponseLogs({
-    id: "mon_123",
+    id: "123456",
     fromTimestamp: BigInt(Date.now() - 24 * 60 * 60 * 1000),
     toTimestamp: BigInt(Date.now()),
     limit: 25,
@@ -421,7 +471,7 @@ redacted response headers, error message, and serialized assertions.
 ```typescript
 const { log } = await client.monitor.v1.MonitorService
   .getMonitorHTTPResponseLog({
-    id: "mon_123",
+    id: "123456",
     logId: "log_456",
   });
 

docs/monitor-service.md

@@ -27,7 +27,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { webhookUrl: "https://hooks.slack.com/services/..." },
       },
     },
-    monitorIds: ["mon_123", "mon_456"],
+    monitorIds: ["123456", "123457"],
   });
 
 console.log(`Notification created: ${notification?.id}`);
@@ -55,7 +55,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { webhookUrl: "https://hooks.slack.com/services/..." },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -72,7 +72,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { webhookUrl: "https://discord.com/api/webhooks/..." },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -89,7 +89,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { email: "alerts@example.com" },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -106,7 +106,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { integrationKey: "your-integration-key" },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -125,7 +125,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { apiKey: "your-api-key", region: OpsgenieRegion.US },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -142,7 +142,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { chatId: "123456789" },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -159,7 +159,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { webhookUrl: "https://chat.googleapis.com/v1/spaces/..." },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -176,7 +176,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { webhookUrl: "https://oncall.example.com/..." },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -197,7 +197,7 @@ const { notification } = await client.notification.v1.NotificationService
         },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -214,7 +214,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { phoneNumber: "+1234567890" },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -231,7 +231,7 @@ const { notification } = await client.notification.v1.NotificationService
         value: { phoneNumber: "+1234567890" },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -253,7 +253,7 @@ const { notification } = await client.notification.v1.NotificationService
         },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -276,7 +276,7 @@ const { notification } = await client.notification.v1.NotificationService
         },
       },
     },
-    monitorIds: ["mon_123"],
+    monitorIds: ["123456"],
   });
 ```
 
@@ -349,7 +349,7 @@ const { notification } = await client.notification.v1.NotificationService
   .updateNotification({
     id: "notif_123",
     name: "Updated Slack Alerts",
-    monitorIds: ["mon_123", "mon_456", "mon_789"],
+    monitorIds: ["123456", "123457", "123458"],
   });
 ```