Serverless Function Monitoring
Debug Lambda and Cloud Functions without CloudWatch. Send logs via HTTP API from any serverless runtime.
>_ the problem
>_ why traditional tools fall short
- $CloudWatch scatters logs across log groups and streams, making it nearly impossible to follow a single request without complex Insights queries.
- $Vercel and Netlify function logs have minimal retention and no meaningful search, often disappearing before you can debug the issue.
- $APM tools designed for long-running servers struggle with the ephemeral nature of serverless functions and cold start patterns.
- $Agent-based monitoring cannot be installed in serverless environments where you do not control the runtime or operating system.
>_ how logmonitor solves this
HTTP API Integration
Send logs from any serverless runtime with a simple HTTP POST. No agents or SDK installation required. Works with Lambda, Cloud Functions, Azure Functions, Vercel, Netlify, and any other serverless platform.
Live Console
Stream serverless function logs in real time. Watch invocations flow through your functions live and spot errors instantly, even across thousands of concurrent executions.
Structured Search
Attach function name, invocation ID, trigger source, and any custom metadata to each log. Search across all invocations by any field to find the exact execution that failed.
Zero Overhead
The SDK and HTTP API add negligible latency to your function execution. Logs are sent asynchronously and do not extend your function's billable duration.
>_ quick setup
import { logmonitor } from 'logmonitor-js';logmonitor.init({ apiKey: 'your-api-key' });// The SDK auto-patches console.log/info/warn/error/debug// Logs are only sent in production (process.env.NODE_ENV === 'production')console.log('App started', { version: '1.0.0' });>_ pricing for this use case
Serverless log volume depends on invocation count. For moderate usage, the Pro plan at $19/mo covers 1 million logs. High-volume functions should use the Scale plan at $99/mo for 5 million logs and 90-day retention.
View all plans →>_ frequently asked questions
Yes. You can use the JavaScript SDK directly in Node.js Lambda functions or send logs via the HTTP API from any Lambda runtime including Python, Go, and Java.
The SDK sends logs asynchronously and batches them for efficiency. The additional execution time is negligible and will not meaningfully impact your Lambda billing.
Yes. The JavaScript SDK works natively in Vercel serverless and edge functions. Import the SDK, initialize it, and your logs will stream to the LogMonitor dashboard instead of disappearing from the Vercel log viewer.
Pass a shared correlation ID or request ID as metadata in every log call. When one function triggers another, forward the correlation ID so you can trace the full chain of invocations in the LogMonitor dashboard.
Yes. The SDK initializes quickly and does not add meaningful cold start latency. Initialization is lightweight and does not make any synchronous network calls during startup.
Yes. Register each function or group of functions as a separate app in LogMonitor. Logs from AWS Lambda, Google Cloud Functions, Azure Functions, and Vercel all appear in the same dashboard.