llms.txt
Compare with other sites' llms.txt files →# Logdash
> Paste your URL and watch a live dashboard in 30 seconds, no account needed. Uptime monitoring, logs and metrics for SaaS founders.
Every link below is the markdown version of a page on https://logdash.io. All of them in one file: https://logdash.io/llms-full.txt
## Product
- [Logdash - Uptime monitoring, logs and metrics for SaaS founders](https://logdash.io/index.html.md): Paste your URL and watch a live dashboard in 30 seconds, no account needed. Uptime monitoring, logs and metrics for SaaS founders.
- [Uptime monitoring with Telegram and webhook alerts](https://logdash.io/features/monitoring.md): Uptime monitoring for your site and API. Checks as often as every 15 seconds, Telegram and webhook alerts, and status pages with a public API. Start free.
- [Error logs that show why your app went down](https://logdash.io/features/logging.md): Error logs from every service in one live stream. Search them to see why your app went down. SDKs for Node.js, Python, Go and 5 more. Free for 10,000 logs an hour.
- [Response time monitoring and custom metrics](https://logdash.io/features/metrics.md): Response time on every uptime check, plus sign-ups, payments or queue depth from your code in one line. Live charts by minute, hour and day. 5 metrics free.
- [Pricing](https://logdash.io/pricing.md): Simple, transparent pricing. Start for free, upgrade as you grow. No hidden fees or complex usage tiers.
- [Uptime monitoring for founders, indie hackers and SaaS](https://logdash.io/use-cases.md): Uptime monitoring for one founder, a pile of side projects, a WordPress store or a SaaS with paying users, with real plan numbers.
- [Uptime monitoring for solo founders](https://logdash.io/use-cases/solo-founders.md): Five monitors checked every 5 minutes for free, Telegram alerts and a public status page, then 15-second checks for $15 a month once the product earns it.
- [Uptime monitoring for indie hackers](https://logdash.io/use-cases/indie-hackers.md): Hosted uptime checks for every side project, Telegram alerts, and a status API to show live uptime on your landing page. Free for 5 projects.
- [Uptime monitoring for WordPress stores and renewals](https://logdash.io/use-cases/wordpress-sites.md): Catch a stalled wp-cron, stuck subscription renewals and a broken checkout on a WooCommerce, membership or booking site, with one health route and Telegram alerts.
- [Uptime monitoring for SaaS](https://logdash.io/use-cases/saas.md): 15-second checks on 50 monitors, Telegram and webhook alerts, a status page on your own domain and a status API, for $15 a month with no per-seat pricing.
## Docs
- [Docs](https://logdash.io/docs.md): Set up Logdash logging, metrics, uptime monitoring and web analytics, read the plan limits and pick one of the eight official SDKs.
- [Logging](https://logdash.io/docs/logging.md): Learn how to track system events and errors in real-time with Logdash logging. Understand retention policies and rate limits.
- [Metrics](https://logdash.io/docs/metrics.md): Track custom metrics from your application to monitor key business indicators with Logdash.
- [Monitoring](https://logdash.io/docs/monitoring.md): Monitor your services with HTTP health checks, uptime tracking, and public status pages with Logdash.
- [Build your own status page](https://logdash.io/docs/status-pages.md): A public API, a typed client and copy-paste components for a status page that looks like the rest of your site.
- [Web analytics](https://logdash.io/docs/web-analytics.md): Count visitors without cookies, track custom events with properties and see which signed-in users come back, with one script tag.
- [Web analytics privacy](https://logdash.io/docs/web-analytics-privacy.md): How Logdash counts visitors without cookies, what it stores and for how long, and what to tell your visitors.
- [SDKs](https://logdash.io/docs/sdks.md): Reference for the eight official Logdash SDKs and the HTTP API underneath them. Install, send your first log and your first metric.
- [Self-host Logdash](https://logdash.io/docs/self-hosting.md): Logdash is AGPL-3.0 licensed and the repository is public. Running it in production on your own infrastructure is not supported yet. Here is what works and what does not.
- [Logdash Node.js SDK](https://logdash.io/docs/sdks/node.md): Install the Logdash Node.js SDK, send your first log and your first metric.
- [Logdash Python SDK](https://logdash.io/docs/sdks/python.md): Install the Logdash Python SDK, send your first log and your first metric.
- [Logdash Go SDK](https://logdash.io/docs/sdks/go.md): Install the Logdash Go SDK, send your first log and your first metric.
- [Logdash .NET SDK](https://logdash.io/docs/sdks/dotnet.md): Install the Logdash .NET SDK, send your first log and your first metric.
- [Logdash Java SDK](https://logdash.io/docs/sdks/java.md): Install the Logdash Java SDK, send your first log and your first metric.
- [Logdash Rust SDK](https://logdash.io/docs/sdks/rust.md): Install the Logdash Rust SDK, send your first log and your first metric.
- [Logdash Ruby SDK](https://logdash.io/docs/sdks/ruby.md): Install the Logdash Ruby SDK, send your first log and your first metric.
- [Logdash PHP SDK](https://logdash.io/docs/sdks/php.md): Install the Logdash PHP SDK, send your first log and your first metric.
## Comparisons
- [Logdash vs Uptime Kuma](https://logdash.io/vs/uptime-kuma.md): Detailed comparison between Logdash and Uptime Kuma. Learn why founders choose managed monitoring over self-hosted solutions.
- [Logdash vs Uptime Robot](https://logdash.io/vs/uptime-robot.md): Detailed comparison between Logdash and Uptime Robot. See why modern founders choose full observability over basic uptime monitoring.
- [Logdash vs Datadog](https://logdash.io/vs/datadog.md): Detailed comparison between Logdash and Datadog. Discover why early-stage founders choose affordable simplicity over enterprise complexity.
- [Logdash vs Grafana](https://logdash.io/vs/grafana.md): Detailed comparison between Logdash and Grafana. See why founders choose pre-built monitoring over DIY dashboards and configurations.
- [Logdash vs Better Stack](https://logdash.io/vs/better-stack.md): Detailed comparison between Logdash and Better Stack. Compare unified monitoring experience vs. multiple separate products.
- [Logdash vs PostHog](https://logdash.io/vs/posthog.md): Detailed comparison between Logdash and PostHog. Learn when to use Logdash for app health monitoring vs PostHog for product analytics.
- [Uptime monitoring alternatives](https://logdash.io/alternatives.md): Honest side-by-side pages for every uptime and cron monitoring tool people move to Logdash from, including when the other tool is the better pick.
- [UptimeRobot alternative for founders](https://logdash.io/alternatives/uptimerobot.md): HTTP checks every 5 minutes free, 15 seconds on Pro, Telegram and webhook alerts, a status page, and your app logs and metrics in the same dashboard.
- [Uptime Kuma alternative, hosted](https://logdash.io/alternatives/uptime-kuma.md): Hosted HTTP checks, push heartbeats, a status page and Telegram alerts, with no container to update. Honest about where Uptime Kuma is the better pick.
- [Pingdom alternative for solo founders](https://logdash.io/alternatives/pingdom.md): Uptime checks, response times, a status page and Telegram alerts for four services on a free plan, without buying synthetic monitoring by the check.
- [Better Stack alternative for small teams](https://logdash.io/alternatives/better-stack.md): HTTP monitors, push heartbeats, a status page and Telegram alerts on a free plan, minus the on-call rotations and escalation policies you never turned on.
- [Cronitor alternative for jobs and uptime](https://logdash.io/alternatives/cronitor.md): Push heartbeats for background jobs and HTTP checks for your API in one dashboard, with Telegram alerts. Honest about where Cronitor still wins on cron.
- [Healthchecks.io alternative](https://logdash.io/alternatives/healthchecks-io.md): Cron heartbeats and HTTP uptime checks in one hosted dashboard, with Telegram and webhook alerts. Includes where Healthchecks.io is still the better tool.
- [Checkly alternative without synthetics](https://logdash.io/alternatives/checkly.md): HTTP checks with status code and response time, Telegram and webhook alerts, no Playwright suite to keep green. Plus where Checkly is worth the extra work.
- [StatusCake alternative, free tier](https://logdash.io/alternatives/statuscake.md): The Logdash free plan: five HTTP monitors, five minute checks, Telegram and webhook alerts, a public status page. And where StatusCake wins.
- [Site24x7 alternative for small teams](https://logdash.io/alternatives/site24x7.md): Site24x7 is an IT operations suite. If you wanted four HTTP checks and a Telegram alert, here is what Logdash does instead, and where Site24x7 still wins.
- [Freshping alternative after the shutdown](https://logdash.io/alternatives/freshping.md): Freshworks shut Freshping down on 6 March 2026. Logdash replaces the HTTP checks, status page and alerts, and adds cron heartbeats, logs and metrics.
- [Hyperping alternative with logs and metrics](https://logdash.io/alternatives/hyperping.md): Hyperping does uptime and status pages well. Logdash puts the logs and metrics for that service next to the check, with cron heartbeats, from $9 a month.
- [updown.io alternative for logs and uptime](https://logdash.io/alternatives/updown-io.md): updown.io does pay-per-check uptime and does it well. Logdash adds application logs, custom metrics and cron heartbeats beside the check, on a flat plan.
- [HetrixTools alternative for HTTP uptime](https://logdash.io/alternatives/hetrixtools.md): Logdash has no blacklist monitoring and no server agent. It does HTTP checks, cron heartbeats, status pages, plus logs and metrics for the same service.
- [Gatus alternative without self-hosting](https://logdash.io/alternatives/gatus.md): Gatus is excellent and its YAML config is a real advantage. Here is where a hosted checker wins instead, and the checks Gatus does that Logdash does not.
- [Upptime alternative, faster checks](https://logdash.io/alternatives/upptime.md): Upptime is a clever hack that works. The five-minute Actions cron floor and the commits in your repo are the two reasons people move. Here is the trade.
- [Instatus alternative with monitoring](https://logdash.io/alternatives/instatus.md): You bought a status page and ended up buying uptime monitoring too. Logdash starts from the monitors. Here is the trade, including where Instatus wins.
- [Statuspage alternative that monitors](https://logdash.io/alternatives/atlassian-statuspage.md): Statuspage does not check anything. You still need a monitor and the glue between them. Logdash runs the check and publishes the page from one monitor.
## Guides
- [Health check endpoint best practices](https://logdash.io/health-check.md): What a health endpoint should check, what it must never check, why it returns 503 and not 500, and how to point a monitor at it in three steps.
- [Next.js health check endpoint](https://logdash.io/health-check/nextjs.md): The App Router health route in full: a GET handler in app/api/health/route.ts, one select 1 against the database, a 503 on failure, and no caching.
- [Express health check endpoint](https://logdash.io/health-check/express.md): Liveness and readiness routes for Express, why the readiness one has to touch the database and return 503, and how to monitor it every 5 minutes.
- [SvelteKit health check endpoint](https://logdash.io/health-check/sveltekit.md): A +server.ts health route for SvelteKit with a database check, a 503 on failure, prerender switched off, and a monitor watching it from outside.
- [Nuxt health check endpoint](https://logdash.io/health-check/nuxt.md): A Nitro health route for Nuxt: server/api/health.get.ts, defineEventHandler, a database check, setResponseStatus for the 503, and a monitor on top.
- [NestJS health check endpoint](https://logdash.io/health-check/nestjs.md): The Terminus controller, the version without the package, what to check and what to leave out, and how to point a monitor at the 503 once it works.
- [FastAPI health check endpoint](https://logdash.io/health-check/fastapi.md): An async /health route with a real SELECT 1, a 503 on failure, the Docker and compose HEALTHCHECK lines, and the monitor that turns it into an alert.
- [Django health check endpoint](https://logdash.io/health-check/django.md): A plain Django view with a real database query and a 503, the django-health-check package, the Celery worker gap, and the monitor that alerts on it.
- [Flask health check endpoint](https://logdash.io/health-check/flask.md): A Flask blueprint that runs one real query, returns 503 when the database is unreachable, and gets watched by a monitor that alerts on the transition.
- [Rails health check endpoint and /up](https://logdash.io/health-check/rails.md): Rails 8 mounts /up by default, but it only proves the app booted. Add a controller that queries the database, returns 503, and put a monitor on it.
- [Laravel health check endpoint and /up](https://logdash.io/health-check/laravel.md): Laravel 11 added a /up health route, but it only proves the framework booted. Add a route with a database check, a 503, and a monitor watching it.
- [Phoenix health check endpoint in Elixir](https://logdash.io/health-check/phoenix.md): Phoenix has no built-in health route. Write one that queries Ecto, reports the cluster, returns 503 when the Repo is gone, and put a monitor on it.
- [Spring Boot health check endpoint](https://logdash.io/health-check/spring-boot.md): Expose /actuator/health, set show-details safely, add a custom HealthIndicator, and watch the 503 that Actuator already returns when a contributor is DOWN.
- [ASP.NET Core health check endpoint](https://logdash.io/health-check/dotnet.md): AddHealthChecks, MapHealthChecks and AddDbContextCheck in Program.cs, why Unhealthy returns 503, what the body should not say, and how to watch it.
- [Go health check endpoint with net/http](https://logdash.io/health-check/go.md): A copy-pasteable Go health handler using db.PingContext, a one-second context timeout and a 503 on failure, plus the monitor that turns it into an alert.
- [Status page and custom status page](https://logdash.io/status-page.md): A status page fed by real uptime checks: hosted by Logdash, a custom status page on your own domain, or your own build on a public JSON API. Free plan included.
- [Status page API: public JSON, no key](https://logdash.io/status-page/api.md): One public endpoint per status page. Curl it or use the typed @logdash/status client. The real response shape, caching rules, and how it compares to the Statuspage API.
- [Open source status page: what is open, what is not](https://logdash.io/status-page/open-source.md): Which parts of a Logdash status page are open source, AGPL-3.0 app and MIT client and components, where the data lives, and how it compares to Uptime Kuma and Upptime.
- [Free self-hosted status page](https://logdash.io/status-page/self-hosted.md): Self-host the status page with an MIT Next.js starter and Docker, for free. The uptime checks stay hosted, because they do not self-host in one command yet.
- [Free status page with built-in monitoring](https://logdash.io/status-page/free.md): What a free status page includes in 2026: the Logdash free plan in full, compared with the Instatus, Better Stack and Atlassian Statuspage free tiers.
- [Free status page with custom domain](https://logdash.io/status-page/free-custom-domain.md): Custom domains on the hosted Logdash page are Pro only. The free path: the public API plus a Next.js starter on your own subdomain, and who else offers it.
- [Custom status page: your domain or your build](https://logdash.io/status-page/custom.md): Put a hosted status page on status.yourdomain.com with one CNAME, or build your own on the public API. The DNS record, the Cloudflare catch, and the trade-offs.
- [Status page template: Next.js, one-click Vercel](https://logdash.io/status-page/template.md): An MIT Next.js status page template with a one-click Vercel deploy, a one-file HTML version you can paste, and how it compares to Upptime and Uptime Kuma themes.
- [React status page component for Next.js](https://logdash.io/status-page/react.md): A copy-paste React status page: one shadcn command, your Tailwind theme, server rendering in Next.js, a Vercel starter, and the same component for Svelte.
- [Status page embed: widget and uptime badges](https://logdash.io/status-page/embed.md): Embed live status in your website: a React or Svelte widget on a public JSON API, or SVG badges in classic, status and card styles, light or dark.
- [Status page examples worth copying](https://logdash.io/status-page/examples.md): GitHub, Vercel, Stripe, Linear and Cloudflare status pages, checked in October 2026: what each does well, what a small SaaS should copy and what to skip.
- [Status page best practices](https://logdash.io/status-page/best-practices.md): Where to host a status page, what to put on it, how to show uptime percentages honestly and how often to post during an incident, with numbers from GitHub and Vercel.
- [Cron job monitoring that alerts on silence](https://logdash.io/cron-monitoring.md): How cron job monitoring works, why one ping per run is not enough on Logdash, the three heartbeat patterns that are, and when Healthchecks.io fits better.
- [Scheduled task monitoring with heartbeats](https://logdash.io/cron-monitoring/scheduled-tasks.md): Monitor scheduled tasks with a heartbeat: the task proves it ran and silence sends a Telegram alert. A crontab to paste, and where Healthchecks.io fits better.
- [Dead man's switch monitoring for cron jobs](https://logdash.io/cron-monitoring/dead-mans-switch.md): How a dead man's switch works for cron: silence is the alert. A crontab to paste, Telegram or webhook alerts, and when Dead Man's Snitch is the better pick.
- [Backup monitoring for AWS, Azure and scripts](https://logdash.io/cron-monitoring/backup-monitoring.md): AWS Backup and Azure Backup already alert on failed jobs. For pg_dump, restic and rsync scripts, a heartbeat that alerts when the last good backup gets too old.
- [Restic backup monitoring with Telegram alerts](https://logdash.io/cron-monitoring/restic-backup.md): A restic script that runs backup and check, moves a stamp only when both pass, and a heartbeat that alerts when it goes stale. Plus when Healthchecks.io fits better.
- [pg_cron monitoring: failed jobs and alerts](https://logdash.io/cron-monitoring/pg-cron.md): Query cron.job_run_details for pg_cron failed jobs, then turn the last good run into a 10-second heartbeat that sends a Telegram alert when a job fails or stops.
- [Laravel scheduler monitoring](https://logdash.io/cron-monitoring/laravel-scheduler.md): Why pingOnSuccess falls short, a 10-second heartbeat that catches a dead schedule:run and failed tasks, and an honest look at spatie/laravel-schedule-monitor.
- [Celery beat monitoring with a 10-second canary](https://logdash.io/cron-monitoring/celery-beat.md): A canary task beat sends every 10 seconds, a push monitor that alerts on the first 15-second gap, and where Cronitor or Flower is the better pick.
- [Sidekiq monitoring with a canary job](https://logdash.io/cron-monitoring/sidekiq.md): A sidekiq-cron canary every 5 seconds, a push monitor that alerts on the first 15-second gap, and when Cronitor is the better pick.
- [BullMQ monitoring: dashboards and heartbeats](https://logdash.io/cron-monitoring/bullmq.md): Bull Board and Taskforce.sh show your queues. A 10-second job scheduler and a Logdash push monitor tell you when nothing is being processed.
- [Kubernetes CronJob monitoring and alerts](https://logdash.io/cron-monitoring/kubernetes-cronjob.md): Alert when a Kubernetes CronJob fails or stops: a 10-second watcher on lastSuccessfulTime with Telegram alerts, or the kube-state-metr