Overview

Projects are isolated workspaces for your telemetry data. Each project has its own logs, threads, alerts, and API keys, ensuring complete separation between different environments or services.

What is a project?

A project is the fundamental unit of data isolation in Sazabi. When you send logs to Sazabi, they are stored within a specific project. When you investigate issues with Chat, you are working within the context of a single project.

Key characteristics of projects:

• Data isolation: Logs sent to one project are not visible in another
• Independent threads: Conversations and investigations are scoped to their project
• Project-specific alerts: Alerts are triggered and managed per project
• Dedicated API keys: Public keys for log ingestion are scoped to a single project

How projects relate to organizations

Projects exist within organizations. An organization is the top-level container that holds your team, billing, and shared integrations. Projects provide data isolation within that organization.

Organization (My Company)
├── Project: production
├── Project: staging
└── Project: development

All team members in an organization can access all projects within it. If you need to restrict access to certain projects, create a separate organization.

When to create separate projects

Separate environments

The most common pattern is one project per environment:

• Production: Your live environment with real user traffic
• Staging: Pre-production testing environment
• Development: Local or shared development environment

This separation ensures production alerts are meaningful and investigations are not polluted with test data.

Separate services or applications

For microservices architectures or multiple applications, consider separate projects when:

• Services have different teams responsible for them
• You want independent alert configurations per service
• Services have different retention or compliance requirements

Separate regions

If you operate in multiple regions with data residency requirements, create separate projects for each region. Each project can be configured with a specific regional backend.

When to use a single project

Use a single project when:

• You have a monolithic application
• You want to correlate logs across multiple services during investigations
• Your team is small and everyone needs visibility into all data

Project components

Each project includes:

Next steps