Krafter Logs

Centralized log management powered by ClickHouse. Ingest structured logs from any service, search and filter in real time, set up alerts, and export data -- all through a simple API.

Features

• ClickHouse-powered search -- Full-text search across millions of log entries with sub-second response times
• Dual authentication -- Team API key for project management, per-project ingest tokens for sending logs
• Structured logging -- Levels (debug, info, warn, error, fatal), service names, and arbitrary metadata fields
• Auto-discovered streams -- Streams are created automatically from the stream field in your log entries
• Distributed tracing -- Correlate logs across services with trace_id and span_id fields
• Alerts -- Get notified by email or webhook when error rates exceed your thresholds
• Export -- Download logs as CSV or JSON for offline analysis (up to 10,000 entries)
• Batch ingestion -- Send thousands of log entries in a single request using NDJSON format

Quick links

• Quickstart -- Send your first log entry in 5 minutes
• Ingestion Guide -- Single and batch ingestion, log schema, and best practices
• Alerts Guide -- Set up threshold-based alerts with email and webhook notifications
• Projects API -- Create and manage log projects
• Search & Export API -- Search logs and export results
• Alerts API -- CRUD endpoints for alert rules
• Ingest API -- Send log entries (single and batch)

Base URL

https://app.krafter.dev/api/v1

Dual authentication

Krafter Logs uses two types of tokens:

• Team API key (Authorization: Bearer kr_live_...) -- for project management, search, alerts, and export
• Project ingest token (Authorization: Bearer krl_live_...) -- for sending log entries via the ingest endpoints

Ingest tokens are generated per-project when you create a project. See Quickstart for details.

Token prefixes

Krafter uses two distinct token formats:

• Team API keys: kr_live_... -- used for project, alert, and search endpoints
• Project ingest tokens: krl_live_... -- used only for /logs/ingest and /logs/ingest/batch

Project responses include ingest_token_prefix (the first 12 characters, e.g. krl_live_kp7) for identification. The full ingest_token is returned only on creation and rotation -- store it securely. Lost tokens cannot be recovered, only rotated.

API requests are subject to platform rate limits — log ingest uses a dedicated log_ingest bucket keyed by project ingest token.