Logs
Ingestion
Push accepted log events to Mydle. Only validated records count toward volume and appear in search — nothing is fabricated when the endpoint is quiet.
Endpoint
POST /api/logs/v1/ingest on the product host (or your deployment origin). Auth: Authorization: Bearer lt_… or sk_live_…. Optional Content-Encoding: gzip.
Payload
- JSON object, array,
{ "logs": [...] }, or OTEL-compatibleresourceLogs. - Batch ceiling: up to 500 records per request.
- Levels:
trace,debug,info,warn,error,fatal. - Stable
eventIdenables idempotent replay protection; events without it remain accepted but cannot be deduplicated. - Optional correlation fields:
traceId,spanId,sessionId,requestId(OTEL attribute aliases accepted on ingest).
Volume
Usage is measured as canonical validated event JSON bytes after redaction and before persistence.
- Free: 0 (feature disabled).
- Pro: 10 GiB / month.
- Team: 100 GiB / month.
- Enterprise: Team-parity volume in code until a contract override is applied.
Limitations
- Requires
log_management. - Storage is Postgres — not ClickHouse for logs.
- Oversized or invalid payloads are rejected; they do not appear as partial invented rows.