# Sazabi ## Overview - [Introduction](https://docs.sazabi.com/index.md): Connect telemetry, ask production questions in plain language, and review detected issues with the supporting records and queries. ## Get started - [Introduction](https://docs.sazabi.com/get-started/index.md): What Sazabi is and how it works — so you know what you are setting up before you start. - [Philosophy](https://docs.sazabi.com/get-started/philosophy.md): The beliefs behind Sazabi — why observability is a conversation, why everything is a log, and who it is built for. - [Core concepts](https://docs.sazabi.com/get-started/core-concepts.md): The essential ideas you need on day zero — threads, the Sazabi agent, surfaces, log sources, issues, automations, the kinds of integrations, and the organization/project model. - [Quickstart](https://docs.sazabi.com/get-started/quickstart.md): Sign in, create an organization, choose a plan, create a project, send one real log, and ask the Sazabi agent your first question. About 10 minutes. - [Setup checklist](https://docs.sazabi.com/get-started/setup-checklist.md): The things to do to get a Sazabi project fully set up — connect your logs and code, wire up chat and your team, and run your first investigation. - [Production checklist](https://docs.sazabi.com/get-started/production-checklist.md): The "are we ready?" bridge before you rely on Sazabi in production — scope and rotate your keys, redact sensitive data, estimate volume, check limits, confirm retention, watch for silent failures, and plan for cost. - [Connect your coding agent](https://docs.sazabi.com/get-started/coding-agents.md): Connect a coding agent to Sazabi so it can investigate production while it writes code. Set up the CLI for terminal agents, or the MCP server for MCP clients. ## Guides ### Instrument - [Instrument](https://docs.sazabi.com/guides/instrument/index.md): Get your logs, metrics, and traces into Sazabi — connect a supported platform account or send to an endpoint — then verify data is flowing. - [Everything is a log](https://docs.sazabi.com/guides/instrument/everything-is-a-log.md): How Sazabi normalizes logs, metrics, traces, and webhook events into one searchable body of log records through a single intake. - [Choosing an ingestion path](https://docs.sazabi.com/guides/instrument/choosing-a-path.md): A decision guide for getting data into Sazabi — connect a supported account, run your own collectors, or instrument application code. - [The Intake page](https://docs.sazabi.com/guides/instrument/intake.md): Read the dashboard's Intake page — ingestion volume, rate, and per-source breakdown — to confirm data is flowing and spot anomalies. - [Log storage & retention](https://docs.sazabi.com/guides/instrument/storage.md): How Sazabi stores the data you send — managed storage, the retention window, the region your project uses, and how data leaves. - [Instrument your frontend](https://docs.sazabi.com/guides/instrument/frontend.md): Instrument a browser app with @sazabi/browser to capture errors, console output, network activity, and interaction events — or forward from a Sentry or PostHog SDK you already run. - [Instrument your mobile app](https://docs.sazabi.com/guides/instrument/react-native.md): Instrument a React Native or Expo app with @sazabi/react-native to capture errors, screens, touches, network activity, and console output, correlated with your backend logs. - [Send metrics](https://docs.sazabi.com/guides/instrument/metrics.md): Send OpenTelemetry or Prometheus metrics to Sazabi, where each data point is stored as a searchable log record, and confirm they arrive. - [Send traces](https://docs.sazabi.com/guides/instrument/traces.md): Send OpenTelemetry traces to Sazabi over OTLP, where spans are stored as searchable records the agent can correlate with your logs, and confirm they arrive. - [Send Kubernetes audit logs](https://docs.sazabi.com/guides/instrument/kubernetes-audit-logs.md): Send Kubernetes API audit logs from Amazon EKS, Google Kubernetes Engine, or a self-managed cluster to Sazabi, so you can see who exec'd into pods, read secrets, or changed RBAC. - [Manage log streams](https://docs.sazabi.com/guides/instrument/log-streams.md): Understand how log streams map to a log source, pause and resume a stream, delete one, and confirm the change took effect. - [Troubleshooting ingestion](https://docs.sazabi.com/guides/instrument/troubleshooting.md): Diagnose logs that don't show up, arrive malformed, or come in at the wrong volume — a checklist from the intake URL to the Intake page. ### Detect - [Detect](https://docs.sazabi.com/guides/detect/index.md): Sazabi detects issues automatically, notifies you, and lets you respond with automations, scripts, and a status page. - [Issues](https://docs.sazabi.com/guides/detect/issues.md): An issue is a problem Sazabi found and decided is worth your attention — with a lifecycle, a severity, and a place to respond. - [Service status](https://docs.sazabi.com/guides/detect/status.md): Track the health of your services from the issues Sazabi opens — components, how issues drive their status, and a timeline of the last week. - [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md): Route issue and system events to the right people and channels — personal channels by your own preference, shared channels by delivery rules. - [Manage scripts](https://docs.sazabi.com/guides/detect/scripts.md): Save a reusable bash script to a project, then run it or attach it to an automation. - [Create automations](https://docs.sazabi.com/guides/detect/automations.md): Run a script on a schedule, or let Sazabi run one when a signal fires — to monitor systems and open issues without being asked. - [Troubleshooting detection & notifications](https://docs.sazabi.com/guides/detect/troubleshooting.md): Diagnose why an issue wasn't detected, why one incident became several issues, or why a notification didn't arrive. ### Investigate - [Investigate](https://docs.sazabi.com/guides/investigate/index.md): Ask the Sazabi agent about your systems in a thread, search your logs directly, build dashboards, use the agent's tools and sandbox, and lean on project memory. - [Threads](https://docs.sazabi.com/guides/investigate/threads.md): Everything about threads — starting one, working across surfaces, visibility, sharing, forking, searching your history, and archiving. - [Working with the agent](https://docs.sazabi.com/guides/investigate/working-with-the-agent.md): How to work effectively with the Sazabi agent — the artifacts it produces, steering long investigations, prompting with project memory in mind, and referencing your project's objects. - [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md): The tools the Sazabi agent uses during an investigation — log search, web search, your code, issues, and integrations — and how to configure which are available. - [Log search](https://docs.sazabi.com/guides/investigate/log-search.md): Ask questions about your logs in plain language, get an answer with the query behind it, then rerun, page through, and list those queries from the CLI, a thread, MCP, or the API. - [Dashboards](https://docs.sazabi.com/guides/investigate/dashboards.md): Saved views of your logs. Keep a chart from a thread, investigate a panel in a conversation, or create dashboards with the agent, CLI, API, MCP, or Terraform. - [Set up the sandbox](https://docs.sazabi.com/guides/investigate/sandbox.md): Give the Sazabi agent command-line tools it can run in an isolated environment during an investigation — using sandbox CLIs or a custom CLI — and understand the security model. - [Use project memory](https://docs.sazabi.com/guides/investigate/memory.md): Give the Sazabi agent durable context that survives between investigations — browse, write, and organize project memory from the CLI. - [Chat outside the dashboard](https://docs.sazabi.com/guides/investigate/chat.md): Ask the Sazabi agent questions from Slack or Microsoft Teams by mentioning it in a channel, and follow the thread back to the dashboard. - [Troubleshooting investigations](https://docs.sazabi.com/guides/investigate/troubleshooting.md): Symptom-first fixes for the most common investigation problems — the agent cannot find logs you expect, answers reference the wrong service or time, or a thread stalls. ### Build - [Build](https://docs.sazabi.com/guides/build/index.md): How Sazabi helps with your code before production — reviewing pull requests, scanning for vulnerabilities, and opening fixes. - [Pull requests](https://docs.sazabi.com/guides/build/pull-requests.md): The three ways Sazabi works with your pull requests — opening one with a proposed fix, reviewing new ones, and answering questions from a comment. - [Security review](https://docs.sazabi.com/guides/build/security-review.md): How Sazabi scans your connected repositories for vulnerabilities and files confirmed findings as issues, and how to turn it off for a project. - [Set up automated code review](https://docs.sazabi.com/guides/build/automated-code-review.md): Have Sazabi review new pull requests on GitHub or Bitbucket with inline comments and a verdict. - [Set up logging review](https://docs.sazabi.com/guides/build/logging-review.md): Have Sazabi add the log lines a pull request is missing and fix the ones that will not help in production, as suggested changes, an on-demand commit or a batched commit. ### Administer - [Administer](https://docs.sazabi.com/guides/administer/index.md): Manage your organization, members, projects, access, single sign-on, keys, billing, and usage. - [Organizations](https://docs.sazabi.com/guides/administer/organizations.md): The organization is the boundary for your members, billing, integrations, and secret keys. - [Connected accounts](https://docs.sazabi.com/guides/administer/connected-accounts.md): Connect your personal vendor accounts so the Sazabi agent can act as you — and understand how that relates to organization integrations and which credential Sazabi uses. - [Access control](https://docs.sazabi.com/guides/administer/access-control.md): Organization roles, project access, and two-factor authentication in Sazabi. - [Pricing](https://docs.sazabi.com/guides/administer/pricing.md): What Sazabi charges for and how — token usage draws from prepaid credits, other metered usage is invoiced monthly. - [Credits](https://docs.sazabi.com/guides/administer/credits.md): How Sazabi credits work — the rollover guarantee, one-time and automatic top-ups, the cycle spending limit, and running out. - [Billing](https://docs.sazabi.com/guides/administer/billing.md): Manage your Sazabi plan and payments — plans, upgrades and downgrades, invoices, issue rejection, payment methods, failure recovery, and cancellation. - [Usage](https://docs.sazabi.com/guides/administer/usage.md): Track your organization's consumption in the dashboard — credit consumption and invoiced usage over time. - [Manage members](https://docs.sazabi.com/guides/administer/members.md): Invite people to your organization, assign roles, group them into teams, and remove access. - [Manage projects](https://docs.sazabi.com/guides/administer/projects.md): Create a project, choose its region, and switch between projects. - [Manage keys](https://docs.sazabi.com/guides/administer/keys.md): Create and manage public keys for log ingestion and secret keys for API and MCP access. - [Configure webhooks](https://docs.sazabi.com/guides/administer/webhooks.md): Send Sazabi notifications to your own HTTPS endpoint, secure the endpoint, and handle retries. - [Contact support](https://docs.sazabi.com/guides/administer/support.md): Reach Sazabi support from the dashboard or the CLI through a conversation with the agent, and know where the reply arrives. #### Single sign-on - [Single sign-on](https://docs.sazabi.com/guides/administer/single-sign-on/index.md): Let people sign in to Sazabi through your identity provider over SAML 2.0 or OpenID Connect, and manage members with SCIM. - [SSO enforcement](https://docs.sazabi.com/guides/administer/single-sign-on/enforcement.md): Require single sign-on for a verified domain, and keep a way back in with break-glass owners if your identity provider is down. - [SCIM provisioning](https://docs.sazabi.com/guides/administer/single-sign-on/scim.md): Let your identity provider add, update and remove the people in your Sazabi organization over SCIM 2.0. - [Add SSO domains](https://docs.sazabi.com/guides/administer/single-sign-on/domains.md): Claim the email domains your people use and prove you control them with a DNS TXT record. - [Configure SSO](https://docs.sazabi.com/guides/administer/single-sign-on/setup.md): Connect Okta, Microsoft Entra ID, Google Workspace or any SAML 2.0 or OIDC identity provider to Sazabi, and test the connection. - [Set up SCIM](https://docs.sazabi.com/guides/administer/single-sign-on/scim-setup.md): Turn on SCIM for your SSO connection and connect Okta, Microsoft Entra ID, OneLogin, PingOne or another SCIM 2.0 identity provider to it. - [Manage SCIM](https://docs.sazabi.com/guides/administer/single-sign-on/scim-manage.md): Rotate the SCIM token, pause and resume provisioning, turn on SCIM only, read the mismatch report and turn SCIM off. - [Troubleshooting SSO](https://docs.sazabi.com/guides/administer/single-sign-on/troubleshooting.md): Fix SSO sign-in, connection test and domain verification failures. - [Troubleshooting SCIM](https://docs.sazabi.com/guides/administer/single-sign-on/scim-troubleshooting.md): Fix SCIM provisioning failures from the status code and scimType your identity provider reports. ## Catalogs ### Log sources - [Log sources](https://docs.sazabi.com/catalogs/log-sources/index.md): Every supported log source, with native setup to connect your account or manual setup to send to an endpoint. #### Native: connect your account - [Native: connect your account](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/index.md): Native log sources let you authorize a supported platform account so Sazabi configures forwarding for you. - [AWS WAF](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/aws-waf.md): Connect your AWS account so Sazabi sets up subscription filters on your AWS WAF log groups and streams web ACL logs in real time. - [Cloudflare](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/cloudflare.md): Connect your Cloudflare account so Sazabi can automatically create and manage Logpush jobs for the datasets you select. - [AWS CloudWatch](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/cloudwatch.md): Connect your AWS account so Sazabi can set up subscription filters on your CloudWatch log groups and stream logs in real time. - [Convex](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/convex.md): Connect your Convex team so Sazabi can automatically configure a log stream on each deployment you select. - [DigitalOcean](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/digitalocean.md): Connect your DigitalOcean account so Sazabi can set up log forwarding on the App Platform apps you select. - [Google Cloud](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/gcp.md): Connect your Google Cloud account so Sazabi can provision a Cloud Logging sink, Pub/Sub topic, and pull subscription for each project, folder, or organization you select. - [Plain](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/plain.md): Connect your Plain workspace so Sazabi can manage a webhook target for the support event types you select. - [PostHog](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/posthog.md): Connect your PostHog account so Sazabi can install and manage a webhook destination for the projects you select. - [Render](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/render.md): Connect your Render account so Sazabi can configure a per-service log stream for each service you select. - [Sentry](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/sentry.md): Connect your Sentry organization so Sazabi can create an Internal Integration that streams issue, comment, and alert events in real time. - [Vercel](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/vercel.md): Connect your Vercel account so Sazabi can create and manage log, trace, and Web Analytics drains for the projects you select. - [Amazon VPC Flow Logs](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/aws-vpc-flow-logs.md): Connect your AWS account so Sazabi creates a flow log for each VPC you pick and streams its network traffic records in through CloudWatch Logs. - [AWS CloudTrail](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/cloudtrail.md): Connect your AWS account so Sazabi can subscribe to your trail's CloudWatch Logs group and stream CloudTrail events in real time. #### Manual: send to an endpoint - [Manual: send to an endpoint](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/index.md): Manual log sources provide an intake URL that you configure your platform, collector, SDK, or agent to send to. - [OpenTelemetry](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/opentelemetry.md): Set OTEL_EXPORTER_OTLP_ENDPOINT to your Sazabi intake URL to forward logs and traces from any OpenTelemetry SDK directly to Sazabi. - [OpenTelemetry Metrics](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/opentelemetry-metrics.md): Set OTEL_EXPORTER_OTLP_METRICS_ENDPOINT to your Sazabi intake URL to store OpenTelemetry metrics as searchable log records. - [OpenTelemetry Traces](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/opentelemetry-traces.md): Set OTEL_EXPORTER_OTLP_TRACES_ENDPOINT to your Sazabi intake URL to store every OpenTelemetry span, and every exception a span records, as a searchable log record. - [OpenTelemetry Collector](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/otel-collector.md): Add an otlphttp exporter to your OpenTelemetry Collector configuration to forward logs and traces from your infrastructure to Sazabi. - [Grafana Alloy](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/grafana-alloy.md): Add an otelcol.exporter.otlphttp component to your Grafana Alloy pipeline to forward logs and traces from your infrastructure to Sazabi. - [SigNoz](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/signoz.md): Add an otlphttp exporter to your SigNoz OpenTelemetry Collector to fan out logs and traces to Sazabi while SigNoz keeps receiving them. - [Fluent Bit](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/fluent-bit.md): Configure the Fluent Bit OpenTelemetry output plugin to forward container and host logs from your Kubernetes cluster or infrastructure to Sazabi. - [osquery](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/osquery.md): Ship osquery scheduled query results and osqueryd status logs from Linux and macOS hosts to Sazabi through an OpenTelemetry Collector or Fluent Bit. - [Vector](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/vector.md): Configure Vector's OpenTelemetry sink to forward logs and traces from your infrastructure to Sazabi using Vector's high-throughput observability pipeline. - [HashiCorp Vault](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/vault.md): Ship HashiCorp Vault audit device logs to Sazabi through Vector, with each request's path, operation, auth accessor and client IP indexed for search. - [Datadog Agent](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/datadog.md): Configure your Datadog Agent to forward logs to Sazabi alongside or instead of Datadog, using logs_config.additional_endpoints or a dedicated Sazabi-only endpoint. - [Prometheus](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/prometheus.md): Run an OpenTelemetry Collector with a prometheus receiver and otlphttp exporter to forward Prometheus metrics to Sazabi as searchable log records. - [Webhook Events](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/webhook-events.md): Point any vendor's webhooks at your Sazabi intake URL to store arbitrary JSON events as searchable log records with no schema or field mapping required. - [AWS API Gateway](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/aws-api-gateway.md): Send AWS API Gateway access and execution logs from CloudWatch Logs to Sazabi to see who calls which API, failed authorizations, and abusive clients. - [Linux auditd](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/auditd.md): Send Linux auditd records and journald auth messages to Sazabi through Fluent Bit or the OpenTelemetry Collector, with audit fields parsed into attributes. - [Palo Alto Networks](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/palo-alto.md): Forward Palo Alto Networks firewall traffic, threat, and system logs to Sazabi from Strata Logging Service HTTPS forwarding, a PAN-OS HTTP server profile, or syslog through a Vector collector. - [Cloudflare](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/cloudflare.md): Create a Cloudflare Logpush job with an HTTP destination pointed at your Sazabi intake URL to stream edge network logs to Sazabi. - [Cloudflare Workers](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/cloudflare-workers.md): Add OTLP log and trace destinations in Cloudflare Workers Observability settings and opt each Worker in via wrangler config to stream telemetry to Sazabi. - [AWS WAF](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/aws-waf.md): Run an OpenTelemetry Collector that reads your aws-waf-logs- CloudWatch log groups and forwards AWS WAF web ACL logs to Sazabi. - [Buildkite](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/buildkite.md): Turn on OpenTelemetry job log export on your self-hosted Buildkite agents to stream every job log line to Sazabi. - [Modal](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/modal.md): Point Modal's built-in OpenTelemetry integration at Sazabi to stream the logs of every Modal Function in your workspace, with no code changes. - [WarpBuild](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/warpbuild.md): Turn on WarpBuild's OTLP telemetry export to stream system logs and GitHub Actions logs from your WarpBuild runners to Sazabi. - [RunsOn](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/runs-on.md): Point your RunsOn stack's OpenTelemetry export at Sazabi to stream control-plane logs, traces and runner bootstrap logs. - [AWS CloudWatch](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/cloudwatch.md): Run an OpenTelemetry Collector with the awscloudwatch receiver and an otlphttp exporter to forward CloudWatch log group data to Sazabi. - [Convex](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/convex.md): Create a Convex webhook log stream with your Sazabi intake URL as the destination to forward deployment logs from your Convex functions to Sazabi. - [Daytona](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/daytona.md): Set your Sazabi intake URL as the OTLP endpoint in Daytona organization settings to stream logs and traces from every sandbox in the organization. - [DigitalOcean](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/digital-ocean.md): Add a Datadog log forwarding destination to your DigitalOcean App Platform app and point it at your Sazabi intake URL to forward application logs. - [E2B](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/e2b.md): Wire an OpenTelemetry log exporter into the host process that creates E2B sandboxes to capture stdout and stderr from sandbox code execution and forward them to Sazabi. - [Elastic Cloud](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/elastic-cloud.md): Use Elastic Agent in OpenTelemetry Collector mode or a self-managed Logstash pipeline to forward logs from your Elastic Cloud deployment to Sazabi. - [evlog](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/evlog.md): Send evlog wide events and structured errors from your TypeScript app to Sazabi with evlog's built-in Sazabi drain. - [Fly.io](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/fly-io.md): Run a fly-log-shipper or Vector app inside your Fly organization pointed at your Sazabi intake URL to forward application logs from all Fly apps. - [Google Cloud](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/gcp.md): Set up your own Cloud Logging sink, Pub/Sub topic, and OpenTelemetry Collector to forward GCP logs to Sazabi without connecting a service account. - [Inngest](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/inngest.md): Instrument the application that hosts your Inngest functions with the OpenTelemetry SDK and point it at a Sazabi endpoint to forward logs and traces. - [Jenkins](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/jenkins.md): Send Jenkins Pipeline build logs and traces to Sazabi with the Jenkins OpenTelemetry plugin, configured in the Jenkins UI or with Configuration as Code. - [LangChain](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/langchain.md): Add OpenInference instrumentation to your LangChain application and point it at a Sazabi endpoint to forward chain, tool, and LLM call traces. - [Mastra](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/mastra.md): Add Sazabi as a custom OTLP exporter in your Mastra observability config to stream agent traces directly to Sazabi. - [Neon](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/neon.md): Point Neon's built-in OpenTelemetry log export at a Sazabi endpoint to forward Postgres logs from your Neon project without deploying an agent. - [New Relic Browser](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/new-relic-browser.md): Point the New Relic browser agent at Sazabi to ship the browser logs and JavaScript errors it already captures. - [Netlify](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/netlify.md): Configure a Netlify log drain pointed at a Sazabi endpoint to forward build, function, edge, and traffic logs in near real time. - [Northflank](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/northflank.md): Create a Northflank HTTP log sink pointed at your Sazabi intake URL to forward runtime logs from your services, jobs, add-ons, and sandboxes. - [OpenRouter](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/openrouter.md): Enable Broadcast in the OpenRouter dashboard and set your Sazabi intake URL as the OpenTelemetry Collector destination to receive an LLM trace span per generation. - [Plain](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/plain.md): Create a Plain webhook target pointed at your Sazabi intake URL to stream support events into Sazabi without sharing a Plain API key. - [Porter](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/porter.md): Add OpenTelemetry environment variables to your Porter service and initialize the SDK to send application logs and traces directly to Sazabi. - [PostHog](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/posthog.md): Create an HTTP Webhook destination in PostHog's Data Pipeline pointed at your Sazabi intake URL to forward product analytics events. - [PostHog SDK](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/posthog-sdk.md): Configure a reverse proxy to send posthog-js browser capture traffic to a Sazabi endpoint instead of PostHog. - [Railway](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/railway.md): Set Railway environment variables and bootstrap the OpenTelemetry SDK on your service to send application logs and traces directly to Sazabi. - [Render](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/render.md): Add a workspace-wide Render log stream pointed at Sazabi to forward service logs without connecting a Render API key. - [Respan](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/respan.md): Point the Respan SDK at your Sazabi intake URL to stream auto-instrumented LLM and agent traces into Sazabi. - [Sazabi Browser SDK](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sazabi-browser-sdk.md): Capture browser sessions — navigation, clicks, errors, and network calls with trace context — with the Sazabi browser SDK. - [Sazabi React Native SDK](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sazabi-react-native-sdk.md): Capture mobile sessions with the Sazabi React Native SDK, including screens, touches, errors, and network calls with trace context. - [Sentry](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry.md): Create a Sentry Internal Integration pointed at your Sazabi intake URL to stream Sentry issue, comment, and alert events into Sazabi. - [Sentry SDK](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry-sdk.md): Point your Sentry SDK at a Sazabi DSN to forward errors, structured logs, and envelope telemetry — either replacing your Sentry project DSN or sending to both. - [Supabase](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/supabase.md): Add an OpenTelemetry log drain in the Supabase dashboard pointed at your Sazabi intake URL to forward Postgres, Auth, and Edge Function logs. - [Temporal](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/temporal.md): Add the OpenTelemetry SDK to your Temporal worker processes and point it at a Sazabi endpoint to forward worker logs and workflow and activity traces. - [Trigger.dev](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/trigger-dev.md): Add an OTLP log exporter in trigger.config.ts pointed at your Sazabi intake URL to stream Trigger.dev task logs into Sazabi. - [Vercel](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/vercel.md): Create a Vercel log drain pointed at your Sazabi intake URL to forward deployment logs from serverless functions, edge functions, and static builds. - [Unkey](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/unkey.md): Add an HTTP log drain in the Unkey dashboard pointed at your Sazabi intake URL to forward API key verifications, rate limits, audit logs, gateway requests, and runtime logs. - [Doppler](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/doppler.md): Connect Doppler's Generic HTTPS logging service to your Sazabi intake URL to forward Activity Logs that show who read or changed secrets, configs, and workplace access. - [Tailscale](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/tailscale.md): Stream Tailscale configuration audit logs and network flow logs to Sazabi through Tailscale log streaming. - [Jamf Pro](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/jamf-pro.md): Create Jamf Pro webhooks pointed at your Sazabi intake URL to stream device enrollment, inventory, policy, smart group, and API activity events. - [Okta](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/okta.md): Stream the Okta System Log to Sazabi with Okta Log Streaming and Amazon EventBridge to monitor sign-ins, MFA changes, admin actions, and suspicious sessions. - [Auth0](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/auth0.md): Create a Custom Webhook log stream in Auth0 pointed at your Sazabi intake URL to stream logins, failed logins, signups, MFA, password resets, attack protection blocks, and Management API calls. - [Zscaler](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/zscaler.md): Add Zscaler Cloud NSS feeds pointed at a Sazabi endpoint to stream Zscaler Internet Access web, firewall, and DNS logs. - [New Relic](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/new-relic.md): Point the New Relic infrastructure agent, Kubernetes logging chart, or New Relic Fluent Bit plugin at Sazabi to forward the logs it already collects. - [WorkOS](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/workos.md): Add a webhook endpoint in the WorkOS dashboard pointed at your Sazabi intake URL to forward authentication, SSO connection, directory sync, user, session, and organization events. - [SentinelOne](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentinelone.md): Forward SentinelOne threats and alerts to your Sazabi intake URL from a Singularity Hyperautomation workflow. - [AWS GuardDuty](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/aws-guardduty.md): Send Amazon GuardDuty findings to Sazabi in near real time with an Amazon EventBridge rule and API destination in each Region. - [GitHub Audit Log](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/github-audit-log.md): Stream your GitHub Enterprise Cloud audit log, including Git events, to Sazabi through GitHub's Splunk audit log streaming target. - [Amazon VPC Flow Logs](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/aws-vpc-flow-logs.md): Run an OpenTelemetry Collector with the awscloudwatch receiver to forward the VPC flow logs you publish to CloudWatch Logs to Sazabi. - [AWS CloudTrail](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/cloudtrail.md): Run an OpenTelemetry Collector with the awscloudwatch receiver on your trail's CloudWatch Logs group and export CloudTrail events to Sazabi over OTLP. #### Agent telemetry - [Agent telemetry](https://docs.sazabi.com/catalogs/log-sources/coding-agents/index.md): Send telemetry from the coding agents your team uses, such as Claude Code, Codex, and Cursor, to Sazabi. - [Claude Code](https://docs.sazabi.com/catalogs/log-sources/coding-agents/claude-code.md): Ship Claude Code session telemetry — prompts, tool calls, and model API requests with token counts — to Sazabi from the CLI, Claude Code on the web, and GitHub Actions. - [Codex](https://docs.sazabi.com/catalogs/log-sources/coding-agents/codex.md): Add an [otel] section to your Codex config to ship session telemetry — prompts, tool calls, and model API requests — to Sazabi via Codex's built-in OTLP exporter. - [Cursor](https://docs.sazabi.com/catalogs/log-sources/coding-agents/cursor.md): Add one OpenTelemetry Export destination in Cursor Team Settings to ship your team's Cursor agent telemetry — model requests with token counts, errors, skills, hooks, and Cloud Agent commits and pull requests — to Sazabi. - [Devin CLI](https://docs.sazabi.com/catalogs/log-sources/coding-agents/devin-cli.md): Add an otel block to your Devin CLI config to ship session telemetry — prompts, tool calls, and model API requests with token counts — to Sazabi. - [Factory Droid](https://docs.sazabi.com/catalogs/log-sources/coding-agents/factory-droid.md): Pin a telemetry block in Factory's org-managed settings to ship Factory Droid usage metrics, or GenAI spans for every turn, model call, and tool run, to Sazabi. - [Gemini CLI](https://docs.sazabi.com/catalogs/log-sources/coding-agents/gemini-cli.md): Add a telemetry block to your Gemini CLI settings to ship session telemetry — prompts, tool calls, and model API requests with token counts — to Sazabi via Gemini CLI's built-in OTLP exporter. - [GitHub Copilot](https://docs.sazabi.com/catalogs/log-sources/coding-agents/github-copilot.md): Point GitHub Copilot's built-in OpenTelemetry exporter at Sazabi to ship Copilot CLI and VS Code agent traces and events — model, token usage, and tool calls, with no prompt text by default. - [oh-my-pi](https://docs.sazabi.com/catalogs/log-sources/coding-agents/oh-my-pi.md): Export the standard OTEL environment variables for oh-my-pi (omp) to ship coding-agent session spans — model, provider, token usage, and cost, with no prompt text — to Sazabi. - [OpenHands](https://docs.sazabi.com/catalogs/log-sources/coding-agents/openhands.md): Export the OpenTelemetry trace variables for OpenHands to ship agent session traces — conversation runs, agent steps, tool calls, and LLM requests — to Sazabi as searchable logs. - [Hermes Agent](https://docs.sazabi.com/catalogs/log-sources/coding-agents/hermes-agent.md): Install the traceverse OpenTelemetry plugin in Hermes Agent to ship sessions, prompts, model responses with tokens and cost, and tool results to Sazabi as searchable logs. - [OpenClaw](https://docs.sazabi.com/catalogs/log-sources/coding-agents/openclaw.md): Enable OpenClaw's official diagnostics-otel plugin to ship agent runs, model calls with token usage, tool executions, message flow, and Gateway logs to Sazabi as searchable logs. - [Claude Agent SDK](https://docs.sazabi.com/catalogs/log-sources/coding-agents/claude-agent-sdk.md): Pass OTEL environment variables through the Claude Agent SDK's env option to ship telemetry from your agents — prompts, tool calls, and model API requests with token counts and cost — to Sazabi. ### Integrations - [Integrations](https://docs.sazabi.com/catalogs/integrations/index.md): Connect source control, chat, work tracking, and incident tools at the organization level so the Sazabi agent can search code, reply where your team works, and route issues. - [GitHub](https://docs.sazabi.com/catalogs/integrations/github.md): Connect GitHub so the Sazabi agent can search your code during investigations, and optionally review new pull requests. - [Bitbucket](https://docs.sazabi.com/catalogs/integrations/bitbucket.md): Connect a Bitbucket workspace so the Sazabi agent can search your code during investigations. - [GitCafe](https://docs.sazabi.com/catalogs/integrations/gitcafe.md): Connect GitCafe so the Sazabi agent can search your code, work on it in sandboxes, open pull requests, and review them. - [Slack](https://docs.sazabi.com/catalogs/integrations/slack.md): Connect Slack so your team gets issue notifications with inline actions, chats with the Sazabi agent, and shares context without leaving Slack. - [Microsoft Teams](https://docs.sazabi.com/catalogs/integrations/microsoft-teams.md): Connect Microsoft Teams so your team can mention the Sazabi agent to investigate and receive issue notifications in Teams channels. - [Discord](https://docs.sazabi.com/catalogs/integrations/discord.md): Post Sazabi issue alerts to Discord channels with Add to Discord or a channel webhook URL. - [Discord bot](https://docs.sazabi.com/catalogs/integrations/discord-bot.md): Add the Sazabi bot to your Discord server so your team can mention it, message it directly, or use /sazabi to investigate without leaving Discord. - [Linear](https://docs.sazabi.com/catalogs/integrations/linear.md): Connect Linear so the Sazabi agent can file issues into your Linear workspace. - [Jira](https://docs.sazabi.com/catalogs/integrations/jira.md): Connect Atlassian Jira so the Sazabi agent can file issues into your Jira site. - [incident.io](https://docs.sazabi.com/catalogs/integrations/incident-io.md): Connect incident.io so Sazabi can route issues to an incident.io alert source. - [PagerDuty](https://docs.sazabi.com/catalogs/integrations/pagerduty.md): Connect PagerDuty so Sazabi can route issues to your services as PagerDuty alerts. - [Rootly](https://docs.sazabi.com/catalogs/integrations/rootly.md): Connect Rootly so Sazabi can route issues to your Rootly alerting targets. - [Better Stack](https://docs.sazabi.com/catalogs/integrations/better-stack.md): Connect Better Stack on-call so Sazabi can open and resolve Better Stack incidents for issues. - [Splunk On-Call](https://docs.sazabi.com/catalogs/integrations/victorops.md): Connect Splunk On-Call (VictorOps) so Sazabi can route issues to your on-call rotation. #### Cloud agents - [Capy](https://docs.sazabi.com/catalogs/integrations/capy.md): Connect Capy so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Claude Agent](https://docs.sazabi.com/catalogs/integrations/claude.md): Connect Claude Agent so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Codex](https://docs.sazabi.com/catalogs/integrations/codex.md): Connect Codex so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Cursor](https://docs.sazabi.com/catalogs/integrations/cursor.md): Connect Cursor so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Devin](https://docs.sazabi.com/catalogs/integrations/devin.md): Connect Devin so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Hoplite](https://docs.sazabi.com/catalogs/integrations/hoplite.md): Connect Hoplite so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Replicas](https://docs.sazabi.com/catalogs/integrations/replicas.md): Connect Replicas so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Tembo](https://docs.sazabi.com/catalogs/integrations/tembo.md): Connect Tembo so Sazabi can hand issue fixes to it and follow the result in the issue thread. - [Warp Oz](https://docs.sazabi.com/catalogs/integrations/warp.md): Connect Warp Oz so Sazabi can hand issue fixes to it and follow the result in the issue thread. ### MCP connectors - [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors/index.md): Give the Sazabi agent tools from external services through the Model Context Protocol. #### Observability and monitoring - [Axiom](https://docs.sazabi.com/catalogs/mcp-connectors/axiom.md): Give the Sazabi agent tools to query your observability datasets and logs using APL directly from agent conversations. - [Better Stack](https://docs.sazabi.com/catalogs/mcp-connectors/better-stack.md): Give the Sazabi agent tools to investigate incidents, monitors, and log sources, and build telemetry queries directly from agent conversations. - [Datadog](https://docs.sazabi.com/catalogs/mcp-connectors/datadog.md): Give the Sazabi agent tools to query Datadog metrics, logs, traces, monitors, dashboards, and incidents using your Datadog site URL, API key, and Application Key. - [down.guide](https://docs.sazabi.com/catalogs/mcp-connectors/down-guide.md): Give the Sazabi agent tools to check whether a cloud, SaaS, or developer provider is down, browse recent provider incidents, and check a project's dependencies for live provider problems. On by default in every project. - [Elastic Cloud](https://docs.sazabi.com/catalogs/mcp-connectors/elastic-cloud.md): Give the Sazabi agent tools to search Elasticsearch indices and query Agent Builder tools from your Kibana-hosted MCP endpoint. - [Grafana Cloud](https://docs.sazabi.com/catalogs/mcp-connectors/grafana.md): Give the Sazabi agent tools to browse dashboards, query metrics, logs, and traces, and review alerts and incidents across your Grafana Cloud stack. - [Honeycomb](https://docs.sazabi.com/catalogs/mcp-connectors/honeycomb.md): Give the Sazabi agent tools to query Honeycomb environments, datasets, columns, boards, triggers, and SLOs, and create or update boards and triggers. - [incident.io](https://docs.sazabi.com/catalogs/mcp-connectors/incident-io.md): Give the Sazabi agent tools to browse incidents, alerts, and on-call schedules from your incident.io organization. - [PagerDuty](https://docs.sazabi.com/catalogs/mcp-connectors/pagerduty.md): Give the Sazabi agent read-only tools to look up PagerDuty incidents, alerts, services, on-call schedules, escalation policies, and change events. - [PostHog](https://docs.sazabi.com/catalogs/mcp-connectors/posthog.md): Give the Sazabi agent tools to query analytics data, feature flags, and experiment results from your PostHog organization. - [Pydantic Logfire](https://docs.sazabi.com/catalogs/mcp-connectors/logfire.md): Give the Sazabi agent tools to query OpenTelemetry traces and metrics, surface recent exceptions, and browse projects, alerts, and dashboards in Logfire. - [Sentry](https://docs.sazabi.com/catalogs/mcp-connectors/sentry.md): Give the Sazabi agent tools to browse error events, issues, and project data across your Sentry organizations. - [SigNoz](https://docs.sazabi.com/catalogs/mcp-connectors/signoz.md): Give the Sazabi agent tools to query metrics, logs, traces, alerts, and dashboards while investigating production issues. #### AI and LLM observability - [AgentCat](https://docs.sazabi.com/catalogs/mcp-connectors/agentcat.md): Give the Sazabi agent tools to review AgentCat agent usage, sessions, issues, and performance metrics. - [Arize AX](https://docs.sazabi.com/catalogs/mcp-connectors/arize.md): Give the Sazabi agent read access to your Arize AX traces, datasets, experiments, evaluators, monitors, and prompts. - [Braintrust](https://docs.sazabi.com/catalogs/mcp-connectors/braintrust.md): Give the Sazabi agent tools to query your Braintrust experiments, datasets, prompts, and logs directly from agent conversations. - [Cekura](https://docs.sazabi.com/catalogs/mcp-connectors/cekura.md): Give the Sazabi agent tools to test, monitor, and evaluate AI agent workflows directly from agent conversations. - [Langfuse](https://docs.sazabi.com/catalogs/mcp-connectors/langfuse.md): Give the Sazabi agent tools to inspect LLM traces, observations, metrics, scores, comments, and prompts from your Langfuse project. - [LangSmith](https://docs.sazabi.com/catalogs/mcp-connectors/langsmith.md): Give the Sazabi agent tools to query LLM tracing projects, runs, datasets, and evaluations from your LangSmith organization. - [Respan](https://docs.sazabi.com/catalogs/mcp-connectors/respan.md): Give the Sazabi agent tools to query LLM request logs, execution traces, prompts, and customer data from your Respan account. - [The Context Company](https://docs.sazabi.com/catalogs/mcp-connectors/the-context-company.md): Give the Sazabi agent read-only observability tools to query agent insights, runs, and sessions. #### Cloud and infrastructure - [AWS](https://docs.sazabi.com/catalogs/mcp-connectors/aws.md): Give the Sazabi agent tools to search AWS documentation and run AWS API operations using your own IAM credentials. - [Cloudflare](https://docs.sazabi.com/catalogs/mcp-connectors/cloudflare.md): Give the Sazabi agent access to Workers logs and analytics, DNS, zones, Audit Logs, bindings, builds, Radar insights, and Cloudflare One CASB findings through Cloudflare's hosted MCP servers. - [Cloudflare (API token)](https://docs.sazabi.com/catalogs/mcp-connectors/cloudflare-api-token.md): Give the Sazabi agent access to Cloudflare Workers, DNS, zones, Audit Logs, and more through the hosted Cloudflare API MCP server, authenticated with an API token you mint yourself. - [Google Cloud (GCP)](https://docs.sazabi.com/catalogs/mcp-connectors/gcp.md): Give the Sazabi agent tools to query Cloud Logging, Cloud Monitoring, BigQuery, and other Google Cloud products using a Google OAuth 2.0 Bearer access token. - [Porter](https://docs.sazabi.com/catalogs/mcp-connectors/porter.md): Give the Sazabi agent tools to read Porter application logs, metrics, deploy status, and cluster state, and to manage Porter apps. - [Railway](https://docs.sazabi.com/catalogs/mcp-connectors/railway.md): Give the Sazabi agent tools to inspect and manage Railway projects, services, deployments, environment variables, and logs. - [Render](https://docs.sazabi.com/catalogs/mcp-connectors/render.md): Give the Sazabi agent tools to inspect and manage Render services, deploys, environment variables, logs, and metrics. - [Rivet](https://docs.sazabi.com/catalogs/mcp-connectors/rivet.md): Give the Sazabi agent tools to inspect actors, call actions, open the Actor Inspector, and manage compute pools in Rivet. #### Databases and data - [Airbyte](https://docs.sazabi.com/catalogs/mcp-connectors/airbyte.md): Give the Sazabi agent tools to read and write records from the third-party platforms you have already connected in your Airbyte Agent Engine workspace. - [Neon](https://docs.sazabi.com/catalogs/mcp-connectors/neon.md): Give the Sazabi agent tools to manage serverless Postgres databases and branches and to run SQL queries in your Neon account. - [PlanetScale](https://docs.sazabi.com/catalogs/mcp-connectors/planetscale.md): Give the Sazabi agent tools to query databases, inspect schema, and explore Insights data in your PlanetScale organization. - [Supabase](https://docs.sazabi.com/catalogs/mcp-connectors/supabase.md): Give the Sazabi agent tools to manage organizations, projects, and databases, and to run SQL queries. #### Developer tools - [Clerk](https://docs.sazabi.com/catalogs/mcp-connectors/clerk.md): Give the Sazabi agent tools to work with your Clerk applications, instance configuration, users, and domains, and to pull Clerk SDK snippets. - [Composio](https://docs.sazabi.com/catalogs/mcp-connectors/composio.md): Give the Sazabi agent tools from the Composio toolkits and connected apps you have configured, through a single hosted MCP endpoint. - [Context.dev](https://docs.sazabi.com/catalogs/mcp-connectors/context-dev.md): Give the Sazabi agent tools to resolve brand data, scrape and crawl websites into LLM-ready Markdown, extract structured data, and manage website-change monitors. - [DeepWiki](https://docs.sazabi.com/catalogs/mcp-connectors/deepwiki.md): Give the Sazabi agent tools to search public GitHub repository documentation and ask natural-language questions about open-source code. - [Exa](https://docs.sazabi.com/catalogs/mcp-connectors/exa.md): Give the Sazabi agent tools to search the web, research companies, crawl pages, and run deep research using Exa's hosted MCP server. - [GrowthBook](https://docs.sazabi.com/catalogs/mcp-connectors/growthbook.md): Give the Sazabi agent tools to manage feature flags, experiments, metrics, and environments in GrowthBook. - [Mobbin](https://docs.sazabi.com/catalogs/mcp-connectors/mobbin.md): Give the Sazabi agent tools to search UI screens, user flows, and website sections from leading mobile and web applications for design inspiration. - [Replicas](https://docs.sazabi.com/catalogs/mcp-connectors/replicas.md): Give the Sazabi agent tools to create and steer Replicas cloud coding-agent workspaces, chats, environments, and automations. - [Resend](https://docs.sazabi.com/catalogs/mcp-connectors/resend.md): Give the Sazabi agent tools to send transactional and broadcast emails and manage domains, contacts, and audiences. #### Security and compliance - [cve.now](https://docs.sazabi.com/catalogs/mcp-connectors/cve-now.md): Give the Sazabi agent tools to look up CVE, GHSA, and OSV vulnerabilities, browse cve.now feeds, and check a project's dependencies against known vulnerabilities. On by default in every project. - [Drata](https://docs.sazabi.com/catalogs/mcp-connectors/drata.md): Give the Sazabi agent read-only tools to look up Drata controls, monitoring tests, evidence, policies, risks, vendors, personnel, and devices. - [GitGuardian](https://docs.sazabi.com/catalogs/mcp-connectors/gitguardian.md): Give the Sazabi agent read-only tools to look up GitGuardian secret incidents, occurrences, sources, and the remediation workflow. - [Google Security Operations](https://docs.sazabi.com/catalogs/mcp-connectors/google-secops.md): Give the Sazabi agent tools to search Google SecOps cases, alerts, entities, UDM events, rules, and detections while investigating a security signal. - [Have I Been Pwned](https://docs.sazabi.com/catalogs/mcp-connectors/hibp.md): Give the Sazabi agent tools to look up public data breaches, the data they exposed, and whether a password appears in known breaches. On by default in every project. - [Secureframe](https://docs.sazabi.com/catalogs/mcp-connectors/secureframe.md): Give the Sazabi agent tools to query and manage compliance data, controls, automated tests, vendors, risks, and framework requirements. - [Semgrep](https://docs.sazabi.com/catalogs/mcp-connectors/semgrep.md): Give the Sazabi agent read-only tools to search Semgrep Code, Supply Chain, and Secrets findings, scans, projects, and advisories in your Semgrep organization. - [Socket](https://docs.sazabi.com/catalogs/mcp-connectors/socket.md): Give the Sazabi agent read-only tools to check dependency risk scores, supply-chain alerts, and the threat feed for your Socket organization. - [Tines](https://docs.sazabi.com/catalogs/mcp-connectors/tines.md): Give the Sazabi agent read-only tools to look up the stories and actions in your Tines tenant. - [Vanta](https://docs.sazabi.com/catalogs/mcp-connectors/vanta.md): Give the Sazabi agent read-only tools to look up Vanta compliance tests, controls, frameworks, vendors, risks, vulnerabilities, and documents as evidence. - [VirusTotal](https://docs.sazabi.com/catalogs/mcp-connectors/virustotal.md): Give the Sazabi agent tools to check file hashes, URLs, domains, and IP addresses against VirusTotal reports while investigating a security signal. - [Wiz](https://docs.sazabi.com/catalogs/mcp-connectors/wiz.md): Give the Sazabi agent read-only access to the Wiz Security Graph for cloud exposure, attack paths, vulnerabilities, and runtime threat context. - [WorkOS](https://docs.sazabi.com/catalogs/mcp-connectors/workos.md): Give the Sazabi agent read-only tools to look up the organizations, users, SSO connections, and directories behind an authentication signal in your WorkOS workspace. #### Work and knowledge - [Atlassian](https://docs.sazabi.com/catalogs/mcp-connectors/atlassian.md): Give the Sazabi agent tools to search and manage Jira, Confluence, Jira Service Management, Compass, and Bitbucket from your workflow. - [Calendly](https://docs.sazabi.com/catalogs/mcp-connectors/calendly.md): Give the Sazabi agent tools to check availability, create scheduling links, and manage meetings directly from agent conversations. - [Circleback](https://docs.sazabi.com/catalogs/mcp-connectors/circleback.md): Give the Sazabi agent tools to search and read your meeting notes, transcripts, and action items. - [Granola](https://docs.sazabi.com/catalogs/mcp-connectors/granola.md): Give the Sazabi agent tools to search and browse your AI-powered meeting notes, transcripts, and folders. - [Linear](https://docs.sazabi.com/catalogs/mcp-connectors/linear.md): Give the Sazabi agent tools to browse and manage issues, projects, and roadmaps in your Linear workspace. - [Notion](https://docs.sazabi.com/catalogs/mcp-connectors/notion.md): Give the Sazabi agent tools to search and work with your Notion pages, databases, and workspace content. - [Superhuman](https://docs.sazabi.com/catalogs/mcp-connectors/superhuman.md): Give the Sazabi agent tools to search, draft, send, and triage emails from your Superhuman Mail inbox. #### Customers, sales, and finance - [Attio](https://docs.sazabi.com/catalogs/mcp-connectors/attio.md): Give the Sazabi agent tools to search and manage your CRM records, workspace data, and relationship intelligence without leaving your workflow. - [Autumn](https://docs.sazabi.com/catalogs/mcp-connectors/autumn.md): Give the Sazabi agent tools to inspect and manage your billing and pricing — customers, plans, features, balances, usage, and subscriptions — from agent conversations. - [Clay](https://docs.sazabi.com/catalogs/mcp-connectors/clay.md): Give the Sazabi agent tools to search contacts, interactions, and workspace workflows, and create or update records and workflows, for enriched prospecting and relationship data. - [Happenstance](https://docs.sazabi.com/catalogs/mcp-connectors/happenstance.md): Give the Sazabi agent tools to search your professional network and find warm introduction paths to the people you want to reach. - [Intercom](https://docs.sazabi.com/catalogs/mcp-connectors/intercom.md): Give the Sazabi agent tools to read support conversations, contacts, and help center content from your Intercom workspace. - [Mercury](https://docs.sazabi.com/catalogs/mcp-connectors/mercury.md): Give the Sazabi agent tools to search banking context such as accounts, cards, recipients, transactions, treasury records, and organization data in Mercury. - [Plain](https://docs.sazabi.com/catalogs/mcp-connectors/plain.md): Give the Sazabi agent tools to search and manage support threads, customers, and tenants from your Plain workspace. - [Plain (API key)](https://docs.sazabi.com/catalogs/mcp-connectors/plain-api-token.md): Give the Sazabi agent tools to search and manage Plain support threads and customers using a Plain API key instead of OAuth. - [Pylon](https://docs.sazabi.com/catalogs/mcp-connectors/pylon.md): Give the Sazabi agent tools to search and manage support issues, customer accounts, and contacts from your Pylon workspace. - [Stripe MCP](https://docs.sazabi.com/catalogs/mcp-connectors/stripe.md): Give the Sazabi agent tools to query and manage payments, customers, subscriptions, invoices, and billing. #### Other - [Herd](https://docs.sazabi.com/catalogs/mcp-connectors/herd.md): Give the Sazabi agent tools to research contracts, wallets, transactions, and on-chain workflows through Herd. - [RentAHuman](https://docs.sazabi.com/catalogs/mcp-connectors/rentahuman.md): Give the Sazabi agent tools to hire and coordinate real human workers for tasks requiring human judgment or real-world action. - [X](https://docs.sazabi.com/catalogs/mcp-connectors/x.md): Give the Sazabi agent tools to search posts and access real-time X data from your X developer app. ### Sandbox CLIs - [Sandbox CLIs](https://docs.sazabi.com/catalogs/sandbox-clis/index.md): Command-line tools the Sazabi agent can run in its sandbox, and how to connect their credentials. #### Cloud and infrastructure - [Aiven](https://docs.sazabi.com/catalogs/sandbox-clis/aiven.md): Give the Sazabi agent the Aiven CLI (avn) in its sandbox to manage Aiven services and projects. - [Argo CD](https://docs.sazabi.com/catalogs/sandbox-clis/argocd.md): Give the Sazabi agent the Argo CD CLI (argocd) in its sandbox to inspect application sync status, health, and rollouts. - [AWS](https://docs.sazabi.com/catalogs/sandbox-clis/aws.md): Give the Sazabi agent the AWS CLI (aws) in its sandbox to interact with AWS services using access keys or an assumed role. - [Azure](https://docs.sazabi.com/catalogs/sandbox-clis/azure-cli.md): Give the Sazabi agent the Azure CLI (az) in its sandbox to interact with Azure resources using a service principal for non-interactive access. - [Cloudflare (cf)](https://docs.sazabi.com/catalogs/sandbox-clis/cf.md): Give the Sazabi agent the Cloudflare CLI (cf) in its sandbox to manage zones, DNS, and security rules. - [DigitalOcean](https://docs.sazabi.com/catalogs/sandbox-clis/digitalocean.md): Give the Sazabi agent the DigitalOcean CLI (doctl) in its sandbox to manage DigitalOcean resources with a personal access token. - [Fly.io](https://docs.sazabi.com/catalogs/sandbox-clis/fly.md): Give the Sazabi agent the Fly.io CLI (flyctl) in its sandbox to deploy and manage Fly.io applications. - [Google Cloud](https://docs.sazabi.com/catalogs/sandbox-clis/gcloud.md): Give the Sazabi agent the Google Cloud CLI (gcloud) in its sandbox to manage Google Cloud resources with a service account. - [Heroku](https://docs.sazabi.com/catalogs/sandbox-clis/heroku.md): Give the Sazabi agent the Heroku CLI (heroku) in its sandbox to manage apps, dynos, releases, and logs. - [Kubernetes](https://docs.sazabi.com/catalogs/sandbox-clis/kubectl.md): Give the Sazabi agent the Kubernetes CLI (kubectl) in its sandbox to inspect and manage your cluster. - [Netlify](https://docs.sazabi.com/catalogs/sandbox-clis/netlify.md): Give the Sazabi agent the Netlify CLI (netlify) in its sandbox to inspect sites, deploys, functions, and logs. - [Porter](https://docs.sazabi.com/catalogs/sandbox-clis/porter.md): Give the Sazabi agent the Porter CLI (porter) in its sandbox to inspect and manage porter.run apps, deployments, and logs. - [Railway](https://docs.sazabi.com/catalogs/sandbox-clis/railway.md): Give the Sazabi agent the Railway CLI (railway) in its sandbox to manage deployments and Railway projects. - [Render](https://docs.sazabi.com/catalogs/sandbox-clis/render.md): Give the Sazabi agent the Render CLI (render) in its sandbox to manage Render services and deployments. - [RunPod](https://docs.sazabi.com/catalogs/sandbox-clis/runpod.md): Give the Sazabi agent the RunPod CLI (runpodctl) in its sandbox to manage GPU pods and serverless endpoints. - [Tailscale](https://docs.sazabi.com/catalogs/sandbox-clis/tailscale.md): Give the Sazabi agent access to your private Tailscale tailnet from its sandbox, with zero stored credentials, via OpenID Connect workload identity federation. - [Terraform](https://docs.sazabi.com/catalogs/sandbox-clis/terraform.md): Give the Sazabi agent the Terraform CLI (terraform) in its sandbox to plan and apply infrastructure changes, authenticated with Terraform Cloud. - [Vercel](https://docs.sazabi.com/catalogs/sandbox-clis/vercel.md): Give the Sazabi agent the Vercel CLI (vercel) in its sandbox to manage Vercel projects and deployments. - [Wrangler](https://docs.sazabi.com/catalogs/sandbox-clis/wrangler.md): Give the Sazabi agent the Wrangler CLI (wrangler) in its sandbox to deploy and manage Cloudflare Workers. #### Databases - [ClickHouse](https://docs.sazabi.com/catalogs/sandbox-clis/clickhouse-cli.md): Give the Sazabi agent the ClickHouse CLI (clickhousectl) in its sandbox to run ClickHouse Cloud and local ClickHouse workflows. - [MongoDB Atlas](https://docs.sazabi.com/catalogs/sandbox-clis/atlas.md): Give the Sazabi agent the MongoDB Atlas CLI (atlas) in its sandbox to manage Atlas clusters, databases, and projects. - [MongoDB Shell](https://docs.sazabi.com/catalogs/sandbox-clis/mongosh.md): Give the Sazabi agent the MongoDB Shell (mongosh) in its sandbox to query and inspect your MongoDB deployment. - [MySQL](https://docs.sazabi.com/catalogs/sandbox-clis/mysql.md): Give the Sazabi agent the MySQL client (mysql) and MySQL Shell (mysqlsh) in its sandbox to query and administer your MySQL databases. - [PlanetScale](https://docs.sazabi.com/catalogs/sandbox-clis/planetscale.md): Give the Sazabi agent the PlanetScale CLI (pscale) in its sandbox to inspect databases, branches, and deploy requests. - [Postgres](https://docs.sazabi.com/catalogs/sandbox-clis/postgres.md): Give the Sazabi agent the Postgres client (psql) in its sandbox to query and inspect your PostgreSQL database. - [Redis](https://docs.sazabi.com/catalogs/sandbox-clis/redis-cli.md): Give the Sazabi agent the Redis CLI (redis-cli) in its sandbox to connect to and query your Redis instance. - [Supabase](https://docs.sazabi.com/catalogs/sandbox-clis/supabase.md): Give the Sazabi agent the Supabase CLI (supabase) in its sandbox to manage Supabase projects, run migrations, and inspect your database. #### Observability and monitoring - [Axiom](https://docs.sazabi.com/catalogs/sandbox-clis/axiom.md): Give the Sazabi agent the Axiom CLI (axiom) in its sandbox to run query, stream, and ingest workflows. - [Checkly](https://docs.sazabi.com/catalogs/sandbox-clis/checkly.md): Give the Sazabi agent the Checkly CLI (checkly) in its sandbox to manage synthetic monitoring, API checks, and browser checks. - [Datadog](https://docs.sazabi.com/catalogs/sandbox-clis/datadog.md): Give the Sazabi agent the Datadog CLI (pup) in its sandbox to validate Datadog API credentials and query your Datadog account. - [PostHog](https://docs.sazabi.com/catalogs/sandbox-clis/posthog.md): Give the Sazabi agent the PostHog CLI (posthog-cli) in its sandbox to upload source maps and query PostHog projects. - [Sentry](https://docs.sazabi.com/catalogs/sandbox-clis/sentry.md): Give the Sazabi agent the Sentry CLI (sentry-cli) in its sandbox to upload source maps, manage releases, and interact with your Sentry organization. #### AI and LLM observability - [Arize](https://docs.sazabi.com/catalogs/sandbox-clis/arize.md): Give the Sazabi agent the Arize AX CLI (ax) in its sandbox to inspect Arize spaces, models, traces, evals, and monitors. - [Braintrust](https://docs.sazabi.com/catalogs/sandbox-clis/braintrust.md): Give the Sazabi agent the Braintrust CLI (bt) in its sandbox to run AI evaluations, experiments, and trace logging. - [Langfuse](https://docs.sazabi.com/catalogs/sandbox-clis/langfuse.md): Give the Sazabi agent the Langfuse CLI (langfuse) in its sandbox to inspect LLM-observability data including traces, prompts, datasets, and scores. - [LangSmith](https://docs.sazabi.com/catalogs/sandbox-clis/langsmith.md): Give the Sazabi agent the LangSmith CLI (langsmith) in its sandbox to inspect LLM traces, datasets, experiments, and evaluations. - [Respan](https://docs.sazabi.com/catalogs/sandbox-clis/respan.md): Give the Sazabi agent the Respan CLI (respan) in its sandbox to manage LLM observability including traces, prompts, evaluators, experiments, datasets, and coding-agent tracing. #### Source control and code review - [Bitbucket](https://docs.sazabi.com/catalogs/sandbox-clis/bitbucket.md): Give the Sazabi agent the Bitbucket CLI (bb) in its sandbox to manage repositories, pull requests, and pipelines. - [CodeRabbit](https://docs.sazabi.com/catalogs/sandbox-clis/coderabbit.md): Give the Sazabi agent the CodeRabbit CLI (coderabbit) in its sandbox to run AI-assisted code review on branches and pull requests. - [Deepsec](https://docs.sazabi.com/catalogs/sandbox-clis/deepsec.md): Give the Sazabi agent the Deepsec CLI (deepsec) in its sandbox to run agent-powered vulnerability scans. - [GitHub](https://docs.sazabi.com/catalogs/sandbox-clis/github.md): Give the Sazabi agent the GitHub CLI (gh) in its sandbox to interact with GitHub repositories, pull requests, and issues. - [Graphite](https://docs.sazabi.com/catalogs/sandbox-clis/graphite.md): Give the Sazabi agent the Graphite CLI (gt) in its sandbox to work with stacked PRs and Git workflows. #### Workflows and backends - [Convex](https://docs.sazabi.com/catalogs/sandbox-clis/convex.md): Give the Sazabi agent the Convex CLI (convex) in its sandbox to inspect Convex deployments, functions, data, and logs. - [Dagster](https://docs.sazabi.com/catalogs/sandbox-clis/dagster.md): Give the Sazabi agent the Dagster CLI (dg) in its sandbox to inspect Dagster+ runs, assets, jobs, and schedules. - [DBOS Cloud](https://docs.sazabi.com/catalogs/sandbox-clis/dbos-cloud.md): Give the Sazabi agent the DBOS Cloud CLI (dbos-cloud) in its sandbox to manage durable workflow applications. - [Inngest](https://docs.sazabi.com/catalogs/sandbox-clis/inngest.md): Give the Sazabi agent the Inngest CLI (inngest) in its sandbox to inspect Inngest Cloud runs, functions, deployments, and events. - [Temporal](https://docs.sazabi.com/catalogs/sandbox-clis/temporal.md): Give the Sazabi agent the Temporal CLI (temporal) in its sandbox to connect to and inspect your Temporal Cloud namespace. #### Secrets and auth - [1Password](https://docs.sazabi.com/catalogs/sandbox-clis/onepassword.md): Give the Sazabi agent the 1Password CLI (op) in its sandbox to read secrets and items from your vaults. - [Clerk](https://docs.sazabi.com/catalogs/sandbox-clis/clerk.md): Give the Sazabi agent the Clerk CLI (clerk) in its sandbox to manage Clerk applications, users, and authentication configuration. - [Doppler](https://docs.sazabi.com/catalogs/sandbox-clis/doppler.md): Give the Sazabi agent the Doppler CLI (doppler) in its sandbox to manage secrets and configuration across environments. #### Apps and services - [Context.dev](https://docs.sazabi.com/catalogs/sandbox-clis/context-dev.md): Give the Sazabi agent the Context.dev CLI (context-dev) in its sandbox for brand lookups, web scraping, and screenshots. - [ElevenLabs](https://docs.sazabi.com/catalogs/sandbox-clis/elevenlabs.md): Give the Sazabi agent the ElevenLabs CLI (elevenlabs) in its sandbox to inspect and manage ElevenLabs Agents, tools, and tests as code. - [Google Drive](https://docs.sazabi.com/catalogs/sandbox-clis/gws.md): Give the Sazabi agent the Google Workspace CLI (gws) in its sandbox for read-only Google Drive access via a service account. - [Mercury](https://docs.sazabi.com/catalogs/sandbox-clis/mercury.md): Give the Sazabi agent the Mercury CLI (mercury) in its sandbox to access read-only banking API data. - [Notion](https://docs.sazabi.com/catalogs/sandbox-clis/notion.md): Give the Sazabi agent the Notion CLI (ntn) in its sandbox to read and manage pages, databases, and blocks. - [Stream](https://docs.sazabi.com/catalogs/sandbox-clis/stream-cli.md): Give the Sazabi agent the Stream CLI (stream) in its sandbox to manage and inspect Stream Chat and Feeds applications. - [Stripe](https://docs.sazabi.com/catalogs/sandbox-clis/stripe.md): Give the Sazabi agent the Stripe CLI (stripe) in its sandbox to inspect and work with your Stripe account. - [Twilio](https://docs.sazabi.com/catalogs/sandbox-clis/twilio.md): Give the Sazabi agent the Twilio CLI (twilio) in its sandbox to manage Twilio resources and inspect messaging and voice activity. - [X](https://docs.sazabi.com/catalogs/sandbox-clis/x.md): Give the Sazabi agent the X CLI (xurl) in its sandbox to interact with the X API using OAuth 1.0a credentials. - [Reference (444 pages)](https://docs.sazabi.com/_llms/reference.txt): Documentation for Reference. ## Security & trust - [Security overview](https://docs.sazabi.com/security/index.md): How Sazabi protects the telemetry you send — encryption, access control, agent and sandbox isolation, privacy, and the compliance posture behind the platform. - [Data handling](https://docs.sazabi.com/security/data-handling.md): How Sazabi encrypts, stores, retains, and deletes the telemetry you send — where it lives, how long it stays, and how it is used. - [Bring your own cloud (BYOC)](https://docs.sazabi.com/security/byoc.md): Run the Sazabi log pipeline in your own AWS account and keep your logs in storage your organization owns, while Sazabi operates the service. - [Access](https://docs.sazabi.com/security/access.md): How Sazabi controls who can see and change your data — roles, project access, sign-in, two-factor, single sign-on, sessions, and the isolation between organizations. - [Agent security](https://docs.sazabi.com/security/agent-security.md): How the Sazabi agent investigates on your behalf with least privilege — running commands in an isolated, ephemeral sandbox with credentials it only holds at runtime. - [Compliance](https://docs.sazabi.com/security/compliance.md): Sazabi's compliance program — its SOC 2 Type II, SOC 1, ISO 27001 and ISO 27017 certifications, how to get the audit reports under NDA, privacy regulations, subprocessors, security testing, and availability. ## cve.now - [cve.now](https://docs.sazabi.com/cve-now/index.md): A free, public vulnerability feed from Sazabi. One merged entry per vulnerability, feeds for the software you run, lockfile checks, early warnings before a CVE exists, and an MCP server for coding agents. No login or API key. - [Data and coverage](https://docs.sazabi.com/cve-now/data-and-coverage.md): Where cve.now's data comes from, how often each source is checked, what makes a vulnerability critical, how summaries are written, and what a lookup does not cover. - [Early warnings](https://docs.sazabi.com/cve-now/early-warnings.md): Security incidents reported before a CVE exists, such as vendor breaches, exploited zero-days, and malicious package releases, with every source linked and a confidence level for each. - [Subscribe to feeds](https://docs.sazabi.com/cve-now/subscribe-to-feeds.md): Subscribe to cve.now's RSS, Atom, or JSON feeds, narrowed to critical or known-exploited vulnerabilities, the technologies you use, and your package ecosystems. Works with any feed reader, Slack, or a script. - [Check your stack](https://docs.sazabi.com/cve-now/check-your-stack.md): Find the vulnerabilities that affect the exact package versions in your lockfile, and subscribe to a feed of only those. Upload a lockfile on cve.now, from the command line, or pass a package list in a URL. - [Connect a coding agent](https://docs.sazabi.com/cve-now/connect-a-coding-agent.md): Add the cve.now MCP server to Claude Code, Codex, OpenCode, Cursor, or any agent that supports remote MCP, so it can look up vulnerabilities, read the feed, and check your lockfile. No login or API key. - [JSON API](https://docs.sazabi.com/cve-now/api.md): Reference for cve.now's public JSON endpoints - fetch one entry, browse the catalog, read a feed, check package versions, read source status and aggregate statistics, and upload a lockfile. No authentication. ## OpenAPI Specs - [openapi](/openapi.json) > The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages. ## Indexes - [Reference (444 pages)](https://docs.sazabi.com/_llms/reference.txt): Documentation for Reference. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.