Rudow Node Logger — AI skill for Claude Code

@rudow/node-logger

**Rudow — AI that reads your logs and tells you what broke, in plain English.**

Send logs to Rudow, then ask questions like "why did checkout errors spike this morning?" from the dashboard, Slack, or any MCP-compatible AI agent (Claude Code, Cursor, Windsurf).

• Read-only by design — Rudow never mutates, rewrites, or acts on your systems. It reads logs. That's it.
• Flat pricing — monthly caps, never usage meters. Limits are caps, not overage charges.
• Free-forever tier — the Hobby plan is free, no credit card, no time limit.
• MCP server — claude mcp add --transport http rudow https://mcp.rudow.ai/mcp

One-line setup for any Node service: batches log entries and ships them to the ingest API.

Homepage: https://rudow.ai · Documentation: https://rudow.ai/docs

Install

npm install @rudow/node-logger

Direct use

import { createLogger } from "@rudow/node-logger";

const logger = createLogger({
  apiKey: process.env.RUDOW_API_KEY!,            // your project API key
});

logger.info("server started", { port: 8080 });
logger.error("checkout failed", { orderId, status: 500, error: "ECONNREFUSED" });

Exported API

`@rudow/node-logger` exports:

• createLogger(options)
• createWinstonTransport(options)
• default export (Pino transport target)
• recordHttpRequest(client, event)
• recordException(client, event)
• startMetricsHeartbeat(client, options?)
• expressTelemetry(client, options?)

Types are exported too (`Logger`, `LoggerOptions`, `Level`, `HttpRequestEvent`, `ExceptionEvent`, `MetricsOptions`, `TelemetryOptions`).

Entries are buffered and flushed every 2s or once 20 are queued (both configurable). Sending is best-effort — logging never throws into your app. On a graceful exit the logger flushes automatically (see **Shutdown durability**); call `await logger.flush()` yourself only if you've set `flushOnExit: false`.

Bandwidth & durability

The logger is built to be light