> ## Documentation Index > Fetch the complete documentation index at: https://docs.logclaw.ai/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Every platform LogClaw connects to — from incident routing to cloud infrastructure to data migration. LogClaw integrates with the tools your team already uses. No proprietary agents, no vendor lock-in — just OpenTelemetry in, intelligence out. *** ## Incident Routing LogClaw auto-creates incident tickets with AI root cause analysis, routed by severity to the platform your team already uses. }> Events API v2 with severity mapping. Critical and high-severity incidents trigger pages automatically. }> REST API v2 issue creation with priority mapping, custom labels, and project routing. }> Incident table API with severity, urgency, impact fields, and assignment group routing. }> v2 Alerts API with priority mapping, responder teams, and escalation support. }> Incoming webhooks with severity indicators, service tags, and direct links to incident details. ### Severity-Based Routing Configure which platform receives incidents based on severity: ```yaml theme={null} routing: critical: pagerduty # Wake someone up high: pagerduty # Page the on-call medium: jira # Create a ticket low: slack # Post to channel ``` Every platform supports connection health checks with latency metrics from the LogClaw dashboard. *** ## Cloud Providers LogClaw is Kubernetes-native and runs on any cloud. Helm charts include provider-specific configurations for authentication, secrets, and object storage. }> **EKS** with IRSA (IAM Roles for Service Accounts), **S3** for object storage, **AWS Secrets Manager** via External Secrets Operator. }> **GKE** with Workload Identity, **GCS** for object storage, **Google Secret Manager** via External Secrets Operator. }> **AKS** with Workload Identity, **Azure Blob Storage**, **Azure Key Vault** via External Secrets Operator. ### Self-Hosted LogClaw also runs on any self-managed Kubernetes cluster with: * **MinIO** for S3-compatible object storage * **HashiCorp Vault** for secret management * Standard CSI-compatible persistent volumes *** ## Data Ingestion }> **The only ingestion protocol.** LogClaw receives logs exclusively via OTLP — the CNCF industry standard adopted by 48.5% of enterprises. gRPC on port 4317, HTTP on port 4318. ### Migrate From Existing Tools LogClaw replaces these platforms for log observability and incident detection. Since OpenTelemetry is vendor-neutral, migrating is straightforward — point your OTel Collector or SDK at LogClaw instead of your current vendor. }> Replace Splunk's log observability at **80-90% lower cost**. No SPL lock-in, no proprietary Universal Forwarders. Your data stays in your cluster. }> Eliminate per-GB pricing surprises. LogClaw delivers autonomous incident detection that Datadog's dashboard-first model cannot match. }> Move from New Relic's consumption-based pricing to self-hosted log intelligence with zero vendor risk. }> Replace Dynatrace log monitoring with OTLP-native ingestion and AI-powered root cause analysis — at a fraction of the cost. }> Consolidate CloudWatch Logs into LogClaw for cross-cloud visibility, anomaly detection, and auto-ticketing that CloudWatch doesn't offer. LogClaw doesn't require you to rip-and-replace overnight. You can run LogClaw alongside your existing tools — send the same OTLP data to both — and migrate incrementally as your team gains confidence. *** ## AI / LLM Providers LogClaw uses LLMs for root cause analysis — generating human-readable incident summaries from correlated log entries. Choose your provider: | Provider | Type | Details | | ---------------------- | ----------- | --------------------------------------- | | **Claude** (Anthropic) | Cloud API | `v1/messages` — recommended for quality | | **OpenAI** | Cloud API | `v1/chat/completions` — GPT-4o / GPT-4 | | **Ollama** | Self-hosted | Local inference — full data sovereignty | | **vLLM** | Self-hosted | High-throughput inference server | For maximum data sovereignty, pair LogClaw with **Ollama** or **vLLM** — your logs and incident summaries never leave your infrastructure. *** ## Observability Stack | Component | Integration | Purpose | | -------------- | ----------- | ------------------------------------------------------------- | | **Prometheus** | Built-in | All LogClaw services expose `/metrics` endpoints for scraping | | **Grafana** | Optional | Pre-built dashboard JSON via `grafanaDashboards` Helm flag | | **OpenSearch** | Core | Log storage, full-text search, and analytics backend | | **Kafka** | Core | Internal message broker for log streaming between components |