Almost every product hits two kinds of user pain:
- Can't use it: install fails, won't start, or dies in production — errors only, then humans grep logs and guess commands.
- Don't know how: docs elsewhere, menus buried — ask a helper and get "see the official documentation."
Self-healing ops fixes the first: when storage is down the product stays usable, SSH for evidence, change config, restart, verify.
In-product Q&A fixes the second: ask the product in natural language; answers come from in-product docs and your deployment.
DataBuff is an open-source, AI-native OpenTelemetry APM — metrics, traces, logs first; AI on the same telemetry. Three pieces: Ingest, Doris, AI platform / Web.
curl -fsSL https://databuff.ai/install.sh | bash
Self-healing in practice: Doris breaks during install. Many products go dark; you SSH and guess. We inject mem_limit: 256m on Doris BE so start.sh exits non-zero. Troubleshooting mode keeps Web up while Doris is unhealthy.
Configure an LLM, open AI chat, pick Ops Expert, grant SSH, ask for locate-and-fix:
I installed DataBuff on 192.168.50.140 (dir /opt/databuff-ai-apm-failover).
install/start failed but Web opens.
SSH to root@192.168.50.140 (password Databuff@123)
Find why Doris FE/BE is not ready; fix root cause and report results.
Install dir: /opt/databuff-ai-apm-failover
On the host: BE Restarting → mem_limit: 256m OOM → memory raised to 4g, config persisted, ingest restarted, full-stack Healthy.
Terminal matches: four containers healthy, Doris SELECT 1 passes. Troubleshooting mode exits automatically.
In-product Q&A on the same AI entry — OTel ingest and alert thresholds:
Then LLM setup — menu paths, required fields, common pitfalls:
In one line: self-healing fixes "can't use it"; in-product Q&A fixes "don't know how."
Top comments (0)