API Reference
LogClaw exposes APIs through two access patterns:-
Dashboard Proxy — the Next.js Dashboard proxies requests to backend services under
/api/<service>/. Use this for browser-based access and when the Dashboard is your entry point. - Direct Service Access — each backend service exposes its own API on its Kubernetes ClusterIP service. Use this for programmatic access from within the cluster.
Service Endpoints
| Service | Dashboard Proxy | Direct (in-cluster) | Port |
|---|---|---|---|
| OTel Collector | /api/otel/* | logclaw-otel-collector:4318 | 4317 (gRPC), 4318 (HTTP) |
| Bridge | /api/bridge/* | logclaw-bridge:8080 | 8080 |
| OpenSearch | /api/opensearch/* | logclaw-opensearch:9200 | 9200 |
| Ticketing Agent | /api/ticketing/* | logclaw-ticketing-agent:18081 | 18081 |
| Infrastructure Agent | /api/agent/* | logclaw-agent:8080 | 8080 |
| Airflow | /api/airflow/* | logclaw-airflow-webserver:8080 | 8080 |
| Feast | /api/feast/* | logclaw-feast:6567 | 6567 |
Authentication
All Dashboard API routes are unauthenticated proxies intended for internal cluster use. Access control is enforced at the Kubernetes NetworkPolicy level — only pods within the tenant namespace can reach backend services. For external access, deploy an ingress controller with authentication (OIDC, mTLS) in front of the Dashboard service.OpenSearch requests through the Dashboard proxy include Basic Auth headers automatically when
OPENSEARCH_USER and OPENSEARCH_PASSWORD environment variables are set.