Skip to main content
Orpheus provides built-in observability for production monitoring.

​
Prometheus Metrics

Every daemon exposes a /metrics endpoint: 
curl http://localhost:7777/metrics

​
Available Metrics

MetricTypeDescription
orpheus_queue_depthGaugePending requests per agent
orpheus_queue_pendingGaugeRequests waiting in queue
orpheus_queue_processingGaugeRequests currently executing
orpheus_queue_max_sizeGaugeMaximum queue capacity
orpheus_pool_workers_totalGaugeTotal workers per agent
orpheus_pool_workers_idleGaugeIdle workers available
orpheus_pool_workers_busyGaugeWorkers currently executing
orpheus_pool_desired_sizeGaugeTarget worker count
orpheus_execlog_requests_totalCounterTotal requests processed
orpheus_execlog_success_rateGaugeSuccess percentage
orpheus_service_upGaugeModel server status
orpheus_service_uptime_secondsGaugeModel server uptime

​
Prometheus Scrape Config

# prometheus.yml
scrape_configs:
  - job_name: 'orpheus'
    static_configs:
      - targets: ['localhost:7777']
    scrape_interval: 15s

​
Grafana Queries

# Queue depth by agent
orpheus_queue_depth{agent="my-agent"}

# Worker utilization
orpheus_pool_workers_busy / orpheus_pool_workers_total

# Request rate
rate(orpheus_execlog_requests_total[5m])

​
Execution Logs

Every request is tracked in the exec log with full lifecycle: 
orpheus execlog list my-agent
Output: 
TIMESTAMP   REQUEST ID      AGENT      STATE     SOURCE  DURATION
────────────────────────────────────────────────────────────────
21:31:59    67f6b220-10b... my-agent   COMPLETED http    234ms
21:31:50    67f6b220-10b... my-agent   STARTED   http    -
21:31:50    67f6b220-10b... my-agent   QUEUED    http    -

​
Request States

StateMeaning
QUEUEDRequest received, waiting for worker
STARTEDWorker picked up the request
COMPLETEDExecution finished successfully
FAILEDHandler returned an error
CRASHEDDaemon died mid-execution

​
Source Tracking

Exec logs distinguish between HTTP and MCP requests: 
# View HTTP requests only
orpheus execlog list my-agent --source http

# View MCP (agent-to-agent) requests only
orpheus execlog list my-agent --source mcp
Visual distinction in CLI:
  • http = Blue text
  • mcp = Magenta text

​
Debugging Agent Chains

When agent-router calls calculator-python via MCP: 
# See what agent-router did (HTTP)
orpheus execlog list agent-router --source http

# See what calculator-python received (MCP)
orpheus execlog list calculator-python --source mcp

​
API Endpoints

​
Get Metrics

curl http://localhost:7777/metrics

​
Query Exec Logs

# All logs for an agent
curl "http://localhost:7777/v1/execlog?agent=my-agent"

# Filter by source
curl "http://localhost:7777/v1/execlog?agent=my-agent&source=mcp"

# Filter by state
curl "http://localhost:7777/v1/execlog?agent=my-agent&state=FAILED"

​
Custom Labels

Add labels to metrics via agent.yaml: 
name: my-agent
runtime: python3
module: agent.py
entrypoint: handler

telemetry:
  enabled: true
  labels:
    team: platform
    tier: production
    use_case: rag
Metrics will include these labels: 
orpheus_queue_depth{agent="my-agent",team="platform",tier="production"}

Autoscaling

Learn how queue-depth drives scaling →