# Monitoring

# Monitoring

Monitoring ensures your Curiosity Workspace environment is healthy, performant, and secure. Effective monitoring covers:

• availability (is the workspace reachable?)
• performance (latency, throughput)
• ingestion and background jobs (success/failure, duration)
• search/index health
• security signals (auth failures, token usage, admin actions)

# What to monitor (baseline)

• Service health
  • uptime, restarts, error rates
• Ingestion
  • last successful run time
  • items processed per run
  • failure rate and top failure reasons
• Indexing
  • queue depth / progress (if available)
  • completion status for rebuilds
• Query performance
  • slow queries (graph and search)
  • timeouts and resource saturation

# Logs and audit trails

Recommended log categories:

• ingestion connector logs
• endpoint invocation logs
• admin configuration changes
• authentication and authorization events

# Alerting

Start with a small set of high-signal alerts:

• workspace unavailable
• repeated ingestion failures
• index rebuild stuck or failed
• elevated error rate or latency regression

# Next steps

• Secure the environment: Security
• Scale with confidence: Best Practices → Scaling