Skip to main content
Set up Sazabi with one command, or hand setup to your coding agent. By the end you have a project receiving logs and an answer from the Sazabi agent about a log you sent yourself.

Prerequisites

  • Node.js, so npx can run the Sazabi CLI. Nothing else to install.
  • A terminal with curl, for the test event.
  • Optional: Claude Code, Codex, Cursor, or Gemini. If one is installed, setup offers to hand the work to it.

Start setup

Run the single entry command:
-y answers the install prompt for you. Keep @latest: without it, npx can reuse an older cached copy that lacks newer commands and flags.The command prints how to sign in and the first setup step. When you are signed in, it names the account it will use. If Claude Code, Codex, Cursor, or Gemini is installed, it also prints the command that hands setup to that agent, such as:
To have your coding agent run setup for you, paste this into it:
Setup signs you in or creates your account, then walks through an organization, a plan, a project, optional GitHub and Slack connections, and a log source. Your agent asks before each change and shows every option, so you choose each one. After each step, run this for the next one, until it says onboarding is complete:
The plan step is where payment starts. The entry plan is Hobby at $50 per 30 days. Your agent shows every plan with its price and subscribes only after you say yes to that plan. Pay on the secure checkout page it prints, then tell the agent you have paid.
Sazabi stores your logs in managed storage for the project. There is no storage backend to configure.

Run without a browser

Once your project exists, CI, scripts, and headless agents can skip signing in. Set SAZABI_TOKEN to a secret key and SAZABI_PROJECT_ID to your project’s ID. Create the key at Settings > Secret keys, or while signed in with npx -y @sazabi/cli@latest secret-keys create "CI agent". Keep it in a secrets manager and never commit it.
Creating the organization and choosing a plan still need a signed-in person, because a secret key belongs to an organization that already exists.

Send a test event

Send one OpenTelemetry-format log record to your log source. It proves the whole path end to end in under a minute, with nothing to install.

Get your intake URL

The command creates a manual OpenTelemetry log source and prints its intake URL. If setup already created a log source, run npx -y @sazabi/cli@latest log-sources get your-log-source-id to print its endpoint again.
Each log source has its own intake URL. The URL authenticates the request on its own, so there is no separate key or header to send.

Send the event

Add the /v1/logs path to your intake URL and post one record:
You should get an HTTP 200 with {"success":true,...}. That means the record was accepted; the steps below confirm it landed. The curl event is a smoke test, not a source.

Send from a real application

To send continuously, point your OpenTelemetry exporter at the same intake URL, with no headers:
Set the endpoint to the base URL without a path: the SDK appends /v1/logs and /v1/traces itself. Sazabi’s OTLP intake is HTTP only, so http/protobuf is required. For per-language steps, see OpenTelemetry log source. Platforms with a one-click Connect your account path, and other endpoint senders such as Fluent Bit, Vector, and the Datadog Agent, are covered in Choosing a path.

Ask your first question

Ask about the event you sent. New logs are normally searchable within a minute or two.

Verify

The answer reports one matching line. Its results show service quickstart, severity INFO, and the message sazabi quickstart test event 8842. In a dashboard thread, the agent also shows the log search it ran. If nothing matches after a couple of minutes, check that you copied the full intake URL and that curl returned 200, then see Troubleshooting ingestion. To watch volume per source, see Check data is flowing.

Next steps

Open the issue Sazabi raised and ask about it. See Run your first investigation.

Further reading

Connect your coding agent

Investigate production from your terminal or GUI agent.

Check data is flowing

Confirm each source is delivering.