Log monitoring next to your uptime checks

Send logs over HTTP

Create an API key in the app and POST to /api/v1/logs/ingest. The endpoint takes whatever is easiest for you to produce:

• a single JSON object,
• a JSON array of objects,
• newline-delimited JSON (NDJSON), one object per line,
• or plain text, one log line per line.

Common field names are recognised, so most loggers work without changes: message, msg or text for the message; timestamp, time, ts or @timestamp for the time; level or severity for the level; service, app or host for the service. Anything else is kept as attributes you can search. Send up to 1,000 lines in a request.

curl -X POST https://uptimedog.makingstuffs.com/api/v1/logs/ingest \
  -H "Authorization: Bearer $UPTIMEDOG_KEY" \
  --data-binary '{"level":"error","service":"checkout","message":"Payment provider timed out","orderId":"A1042"}'

Search

Logs are indexed for full-text search as they arrive. Search for words or phrases across messages and attributes, then narrow by level (trace, debug, info, warn, error, fatal), by service and by time. A histogram shows volume over the range you're looking at, so a sudden burst of errors stands out before you read a single line.

Logs around an incident

Every incident links to the logs from the minutes around it. Instead of matching timestamps between two tools, open the incident and read what your application was saying when the monitor failed. If you've set up the AI assistant, it can search the same logs while it investigates.

Volume and retention by plan

Log volume is counted per month and logs are kept for a set number of days, depending on your plan:

When a month's volume is used up, further logs are refused with a clear error until the next month or an upgrade, and nothing else about your monitoring changes. Logs older than your retention are deleted automatically every hour.

Is this a replacement for a full logging platform?

For many small teams, yes: the questions they ask of logs are "what happened just before it broke?" and "how often is this error happening?", and that's what this is built for. If you need long-term archives, dashboards built from log fields or petabyte-scale queries, a dedicated logging product is a better fit, and you can still use Uptime Dog for uptime, status pages and on-call alongside it.