Frequently Asked Questions

General

What is SLOzy?

SLOzy is a commercial Service Level Objective (SLO) management platform for DevOps engineers, SREs, and technical leads. It provides real-time SLO monitoring, error budget tracking, multi-channel alerting, and GitOps integration for managing reliability targets.

What are the system requirements?

See the Prerequisites page for full details. Minimum requirements:

• PostgreSQL 16+
• Redis 7+ (optional, for cache)
• 512 MB RAM, 1 GB disk, 1 CPU core
• Docker or Kubernetes for containerized deployment

SLOs and Error Budgets

What is an SLO?

A Service Level Objective (SLO) is a target value for a service's reliability, typically expressed as a percentage over a time window (e.g., 99.9% availability over 30 days). SLOzy helps you define, track, and alert on these targets.

How is the error budget calculated?

The error budget is the maximum allowable number of failures within a time window. It is calculated as:

Error Budget = (1 - SLO Target) × Total Events
Error Budget Used = (Current Failures / Error Budget) × 100

For example, a 99.9% SLO over 30 days allows 0.1% downtime (~43 minutes).

What is burn rate?

Burn rate measures how fast the error budget is being consumed relative to the SLO target. A burn rate of 1.0 means you're consuming error budget at exactly the rate that would exhaust it by the end of the time window. A burn rate > 1.0 means you're on track to exceed the error budget.

Deployment

How do I deploy SLOzy in production?

See the Deployment Guide for systemd, Docker, and Kubernetes deployment options. For Kubernetes specifically, apply the manifests in k8s/:

kubectl apply -f k8s/
kubectl rollout status deployment/slozy-web -n slozy

Can I use Docker Compose for production?

Docker Compose is recommended for development and evaluation only. For production, use Kubernetes with proper resource limits, health checks, and persistent storage.

How do I configure environment variables?

Copy .env.example to .env and edit the values. Key variables include:

Variable	Description
PORT	Application port (default: 8080)
POSTGRES_*	Database connection settings
JWT_SECRET	JWT signing key (min 32 chars)
CORS_ORIGINS	Allowed CORS origins

Notifications

What notification channels are supported?

SLOzy supports email, Slack, and webhook notifications. Notification channels are configured via the API or UI and support deduplication with configurable time windows.

How do I set up Slack notifications?

Create a webhook URL in your Slack workspace and add it as a notification channel in SLOzy. Configure alert rules to trigger notifications when error budget consumption exceeds thresholds.

API

Is there a public API?

Yes. The API is documented in the API Reference. Authentication is via JWT Bearer tokens or API keys. All endpoints are versioned under /api/v1/.

Security

How is data encrypted?

Passwords are hashed using bcrypt. JWT tokens are signed with HS256. API keys are hashed before storage. All communications should use HTTPS in production. Prometheus data source connections use TLS with certificate validation.

Can I use SSO?

SLOzy supports OAuth2 authentication with providers like GitHub and Google. OAuth2 flow is fully persisted with authorization codes, access tokens, and refresh tokens.