what problem does iocane solve?
multi-agent systems often fail due to coordination issues (fan-out, retry storms) that traditional apms miss. iocane explains why these failures happen by analyzing agent behaviors.
is iocane real-time?
analysis is near-real-time (seconds latency), focused on post-hoc diagnosis rather than inline blocking.
do you store my prompts?no. iocane operates on metadata (spans, timings, errors). payload capture is opt-in and disabled by default.
what data do you store?
trace metadata (ids, timestamps), agent graphs, incident reports, and aggregated metrics. raw telemetry is retained for a configurable, limited period.
is cli login required for ingestion?no. the cli is only for setup. once the ingest key is generated and stored in your environment (.env), ingestion works independently of the cli.
what languages are supported?
any language compatible with opentelemetry (python, node.js, go, java, etc.). iocane is framework-agnostic.
how secure is iocane?
ingest keys are environment-scoped and stored as secure hashes. all traffic uses tls. we do not read your application payloads.
can i use this with kubernetes or vms?
yes. iocane connect supports various environments. for kubernetes and vms, manual configuration of your otel exporter is fully supported. please refer to the integration section or use the reference configuration below.