Incident Routing
LogClaw auto-creates incident tickets with AI root cause analysis, routed by severity to the platform your team already uses.PagerDuty
Events API v2 with severity mapping. Critical and high-severity incidents trigger pages automatically.
Jira
REST API v2 issue creation with priority mapping, custom labels, and project routing.
ServiceNow
Incident table API with severity, urgency, impact fields, and assignment group routing.
OpsGenie
v2 Alerts API with priority mapping, responder teams, and escalation support.
Slack
Incoming webhooks with severity indicators, service tags, and direct links to incident details.
Severity-Based Routing
Configure which platform receives incidents based on severity:Cloud Providers
LogClaw is Kubernetes-native and runs on any cloud. Helm charts include provider-specific configurations for authentication, secrets, and object storage.AWS
EKS with IRSA (IAM Roles for Service Accounts), S3 for object storage, AWS Secrets Manager via External Secrets Operator.
Google Cloud
GKE with Workload Identity, GCS for object storage, Google Secret Manager via External Secrets Operator.
Azure
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
OpenTelemetry (OTLP)
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.Splunk
Replace Splunk’s log observability at 80-90% lower cost. No SPL lock-in, no proprietary Universal Forwarders. Your data stays in your cluster.
Datadog
Eliminate per-GB pricing surprises. LogClaw delivers autonomous incident detection that Datadog’s dashboard-first model cannot match.
New Relic
Move from New Relic’s consumption-based pricing to self-hosted log intelligence with zero vendor risk.
Dynatrace
Replace Dynatrace log monitoring with OTLP-native ingestion and AI-powered root cause analysis — at a fraction of the cost.
CloudWatch
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 |
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 |