llms.txt
Compare with other sites' llms.txt files →# Sazabi
> AI-native observability for engineering teams and coding agents. Connect logs with source code, investigate production issues, and find root causes.
## Start here
- [Quickstart](https://docs.sazabi.com/get-started/quickstart): Connect your first project. CLI setup: `npx @sazabi/cli start`
- [Developer documentation](https://docs.sazabi.com): API, authentication, and integration guides
- [Connect a coding agent](https://docs.sazabi.com/get-started/coding-agents): MCP setup and authentication for coding agents and AI IDEs
- [MCP server reference](https://docs.sazabi.com/reference/mcp-server): Streamable HTTP endpoint and tool behavior
For workspace operations, connect through `https://mcp.sazabi.com/mcp`. Discover operations with `search` before calling `execute`. Follow the setup guide for authentication; never paste secret keys into chat.
## Product
- [Home](https://www.sazabi.com/home.md): Platform overview and key features
- [Company](https://www.sazabi.com/company.md): Our origins, mission, team, values, and open positions
- [Pricing](https://www.sazabi.com/pricing.md): Plans, included allowances, and usage pricing
- [Integrations](https://www.sazabi.com/integrations.md): Supported integrations and their public documentation
## Customer stories
- [Customers](https://www.sazabi.com/customers.md): Customer stories and production results
- [Weave](https://www.sazabi.com/customers/weave.md): Discover how this engineering intelligence platform uses Sazabi to replace noisy alerts and surface production issues within minutes.
- [Mastra](https://www.sazabi.com/customers/mastra.md): Discover how this TypeScript agent framework uses Sazabi to uncover and diagnose production problems without starting every investigation with a manual log review.
- [XMTP Labs](https://www.sazabi.com/customers/xmtp.md): Discover how this secure, decentralized messaging protocol partnered with Sazabi to catch bugs before they reach users and scale observability for its agent-powered consumer app.
## Blog
- [Blog](https://www.sazabi.com/blog.md): Engineering articles and product news
- [Announcing Sazabi 1.0 and General Availability](https://www.sazabi.com/blog/general-availability.md): Sazabi 1.0 is generally available, with two new features - Dashboards and Log Search - and fully self-serve sign-up in less than ten minutes.
- [Introducing Sazabi BYOC: Run Sazabi in Your Own Cloud](https://www.sazabi.com/blog/introducing-byoc.md): With Sazabi BYOC, the part of Sazabi that receives, processes, and stores your logs runs in your own cloud account, and Sazabi operates it.
- [Introducing cve.now: A Free Feed of Security Vulnerabilities for Agents](https://www.sazabi.com/blog/introducing-cve-now.md): cve.now is a free feed of CVEs and security advisories for agents and the teams that use them. No login, signup, or API key required.
- [The Sazabi Manifesto](https://www.sazabi.com/blog/manifesto.md): AI has changed what's possible in software systems. Observability hasn't caught up. This manifesto lays out a path forward.
- [Announcing Our $8M Seed Round and Open Beta](https://www.sazabi.com/blog/seed-round.md): Sazabi raised an $8M seed round led by J2 Ventures, Village Global, and Y Combinator - and we're opening the beta. No more waitlist.
- [Sazabi is Part of Y Combinator P26](https://www.sazabi.com/blog/yc-p26.md): Sazabi is joining Y Combinator's P26 batch as we continue building the future of AI-native observability.
## Comparisons and guides
- [Compare Sazabi](https://www.sazabi.com/compare.md): How Sazabi compares with other observability, logging and monitoring tools, with dated vendor facts.
- [Alternatives](https://www.sazabi.com/alternatives.md): Alternatives to popular observability tools, with prices taken from each vendor’s own pages.
- [Guides](https://www.sazabi.com/guides.md): Pricing explainers, how-to guides and security guides for engineering teams that run production.
- [Pricing guides](https://www.sazabi.com/guides/pricing.md): What observability, logging and monitoring tools cost, from list prices checked on each vendor’s own pages.
- [Security guides](https://www.sazabi.com/guides/security.md): What attacks and incidents leave behind in your logs, and how to investigate them with the logs you already have.
- [Glossary](https://www.sazabi.com/glossary.md): Plain-language definitions of observability, logging, incident and security terms.
- [Integrations by category](https://www.sazabi.com/integrations/categories.md): The sources Sazabi reads, grouped by what they are: cloud platforms, security tools, AI frameworks and more.
- [Detection](https://www.sazabi.com/detection.md): What Sazabi detects in production today, by issue group, with no monitors or alert rules to write.
- [Third-party dependency failures](https://www.sazabi.com/dependencies.md): How rate limits, exhausted quotas, outages and webhook failures from the APIs you call show up, and how to catch them.
- [Account Takeover Investigation: A Response Playbook](https://www.sazabi.com/guides/security/account-takeover-investigation.md): Investigate a suspected account takeover from your logs: scope sessions and IPs, build the timeline, contain, check what was accessed, and notify.
- [Active Attack Alerts From Your Production Logs | Sazabi](https://www.sazabi.com/detection/active-attacks.md): Sazabi opens an investigated issue when attack payloads, exploit probes or credential stuffing show up in your logs. No rules to write. See what is live.
- [AgentCat MCP connector for the Sazabi agent](https://www.sazabi.com/integrations/agentcat.md): The Sazabi agent signs in to AgentCat over OAuth to search sessions, open issues and read metric trends for the MCP servers you track in AgentCat.
- [AI Agent Misbehavior Alerts From Your Logs | Sazabi](https://www.sazabi.com/detection/agent-misbehavior.md): Sazabi opens an investigated issue when token usage jumps by feature or customer, a sign of a looping or abused agent. See what is live and what is not.
- [AI Agent Monitoring: How to Catch a Rogue Agent](https://www.sazabi.com/guides/detect/rogue-ai-agents.md): AI agent monitoring for tool calls and permissions: log every action, compare it to an allowed scope and alert on new tools, loops and sensitive calls.
- [Airbyte MCP: sync logs and records in Sazabi](https://www.sazabi.com/integrations/airbyte.md): The Sazabi agent uses the Airbyte MCP connector to read sync job logs and connection status, and query connected sources, with your Airbyte permissions.
- [ALB Access Logs: Enable, Read, and Query with Athena](https://www.sazabi.com/guides/alb-access-logs.md): Turn on Application Load Balancer access logs, set the S3 bucket policy, read each field in an entry, and query the files with Athena or awk.
- [Alchemy Webhooks: Notify Types, Payloads and Retries](https://www.sazabi.com/integrations/webhooks/alchemy.md): Alchemy Notify webhooks explained: Address Activity, NFT Activity and Custom types, the event object, setup with a Sazabi URL, signing and retries.
- [Alert Fatigue: Causes, Effects, and How to Reduce It](https://www.sazabi.com/glossary/alert-fatigue.md): Alert fatigue is when too many low-value alerts make on-call engineers slower to react to real ones. See the causes, Google SRE rules, and a fix checklist.
- [Anthropic API rate limits: 429s, headers and detection](https://www.sazabi.com/dependencies/anthropic/rate-limits.md): Claude API rate limits: RPM, input and output tokens per minute, cache-aware ITPM, anthropic-ratelimit headers, spend-cap 429s and what to log.
- [Anthropic outage: Claude 529 overloaded\_error and detection](https://www.sazabi.com/dependencies/anthropic/outages.md): How an Anthropic API outage shows up: 529 overloaded\_error, 500, 504, mid-stream errors, plus spend limit and credit balance errors, and detection.
- [API Contract Change Alerts for Third-Party APIs | Sazabi](https://www.sazabi.com/detection/api-contract-changes.md): Sazabi sets up detection for vendor API responses that change shape, such as a field that starts arriving empty, and opens an investigated issue.
- [API Gateway Logs: Access and Execution Logging](https://www.sazabi.com/integrations/aws/api-gateway.md): Which API Gateway access log fields matter, how to find 5xx by route and failed authorizations, and how Sazabi reads the logs from CloudWatch Logs.
- [APM: Application Performance Monitoring Explained](https://www.sazabi.com/glossary/apm.md): Application performance monitoring (APM) tracks the speed, errors, and dependencies of a running app. See what it covers, how data arrives, and its limits.
- [AppDynamics vs Dynatrace: Pricing, APM and Fit](https://www.sazabi.com/compare/appdynamics-vs-dynatrace.md): AppDynamics vs Dynatrace compared on list prices, business transactions, topology, deployment and OpenTelemetry, using vendor pages checked Nov 8, 2026.
- [Approaching Limit Alerts for Quotas and Credits | Sazabi](https://www.sazabi.com/detection/approaching-limits.md): Sazabi opens an investigated issue when a quota, burst credit, rate limit or file handle budget runs low. Its agent sets it up from your logs.
- [Attack Payload Alerts: SQLi, SSRF and Path Traversal](https://www.sazabi.com/detection/attack-payloads.md): Sazabi spots SQL injection, SSRF and path traversal payloads in your logs and opens an investigated issue. A built-in sensor, on by default.
- [Attio MCP connector for the Sazabi agent](https://www.sazabi.com/integrations/attio.md): The Sazabi agent calls Attio's MCP tools to match error-log domains to company records, list entries, tasks and notes, and follow up on affected customers.
- [Authentication Anomaly Alerts: Stuffing and Travel](https://www.sazabi.com/detection/authentication-anomalies.md): Sazabi writes sensors for failed-login bursts, credential stuffing and impossible travel from your login logs and opens investigated issues.
- [Automatic Outage Detection From Your Logs | Sazabi](https://www.sazabi.com/detection/outages.md): Sazabi opens an investigated issue when a service goes quiet, an event rate collapses or workers crash-loop. Built-in sensors, no alert rules to write.
- [Autumn MCP connector for the Sazabi agent](https://www.sazabi.com/integrations/autumn.md): The Sazabi agent reads Autumn customers, plans, balances and request logs through its MCP server to explain a blocked feature or a stuck subscription.
- [AWS CloudTrail Logs and Monitoring With Sazabi](https://www.sazabi.com/integrations/aws/cloudtrail.md): What CloudTrail logs contain, what to query for root logins and failed console sign-ins, and how Sazabi ingests a trail through CloudWatch Logs.
- [AWS Cost Anomaly Detection and DIY Alternatives](https://www.sazabi.com/guides/detect/cloud-spend-anomalies.md): Cloud cost anomaly detection with AWS Cost Anomaly Detection plus a SQL query over billing exports. Covers delays, thresholds, credits and what to do.
- [AWS WAF Logs: Fields, Queries and Sazabi Setup](https://www.sazabi.com/integrations/aws/waf.md): What AWS WAF logs record, how to read terminatingRuleId and rate-based rule matches, and how Sazabi ingests web ACL logs from CloudWatch Logs.
- [Axiom MCP connector and CLI with Sazabi](https://www.sazabi.com/integrations/axiom.md): The Sazabi agent queries Axiom datasets in APL through the MCP connector and can run the axiom CLI in its sandbox for query, stream and ingest.
- [Background Job Failure Alerts, Automatically | Sazabi](https://www.sazabi.com/detection/background-job-failures.md): Sazabi opens an issue when a cron job skips, a queue backs up, a job retries in a loop or a sync goes stale. Sensors the agent writes for your jobs.
- [Better Stack MCP connector with the Sazabi agent](https://www.sazabi.com/integrations/better-stack.md): Connect Better Stack over OAuth so the Sazabi agent can read incidents, on-call context, uptime monitors and heartbeats, and build telemetry queries.
- [Better Stack Pricing Explained: Telemetry and On-Call](https://www.sazabi.com/guides/pricing/better-stack.md): Better Stack list prices by data region: responder seats, bundles, per-GB log ingestion and retention, uptime and status pages. Checked 8 Nov 2026.
- [BigCommerce Webhooks: Scopes, Payloads and Retries](https://www.sazabi.com/integrations/webhooks/bigcommerce.md): BigCommerce webhooks explained: store scopes, the light callback payload, creating a hook that posts to Sazabi, 48 hour retries and deactivation.
- [Blue/Green Deployment: Definition, Pros, and Cons](https://www.sazabi.com/glossary/blue-green-deployment.md): Blue/green deployment runs two identical environments and switches traffic between them. See how it works, how rollback works, and the database caveat.
- [BOLA Attack Detection: Spot Access Anomalies in API Logs](https://www.sazabi.com/guides/detect/access-anomalies.md): How to detect BOLA attacks and access anomalies: log actor and object, count distinct IDs per user, find sequential ID walks and ownership mismatches.
- [Bot and Scraper Alerts: Issues When Automation Hits You](https://www.sazabi.com/detection/bots-and-scraping.md): Sazabi spots scrapers, headless browsers and rotating-IP bots in your logs and opens an investigated issue. A built-in sensor, on by default.
- [Bot and Scraping Alerts From Your Request Logs | Sazabi](https://www.sazabi.com/detection/abuse-and-fraud.md): Sazabi opens an investigated issue when high-rate clients, headless browsers or rotating IPs show up in your logs. See what this category covers today.
- [Bot Detection: How to Spot Scrapers in Your Logs](https://www.sazabi.com/guides/detect/bots-and-scraping.md): Bot detection from your own logs: per-client rates, path coverage, headless user agents and rotating IPs, with queries, thresholds and what to do.
- [Browser-Specific Error Detection for Your App | Sazabi](https://www.sazabi.com/detection/segment-specific-behavior.md): Sazabi opens an issue when failures hit only one browser, OS, app version, region or customer. Group-level checks the agent writes. Example inside.
- [Business Flow Breakage Detection | Sazabi](https://www.sazabi.com/detection/business-flow-breakage.md): Sazabi opens an investigated issue when a key event vanishes, funnel conversion falls or signups and payments run far below usual. No dashboards to watch.
- [Business Metric Drift Alerts for Signups | Sazabi](https://www.sazabi.com/detection/business-metric-drift.md): Sazabi watches signups, applications, payments and messages by default and opens an investigated issue when volume is out of range for this hour.
- [Calendly MCP connector for the Sazabi agent](https://www.sazabi.com/integrations/calendly.md): The Sazabi agent uses Calendly's MCP tools to find scheduled events by invitee, read invitees and no-shows, and check slots when a booking flow fails.
- [Canary Deployment: Definition, Metrics, and Examples](https://www.sazabi.com/glossary/canary-deployment.md): A canary deployment sends a new release to a small share of production traffic first. See how it works, which metrics to judge it by, and how it compares.
- [Capacity Monitoring: Catch Resource Limits Early](https://www.sazabi.com/guides/detect/capacity-risks.md): Capacity monitoring for disks, memory, pools and quotas: what to log, a predict\_linear query, alert thresholds and pitfalls like sawtooth data.
- [Capacity Risk Alerts Before a Limit Is Hit | Sazabi](https://www.sazabi.com/detection/capacity-risks.md): Sazabi opens an issue when a connection pool, queue, quota or cardinality count heads toward a limit. Sensors the agent writes and backtests.
- [Cardinality in Metrics: What It Is and Why It Matters](https://www.sazabi.com/glossary/cardinality.md): Cardinality is the number of unique label combinations a metric has, and each one is a time series. See the math, Prometheus guidance, and how to cap it.
- [Cardinality Jump Alerts for Logs and Cache Keys | Sazabi](https://www.sazabi.com/detection/cardinality-jumps.md): Sazabi opens an issue when a field in your logs gains far more distinct values than usual, such as a cache key or user ID. Includes an example issue.
- [Cekura MCP: run voice agent tests from Sazabi](https://www.sazabi.com/integrations/cekura.md): Connect Cekura with an API key so the Sazabi agent can run evaluators with scenarios\_run, read result statuses and compare a failing run with service logs.
- [Certificate Expiration Monitoring: Catch Expiry Early](https://www.sazabi.com/guides/detect/expiring-certificates.md): SSL certificate expiry monitoring with probes, ACM metrics and an openssl check. Covers renewal failures, shortening lifetimes, tokens and thresholds.
- [Chargebee Webhooks: Send Billing Events to Sazabi](https://www.sazabi.com/integrations/webhooks/chargebee.md): Add a Chargebee webhook so subscription, invoice and payment events land in Sazabi as searchable JSON records. Setup, example payload and retry schedule.
- [Check Your Logs for Exploit Attempts After a CVE](https://www.sazabi.com/guides/security/exploit-attempts-after-cve.md): A new CVE is public. Decide if it is worth a hunt, set the log window, search with zgrep and jq, and separate failed attempts from real compromise.
- [Chronosphere vs Datadog: Pricing, Control and Fit](https://www.sazabi.com/compare/chronosphere-vs-datadog.md): Chronosphere prices what you keep after shaping, with no public list price. Datadog publishes per-host and per-GB rates. Compared 2026-11-08.
- [Circleback MCP connector for the Sazabi agent](https://www.sazabi.com/integrations/circleback.md): The Sazabi agent uses Circleback's MCP tools to search transcripts, read meeting notes and find action items that match an error it found in your logs.
- [Claude Code Monitoring and Coding Agent Observability](https://www.sazabi.com/integrations/categories/coding-agents.md): Ship session telemetry from Claude Code, Codex, Cursor, Gemini CLI, Copilot and more to Sazabi. See fields recorded, privacy settings and queries.
- [ClickUp Webhooks: Events, Payloads, Signature and Health](https://www.sazabi.com/integrations/webhooks/clickup.md): ClickUp webhooks explained: event names, the history\_items payload, creating a webhook through the API with a Sazabi URL and how health status works.
- [Client Error Detection for Web and Mobile Apps | Sazabi](https://www.sazabi.com/detection/client-errors.md): Sazabi opens an issue when users hit JavaScript exceptions, failed fetches or hydration errors in your web or React Native app. Setup is one SDK.
- [Clock Skew: How to Detect Timestamp Drift Between Hosts](https://www.sazabi.com/guides/detect/clock-skew.md): How to detect clock skew: read NTP offset, compare event time with arrival time, find effects stamped before causes and avoid mistaking lag for skew.
- [Cloud Logging and Cloud Log Management for Sazabi](https://www.sazabi.com/integrations/categories/cloud-platforms.md): Connect AWS, Google Cloud, Cloudflare, Vercel, Render, Netlify, Fly.io, Railway and others to Sazabi. Which path each platform uses and what it costs you.
- [Cloud Provider Error Alerts for AWS and GCP | Sazabi](https://www.sazabi.com/detection/cloud-provider-errors.md): Sazabi sets up detection for throttling and API errors from AWS or GCP in your logs, then opens an issue that says which service, which call and why.
- [Cloudflare Logs with Sazabi: Logpush and Workers](https://www.sazabi.com/integrations/cloudflare.md): Send Cloudflare Logpush datasets and Workers telemetry to Sazabi. Which source covers edge traffic, which covers your code, and what each one needs.
- [Cloudflare outage: 5xx errors, status feed and detection](https://www.sazabi.com/dependencies/cloudflare/outages.md): What a Cloudflare outage looks like from your side: branded vs unbranded 502/504, 52x codes, the status feed and how to detect an edge failure in logs.
- [Cloudflare Workers Logs and Traces in Sazabi](https://www.sazabi.com/integrations/cloudflare/workers.md): Add OTLP log and trace destinations in Cloudflare Workers Ob