# LogClaw

## Docs

- [API Keys](https://docs.logclaw.ai/api-keys.md): Create and manage API keys for authenticating log ingestion on LogClaw Cloud
- [Infrastructure Agent API](https://docs.logclaw.ai/api-reference/agent.md): Cluster health monitoring API from the Go-based infrastructure agent.
- [Bridge API](https://docs.logclaw.ai/api-reference/bridge.md): Bridge service API for health checks, metrics, and runtime configuration.
- [Agent Health](https://docs.logclaw.ai/api-reference/endpoints/agent-health.md): Liveness probe for the Infrastructure Agent.
- [Infrastructure Metrics](https://docs.logclaw.ai/api-reference/endpoints/agent-metrics.md): Returns aggregated infrastructure health metrics from all cluster collectors: Kafka broker and topic status, Flink job states, OpenSearch cluster health, and External Secrets sync status.
- [Bridge Configuration](https://docs.logclaw.ai/api-reference/endpoints/bridge-config.md): Returns the current Bridge runtime configuration including anomaly detection thresholds, Kafka topics, and OpenSearch endpoint.
- [Bridge Health](https://docs.logclaw.ai/api-reference/endpoints/bridge-health.md): Returns the health status of all Bridge processing threads and backend connections (Kafka, OpenSearch).
- [Create API Key](https://docs.logclaw.ai/api-reference/endpoints/create-api-key.md): Create a new API key for the project. The full key value is returned **only once** in the response — store it securely.
- [List API Keys](https://docs.logclaw.ai/api-reference/endpoints/list-api-keys.md): Returns all API keys for the authenticated project. Key values are masked — only the prefix is returned.
- [List Incidents](https://docs.logclaw.ai/api-reference/endpoints/list-incidents.md): Returns all tracked incidents for your project with their current state, severity, affected services, and ticketing platform status.
- [List Indices](https://docs.logclaw.ai/api-reference/endpoints/list-indices.md): Returns all OpenSearch indices with their health status, document count, and storage size. LogClaw uses daily indices with the pattern `logclaw-logs-YYYY.MM.dd`.
- [Revoke API Key](https://docs.logclaw.ai/api-reference/endpoints/revoke-api-key.md): Permanently revoke an API key. The key stops working immediately — any requests using it will receive `401 Unauthorized`. This action is irreversible.
- [Runtime Configuration](https://docs.logclaw.ai/api-reference/endpoints/runtime-config.md): Returns the complete Ticketing Agent runtime configuration including platform settings, severity routing rules, anomaly thresholds, and LLM config.
- [Send Logs](https://docs.logclaw.ai/api-reference/endpoints/send-logs.md): Ingest log records in OTLP HTTP/JSON format. This is the primary ingestion endpoint for LogClaw Cloud. Logs are processed through the pipeline: OTel Collector → Kafka → Bridge → OpenSearch.
- [Ingestion API](https://docs.logclaw.ai/api-reference/ingestion.md): OTLP log ingestion endpoints via the OpenTelemetry Collector.
- [OpenSearch API](https://docs.logclaw.ai/api-reference/opensearch.md): OpenSearch query and index management endpoints proxied through the Dashboard.
- [API Reference](https://docs.logclaw.ai/api-reference/overview.md): Complete API documentation for all LogClaw services with interactive playground.
- [Ticketing API](https://docs.logclaw.ai/api-reference/ticketing.md): Incident management and runtime configuration API for the Ticketing Agent.
- [Architecture](https://docs.logclaw.ai/architecture.md)
- [Bridge](https://docs.logclaw.ai/components/bridge.md): OTLP ETL translator, anomaly detection, trace correlation, and OpenSearch indexing service.
- [Dashboard](https://docs.logclaw.ai/components/dashboard.md): Next.js web UI for log ingestion, incident management, anomaly visualization, and pipeline monitoring.
- [Incident Classification](https://docs.logclaw.ai/components/incident-classification.md): How LogClaw decides which log signals are incident-worthy vs. noise.
- [OTel Collector](https://docs.logclaw.ai/components/otel-collector.md): OTLP-native log ingestion gateway using OpenTelemetry Collector.
- [Ticketing Agent](https://docs.logclaw.ai/components/ticketing-agent.md): AI SRE agent for automated incident detection, trace correlation, and multi-platform ticket management.
- [Integrations](https://docs.logclaw.ai/integrations.md): Every platform LogClaw connects to — from incident routing to cloud infrastructure to data migration.
- [MCP Server](https://docs.logclaw.ai/integrations/mcp.md): Connect Claude Code, Cursor, or Windsurf to LogClaw incidents, logs, and anomalies via the Model Context Protocol.
- [Introduction](https://docs.logclaw.ai/introduction.md): AI-powered log intelligence platform with real-time anomaly detection, trace correlation, and OTLP-native ingestion.
- [Local Development](https://docs.logclaw.ai/local-development.md): Set up a local LogClaw development environment for testing and development.
- [Tenant Onboarding](https://docs.logclaw.ai/onboarding.md): Provision a new LogClaw tenant from zero to fully operational in 30 minutes.
- [OTLP Integration Guide](https://docs.logclaw.ai/otlp-integration.md): Send logs to LogClaw from any language or framework using OpenTelemetry Protocol.
- [Quick Start: Send Logs to LogClaw](https://docs.logclaw.ai/quickstart-send-logs.md): Get your application logs flowing into LogClaw in under 5 minutes
- [Values Reference](https://docs.logclaw.ai/values-reference.md): Full configuration reference for all LogClaw Helm chart values.

## OpenAPI Specs

- [openapi](https://docs.logclaw.ai/openapi.yaml)

## Optional

- [GitHub](https://github.com/logclaw/logclaw)