Error logs that show why it went down. Every line, one search away.

Your monitor tells you the app is down. Logs from every instance, in one live stream, tell you why. One line of code in any of 8 languages.

No signup · No credit card · See the live demo

Search logs Live
Last hour 48,213 lines
Errors 2

A monitor tells you it’s down. Your logs tell you why.

Logs spread across servers and terminals turn every bug into a hunt. Put them in one stream and the hunt becomes a search.

  • Error volume chart

    A chart above the list counts lines over time, with errors in red. Drag across a spike to zoom the list into those minutes.

  • Every instance, one stream

    Every server, worker and cron job that uses your API key writes to the same stream. No more hopping between machines.

  • Live tail

    New lines show up the moment they arrive. Your search and filters stay on, so only the lines you care about scroll by.

  • Full-text search

    Type a few words and get every line that contains all of them, ignoring case. Any id or email you logged is searchable.

  • Levels and namespaces

    Seven log levels, from error down to silly. Split an app into auth, payments or cron with namespaces and filter by them.

  • The whole line

    Open a line to read the whole message, with JSON pretty printed. Arrow keys step through the other lines at that level.

Your first log in three steps.

No agent to run and no config file. If you can write console.log, you can do this.

  1. Copy the setup prompt

    Open Logs in your service and pick your stack. The prompt Logdash copies holds your API key, the install command and a code sample.

  2. Paste it, or wire it by hand

    Hand the prompt to your AI coding assistant and it adds the SDK. Or run npm install @logdash/node and pass your key yourself.

  3. Search the first lines

    Logs land in the live stream a moment after you send them. Type a word, pick a level, and open a line to read it in full.

Node.js logging in one line.

Import the SDK, pass your API key and call the level you need. Lines print to your console too, and the same package runs in Next.js, SvelteKit, Express and Bun.

Browse all SDKs
server.ts 
import { Logdash } from '@logdash/node';

const logdash = new Logdash(process.env.LOGDASH_API_KEY);

logdash.info('Application started successfully');
logdash.error('An unexpected error occurred');
logdash.warn('Low disk space warning');

const authLogdash = logdash.withNamespace('auth');
authLogdash.info('User logged in');
authLogdash.error('Authentication failed');

Works with your stack

  • Node.js
  • Python
  • Go
  • logo_NET .NET
  • Java
  • file_type_rust Rust
  • Ruby
  • PHP
  • Curl

Error logs FAQ

Have a different question? Reach out on Discord

How long are logs kept?
24 hours on the free Hobby plan, 7 days on Builder and 30 days on Pro. Older lines drop out of search on their own.
Is there a free plan for logs?
Yes. Hobby is free and takes up to 10,000 logs per hour for each app, kept for 24 hours. Builder at $9 a month raises that to 25,000 an hour, and Pro at $15 to 50,000.
Which languages are supported?
Official SDKs cover Node.js, Python, Go, .NET, Java, Rust, Ruby and PHP. The Node.js package also runs in Next.js, SvelteKit, Express, NestJS, Fastify, Bun and Deno.
Can I send logs without an SDK?
Yes. POST JSON with message, level and createdAt to https://api.logdash.io/logs and put your key in the project-api-key header. /logs/batch takes up to 100 logs per request.
Can I search my logs?
Yes. Type one or more words and you get every line whose message contains all of them, ignoring case. Level and namespace filters stack on top and keep working as new lines stream in, and a time range takes you further back.
Which log levels are supported?
Seven: error, warning, info, http, verbose, debug and silly. The Node.js SDK has a method for each, like logdash.error() and logdash.warn().
Does logging slow down my app?
Log calls in the Node.js SDK return right away. Lines are queued and sent in small batches in the background. In short-lived jobs, await logdash.flush() before the process exits.
Can I get alerts on error logs?
Not yet. Alerts fire when an uptime check fails, on Telegram or a webhook. In the log view, errors are drawn in red on the volume chart, so a spike stands out the moment you open it.

Know before they do.

Paste your URL and we start watching it right now.

No signup · No credit card · Claim later with GitHub or Google

Or watch the live demo
Your first 30 days
  1. Day 1
    The alert beats the tweet Checks start 30 seconds after you paste a URL. When it goes down, you hear it first.
  2. Day 7
    The refresh reflex is gone Logs and metrics sit next to your uptime, so you stop checking by hand.
  3. Day 30
    Users hear it from you first A status page on your domain answers before they ask. You ship, Logdash watches.