Creating Projects

This guide walks you through creating a new project in Sazabi. Projects provide isolated workspaces for your telemetry data, and you can create them through the dashboard, CLI, or API.

Prerequisites

A Sazabi account
Membership in an organization (created automatically on signup)

Create a project

Open Settings

Navigate to Settings in the left sidebar of the Sazabi dashboard.

Go to Projects

Click Projects in the settings menu to view your existing projects.

Create new project

Click New project to open the project creation dialog.

Configure project settings

Enter the following details:

Name: A descriptive name for your project (e.g., "production", "staging-us-east", "my-app-dev")
Region: The region where your data will be stored
Backend: Choose between Sazabi managed storage or an external backend

Click Create to create the project.

You should now see your new project in the project list.

Create a project using the Sazabi CLI:

sazabi projects create --name "production"

The CLI returns the project ID, which you use to configure API keys and send logs:

{
  "id": "proj_abc123def456",
  "name": "production",
  "region": "us-east-1",
  "created_at": "2024-01-15T10:30:00Z"
}

Additional options

Specify a region:

sazabi projects create --name "production-eu" --region "eu-west-1"

List all projects in your organization:

sazabi projects list

Create a project using the REST API:

curl -X POST "https://api.sazabi.com/v1/projects" \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production",
    "region": "us-east-1"
  }'

Response:

{
  "id": "proj_abc123def456",
  "name": "production",
  "region": "us-east-1",
  "backend": "sazabi",
  "created_at": "2024-01-15T10:30:00Z"
}

See the API Reference for authentication details.

Initial configuration

After creating a project, configure these settings:

1. Get your API key

Every project has a public API key for log ingestion. Navigate to Settings > API Keys to view and copy your project's public key.

# Your public key looks like this
pk_live_abc123...

2. Configure data sources

Connect your log sources to start sending data:

Native integrations: Connect platforms like Vercel, CloudWatch, or Fly.io with one-click setup
OpenTelemetry: Send logs using the OpenTelemetry SDK
Direct API: Send logs directly to the intake endpoint

See Sending Logs for detailed setup guides.

3. Set up alerts

Configure how you want to receive alert notifications:

Slack: Post alerts to a Slack channel
Email: Send notifications to team members
Webhooks: Trigger custom workflows

Navigate to Settings > Alerts to configure delivery channels.

Switching between projects

Use the project switcher in the dashboard header to change your active project. The switcher shows all projects within your current organization.

Set the active project for CLI commands:

sazabi config set project proj_abc123def456

Or use the SAZABI_PROJECT_ID environment variable:

export SAZABI_PROJECT_ID=proj_abc123def456
sazabi logs query "level:error"

The environment variable takes precedence over the configured project.

Best practices

Keep production data separate from development and staging. This ensures alerts are meaningful and investigations are not polluted with test data.

Use descriptive names: Name projects clearly (e.g., "production", "staging-us-east", "local-dev") so team members know which environment they are viewing.
One project per environment: Create separate projects for production, staging, and development.
Document project purposes: Include context in project names or descriptions so team members understand what each project is for.
Consider regional needs: If you have data residency requirements, create projects in appropriate regions.