Ingest structured logs, monitor real-time time-series metrics with Recharts, inspect JSON payloads, and automate background threshold alerting in milliseconds.
Sub-millisecond ingestion pipeline with non-blocking async serialization.
Continuous live polling stream updating logs and graphs dynamically.
Complete compile-time type validation, auto-retry, and lightweight payloads.
Autonomous background worker evaluating error rate and latency anomalies.
Everything your engineering team needs to ingest, visualize, and monitor real-time distributed telemetry with zero bloat.
Ingests high-throughput JSON telemetry into Neon Serverless PostgreSQL with indexed composite lookups on service, level, and timestamp for real-time querying.
Tracks response_time_ms, cpu_usage_pct, and memory_usage_mb with Recharts area charts and statistical KPI calculations (P95, Avg, Min, Max).
Auto-registers active telemetry producers like payment-service and auth-service with dynamic heartbeat tracking.
Built-in multi-service telemetry generator (scripts/simulate-traffic.ts) emitting concurrent traffic spikes and webhook errors.
Evaluates error count and latency thresholds every minute via node-cron, recording violation events in the incident audit stream.
Integrate PulseLens into any Node.js, Next.js, Express, or microservice architecture with lightweight REST APIs or our strongly-typed TypeScript SDK.
import { PulseLens } from '@pulselens/sdk';// 1. Initialize PulseLens SDK clientconst pulse = new PulseLens({endpoint: 'http://localhost:3000',service: 'payment-service',});// 2. Ingest structured telemetry logsawait pulse.log({level: 'info',message: 'Processed stripe webhook for order #9821',});// 3. Emit real-time time-series metricsawait pulse.metric({name: 'response_time_ms',value: 42.5,});
How PulseLens coordinates high-throughput telemetry streams across database storage, real-time UI subscribers, and autonomous cron alerting.
Services emit structured logs and latency metrics via TypeScript SDK.
Next.js API routes validate payloads and enforce indexing requirements.
Persistent indexed relational storage with high-speed composite queries.
3s live polling stream in frontend and automated 60s rule evaluation daemon.