Skip to main content

Status Page & Service Registry

The status page at https://status.jettaintelligence.com serves as both a public status page and internal service registry. MCPammer provides tools to manage services, connections, and documentation.

Service Registry​

Every service in the Jetta ecosystem should be registered:

mcpammer status create myservice \
  --name "My Service" \
  --description "What it does" \
  --url "https://myservice.jettaintelligence.com" \
  --health-endpoint "https://myservice.jettaintelligence.com/health" \
  --category-id backend \
  --repo "aic-holdings/myservice"

Categories​

CategoryDescription
infrastructureCore infrastructure (Coolify, Infisical, etc.)
backendAPI services and backends
frontendWeb applications and UIs
databaseDatabases and data stores
mcpMCP servers
externalExternal services
dataData processing and pipelines

Common Operations​

List Services​

# All services
mcpammer status list

# By category
mcpammer status list --category backend

# Include inactive
mcpammer status list --include-inactive

Get Service Details​

mcpammer status get myservice

Update Service​

mcpammer status update myservice \
  --description "Updated description" \
  --health-endpoint "https://myservice.jettaintelligence.com/api/health"

Delete Service​

# Soft delete (marks inactive)
mcpammer status delete myservice

# Hard delete (permanent)
mcpammer status delete myservice --hard

Service Connections​

Visualize dependencies between services:

# myservice depends on artemis
mcpammer status connection add myservice artemis --label "LLM calls"

# Remove connection
mcpammer status connection delete myservice artemis

# View graph
mcpammer status graph

Service Documentation (SCD Type 2)​

Documentation is versioned - every update creates a new version while preserving history.

Update Documentation​

mcpammer status docs update myservice \
  --description "Service description" \
  --purpose "Why it exists" \
  --tech-stack "Python, FastAPI, PostgreSQL" \
  --changed-by "claude" \
  --change-reason "Initial documentation"

View History​

mcpammer status docs history myservice

Point-in-Time Query​

# What was the documentation on Jan 1, 2024?
mcpammer status docs get myservice --as-of "2024-01-01"

Service Features​

Track features per service (also versioned):

# Add feature
mcpammer status feature add myservice \
  --name "Authentication" \
  --description "OAuth2 and API key auth" \
  --category "security" \
  --major

# List features
mcpammer status feature list myservice

# Remove feature
mcpammer status feature remove myservice "Authentication"

Integration with Monitoring​

Services can link to Uptime Kuma monitors:

mcpammer status update myservice \
  --kuma-monitor-id 42 \
  --kuma-monitor-name "myservice-health"

Best Practices​

  1. Register early - Add to status page when service is created
  2. Keep docs updated - Update when features change
  3. Map connections - Shows architecture and dependencies
  4. Use categories - Helps with filtering and visualization
  5. Add health endpoints - Enables monitoring integration