DevOpsDays Taipei 2026 DevOpsDays Taipei 2026

OTel Lakehouse: From O11y to AIOps

"Why isn't my data ready?" — every on-call engineer knows this moment: jumping between dashboards, losing precious minutes while incidents escalate.

We built a unified telemetry lakehouse using OpenTelemetry and Apache Iceberg, cutting investigation time from 30+ minutes to ~8 seconds per query. But the real story is the collaboration model behind it — how platform engineers and domain experts co-designed a three-layer anomaly detection system that catches silent drift and cascading failures before they page anyone, and how we closed the loop with automated ticketing and remediation.

We'll share the bridge pattern for writing telemetry into open table formats, the correlation key model that joins signals across teams, and the cultural shifts that made cross-functional ownership actually work.


聽眾收穫:

Platform engineers, SREs, and data engineers who are tired of context-switching across disconnected observability tools. Attendees will walk away with:

  • A practical blueprint for unifying logs, metrics, and traces into a queryable lakehouse using OTel and Iceberg
  • The bridge pattern for open table format ingestion
  • A three-layer anomaly detection approach that catches what single methods miss
  • The AIOps automation loop: from detection to auto-remediation
  • Collaboration patterns for cross-functional platform and domain teams

All architecture, code, and runbooks are open-source and reproducible.

游舜傑 (Jay)

講者

游舜傑 (Jay)

外商
Data Engineer
LEVEL

中階

LANGUAGE

中文

TAGS
Observability (可觀測性)
適合聽眾
DevOps新手 (Newbie)DevOps老司機 (DevOps Veteran)IT人員 / 偏維運 (IT / OPS)IT人員 / 偏開發 (IT / DEV)經營決策者 (Decision maker)非IT部門 (Non-IT)IT人員 / 全都做 (IT / I have to do everything)