On Better Stack?

Better Stack logs, uptime or status page acting up? We fix it.

Better Stack is three products in a trenchcoat: Logtail, uptime monitoring and status pages. Each works well on its own. When one of them silently stops delivering or quietly drops data outside its retention window, it is on you to notice, and that is usually how we get called.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

better-stack.log

still failing

What it is

Better Stack at a glance

Better Stack is an observability platform originally built on top of Logtail, the log management product from Czech company Better Stack s.r.o. It now bundles log management, uptime monitoring, incident management and status pages into one integrated SaaS.

Logs are stored in ClickHouse, which keeps queries fast across billions of lines. Uptime monitoring runs from several global probe regions, incident response rolls up alerts from logs and checks, and the status page component is often used independently of the rest. The free tier is generous, and paid plans unlock longer retention and more probe regions.

Type
Observability SaaS: logs, uptime, incidents, status pages
First released
2020 as Logtail; rebranded as Better Stack in 2022
License
Proprietary SaaS, free tier and usage based pricing
Maintained by
Better Stack s.r.o., Prague
Typically used for
Centralised logs, uptime monitoring, on call alerting, public status pages

The honest version

Better Stack pros and cons

No technology is all upside. This is where Better Stack earns its place and where it tends to cause trouble.

Where Better Stack is strong

  • Four products, one billLogs, uptime, incidents and status pages are tied together, so a failing deployment shows up in the same timeline as the probes that noticed it and the incident that was opened.
  • Logtail queries are quickClickHouse backs the log store, which keeps searches across billions of lines responsive in a way that cheaper offerings do not.
  • Status page on a public URL in minutesTemplates, subscribers, incident history and a custom domain can be live inside an afternoon, which is useful during an outage week when leadership is asking for one.
  • Reasonable free tierEnough log retention and uptime checks for a small side project or an early stage startup, which is not true of every alternative in this bracket.
  • Multi region probesUptime checks run from several continents, so a US only probe failure versus a European pass tells you the problem is network, not origin.
  • Friendly API and SDKsLog shipping SDKs exist for most mainstream languages, and the REST API covers the setup paths that matter for infrastructure as code.

Where Better Stack bites

  • Retention is short on the cheap plansThree to seven days of log retention is common on entry plans, which is enough for live debugging but not for a post incident review two weeks later.
  • Incident ladder is less mature than PagerDutyRotations, overrides and escalation policies work but are younger than the incumbents, and large on call teams sometimes find edge cases.
  • Status page subscriber errors are quietA bounced email or a broken RSS subscriber drops silently, and the customers you most wanted to notify are the ones that stop getting updates.
  • Ingest rate limits bite under incident loadA noisy service during an outage can blow through the ingest budget and have its own logs dropped exactly when you needed them.
  • Custom domain DNS can be fiddlyCNAME and SSL verification on a status page occasionally fail in ways that are hard to diagnose without access to the upstream registrar.
  • Less third party ecosystem than DatadogFewer official integrations with the long tail of SaaS tools, so unusual sources often need their own small shipping script.

Sound familiar?

Common Better Stack problems we fix

The Better Stack problems that bring people to us, and what you have once each one is fixed.

retention: log older than 3 days

Historical logs are not in the query result

Retention on the current plan has expired, so the log line you remember writing last week is simply no longer stored. The fix is either longer retention or archiving the slice you care about before it drops.

Retention aligned with how you debug

subscriber delivery failed

Status page subscribers are not getting updates

Email bounces, broken webhooks and stale RSS readers accumulate quietly. During a real incident, the customers you most want to reach are the ones silently removed from the list.

Subscribers reachable again

uptime check flapping

Uptime probes disagree with each other

One region sees a 500 while another sees a 200, so the check alternates and alerts fire every few minutes. Usually a DNS or CDN edge issue rather than a true origin fault.

Probes agree, alerts quiet

401 Unauthorized: source token

Log shipping suddenly stops

A source token was rotated or a service redeployed with the wrong secret. The dashboard looks fine until nobody can find today's logs.

Shipping restored, alerts set

ingest rate limited

Logs dropped during incident load

A noisy service under pressure pushes past the ingest budget, and a chunk of the logs you most needed go into the void. Buffering, filtering and plan sizing settle it.

Ingest headroom for the worst hour

DNS verification failed, CNAME not found

Status page custom domain is not verifying

A CNAME at the registrar is missing, pointing at the wrong target, or being flattened by a proxy in front of it. We walk the DNS chain and the SSL issuance until status.yourdomain.com resolves cleanly.

Custom domain live and encrypted

webhook signature mismatch

Incident webhooks fail to deliver

A signing secret drift between Better Stack and the receiving endpoint, so every incident webhook is rejected and the downstream automation never fires.

Webhooks signed and accepted

heartbeat missed for monitor

Heartbeat pings keep going missing

A cron job that was supposed to ping Better Stack after it finished is either failing silently or running on a schedule that misses the heartbeat window. We align the schedule and add a retry.

Heartbeats honest about the job

What we do

Better Stack help, from setup to sustained reliability

Call us for one failing monitor, or let us own the whole observability setup.

Rescue
Logs missing, status page subscribers lost, or uptime checks flapping. We settle the immediate symptom and then explain what happened.
Log pipeline setup
Source tokens, sampling, retention, archiving and shipping SDKs configured against your actual log volume rather than an optimistic estimate.
Uptime and heartbeat design
Multi region probes, heartbeat jobs, alert routing and dashboards built so a real outage looks different from a probe blip.
Status page rollout
Subscribers imported, custom domain verified, incident templates written and historical incidents backfilled where it helps buyers trust the page.
Incident playbooks
Rotations, overrides, severity ladders and post incident templates set up so the on call experience is not a different story on every call.
Managed Tech
Monthly reviews of retention, ingest, subscriber health and alert fatigue, and a line to call when the status page fails to update at the worst possible moment.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Better Stack alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Better Stack questions

Something else? Call+1 737 727 7327

Why can I not find yesterday's logs in Better Stack?

Retention on the current plan is likely shorter than the gap you are asking about. The free and lower paid tiers store logs for three to seven days by default, and queries silently return nothing beyond that window. Moving to a longer retention tier or exporting a rolling archive into object storage both solve it, and we size the right option against your real log volume.

How do we stop uptime checks from flapping?

Flapping usually means one probe region sees something the others do not, which is almost always a DNS or CDN edge issue rather than a bad origin. We tighten the check to require failure from two regions before firing, set a reasonable recovery grace period, and dig into the region that disagreed to find the real cause.

Why are status page subscribers not getting notifications?

Email bounces, webhook signature changes and stale RSS readers all remove subscribers quietly. The dashboard shows the failure counts per subscription type. We clear bounces, re-verify the sending domain's SPF and DKIM, and reach out to key customer subscribers directly if they were on the removed list.

Is Better Stack a reasonable Datadog replacement?

For small to mid sized teams that mostly need logs, uptime, incidents and a status page, yes. Once you need distributed tracing across dozens of services, deep APM, or an enormous ecosystem of integrations, Datadog or Grafana Cloud usually fit better. We will say plainly which side of that boundary your workload sits on.

Can you help with log ingestion when we are rate limited?

Yes. The first step is usually filtering out debug level noise and sampling health check logs at source, which cuts volume without hiding real problems. If you are genuinely producing data at the limit the fix is a bigger plan, but most teams recover the budget by shipping less from the start.

How much does Better Stack help cost?

Estimates do not cost anything. Share what you are trying to set up or fix, send a snapshot of the current configuration, and we send back a price before anything is touched.

Free estimate

Better Stack letting you down?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.