SkyWalking Ships a Three-Layer AI Stack That Reads Traces So You Don't Have To
Distributed tracing has always produced more data than most on-call engineers can interpret under pressure. SkyWalking's AI assistant collapses the 20-minute drill of flipping through trace lists, reading span trees, and correlating logs into a single question, while the GenAI dashboard gives teams that ship LLM-powered features their first real view of per-call cost and latency.
SkyWalking's new AI capabilities ship across three independent layers. Horizon UI AI Assistant answers natural-language questions by querying live OAP data and rendering real charts, not just text summaries. Virtual GenAI instruments every LLM call made through Spring AI or OpenAI SDKs, surfacing latency percentiles, token counts, TTFT, and estimated cost per model. AI Pipeline connects to an external gRPC service for ML-based baseline calculation and URI pattern recognition, flagging anomalies without manual thresholds. Each layer can be adopted separately, and the assistant defaults to off so teams control which model endpoint it hits — local Ollama or a cloud API — keeping data in-region.
SkyWalking's AI strategy is additive, not a rewrite — each layer bolts onto the existing OAP and agent architecture, which lowers the adoption risk for teams already running it in production.
Making the assistant default-off and model-agnostic sidesteps the enterprise objection that AI features will leak observability data to a third-party cloud.
GenAI monitoring addresses a genuine blind spot: most teams deploying LLM features have no per-request cost or latency visibility, so they optimize prompts and model selection by guesswork.
The assistant's 'show, don't describe' design — rendering real charts instead of hallucinated text — is a practical hedge against LLM confabulation in an operational context where wrong numbers trigger wrong decisions.