Clusters

A Cluster is a logical grouping of computing resources where your FixPanic agents run. Clusters help you organize your infrastructure and manage agents effectively.

What is a Cluster?

A cluster represents:

• An environment (Production, Staging, Development)
• A project or application
• A region or data center
• Any logical grouping that makes sense for your organization

Why Use Clusters?

Organization

Group related infrastructure:

• All production servers in one cluster
• Each environment separate
• Easy to navigate and manage

Isolation

Keep environments separate:

• Production commands don't affect staging
• Development experiments isolated
• Clear boundaries between contexts

Access Control

Manage permissions at the cluster level:

• Team members see only their clusters
• Different access levels per cluster
• Audit trails per environment

Credentials

Each cluster has unique credentials:

• Agents authenticate per cluster
• Compromise isolation
• Easy to rotate

Cluster Organization Patterns

By Environment

The most common pattern:

By Region

For geographically distributed infrastructure:

By Application

For multi-application organizations:

Combined

Combine patterns as needed:

Cluster Lifecycle

Creating a Cluster

1. Navigate to Clusters in the dashboard
2. Click "Create Cluster"
3. Enter a name and description
4. Save the generated credentials

Cluster States

Deleting a Cluster

Warning: You must delete all agents in a cluster before deleting the cluster itself.

1. Remove or move all agents
2. Go to cluster settings
3. Click "Delete Cluster"
4. Confirm deletion

Cluster Credentials

Each cluster has:

Credential Security

Best practices:

• Store keys in a secrets manager
• Use environment variables
• Never commit to version control
• Rotate periodically

Regenerating Credentials

If a key is compromised:

1. Go to cluster settings
2. Click "Regenerate API Key"
3. Confirm (this invalidates the old key)
4. Update all agents with the new key

Cluster Health

Health Indicators

Health Checks

The platform monitors:

• Agent heartbeats (every 30 seconds)
• Connection status
• Response times

Alerting

Configure alerts for:

• Agent disconnections
• Health status changes
• Resource thresholds

Infrastructure Flexibility

Clusters are infrastructure-agnostic. They can contain agents running on:

Multi-Cluster Strategies

Environment Promotion

Move code through environments:

Use separate clusters for each stage.

Blue-Green Deployments

Maintain two production clusters:

• production-blue - Current live
• production-green - New deployment

Switch traffic between them.

Regional Failover

Clusters in multiple regions:

• prod-us-east - Primary
• prod-us-west - Secondary

Failover between regions as needed.

Best Practices

Naming Conventions

Use consistent, descriptive names:

• Include environment: prod-, staging-, dev-
• Include region if applicable: -us-east, -eu
• Include project if multi-tenant: -api, -web

Documentation

Document your clusters:

• Purpose and scope
• Who has access
• Related systems
• Contact information

Limits

Consider subscription limits:

• Number of clusters allowed
• Number of agents per cluster
• API rate limits

Cleanup

Regularly review clusters:

• Archive unused clusters
• Remove obsolete agents
• Clean up test environments

Next Steps

• Security - Learn about security controls for clusters.
• Managing Clusters - Manage clusters through the dashboard.
• First Deployment - Deploy your first agent to a cluster.