Skip to main content
OpenViking Server provides comprehensive endpoints for monitoring system health and component status.

Health Check

The /health endpoint provides a simple liveness check with no authentication required.
Response:
This endpoint is always accessible without authentication, making it ideal for load balancers and monitoring tools.

Readiness Check

The /ready endpoint checks all system components before accepting traffic.
Response:
Use /health for Kubernetes liveness probes and /ready for readiness probes.

System Status

Get comprehensive status of all components.

Overall System Health

Response:

Component Status

Check individual component health.

Queue Status

Monitor the processing queue:

VikingDB Status

Check vector database health:

VLM Status

Monitor Vision Language Model health:

Response Time Monitoring

Every API response includes processing time in the X-Process-Time header.
Time is measured in seconds and represents server-side processing time only.

Kubernetes Integration

Configure health probes for Kubernetes deployments:
1

Liveness Probe

Uses /health to check if the container is alive. Kubernetes restarts the pod if this fails.
2

Readiness Probe

Uses /ready to check if the service is ready to accept traffic. Kubernetes removes the pod from service endpoints if this fails.

Monitoring Best Practices

Configure alerts for component health:

Prometheus Integration

While OpenViking doesn’t expose Prometheus metrics directly, you can create a simple exporter:
Add to prometheus.yml:

Troubleshooting

Symptom: is_healthy: false for a componentSolutions:
  1. Check component logs
  2. Verify configuration (API keys, endpoints)
  3. Test network connectivity
  4. Restart the service
Symptom: Processing queue grows without clearingSolutions:
  1. Increase embedding concurrency:
  2. Check VLM rate limits
  3. Scale horizontally with more workers
Symptom: X-Process-Time > 1 secondSolutions:
  1. Check vector database performance
  2. Optimize search parameters (limit, threshold)
  3. Use local storage for better latency
  4. Enable caching

Deployment

Server deployment and configuration

Configuration

System configuration reference

Python SDK

Client health check methods

CLI Usage

CLI monitoring commands