Earticle

초록

영어

In this study we evaluate a production-style OpenTelemetry (OTel) pipeline on Google Kubernetes Engine (GKE) Autopilot under a sustained trace workload, instrumenting end-to-end ingestion→processing→export and scraping Collector self-telemetry and spanmetrics with Prometheus over a 30-minute run. The Collector averaged 573 spans/s accepted and 561 spans/s exported, yielding 97.84% within-window export efficiency and peaking near 924 spans/s. A brief saturation interval (150 s) produced a queue peak of 6.38, short drops (peak 3.49 spans/s, ~358 total), and p95 inflation to 116 ms; median latency remained low (p50 ≈ 12.9 ms) and recovered after pressure subsided. Resource footprint was modest (≈0.36 CPU cores, 0.21 GiB memory, sub-Mbps network), indicating headroom. We document integration pitfalls (OTLP endpoint/protocol) and show that queue growth and exporter errors anticipate p95 tails. The study contributes reproducible methodology, quantitative evidence of cloud-scale OTel scalability, and operator guidance for capacity planning and alert design.

목차

Abstract
I. INTRODUCTION AND BACKGROUND
II. SYSTEM AND METHODOLOGY
III. RESULTS
A. Throughput and Export Efficiency
B. Latency and Tail Behavior
C. Ackpressure and Drops
D. Resource Footprint
IV. DISCUSSION
V. CONCLUSION AND FUTURE WORK
ACKNOWLEDGMENT
REFERENCES

저자

• Omar Bin Kasim Bhuian [ SysCore Lab, Sejong University Seoul, South Korea ]
• Sang-Hoon Choi [ SysCore Lab, Sejong University Seoul, South Korea ]
• Young-Soo Kim [ Electronics and Telecommunications Research Institute, Seoul, South Korea ]
• Hongri Liu [ Weihai Cyberguard Technologies Co., Ltd., Weihai 264209, China ]
• Ki-Woong Park [ Department of Information Security and Convergence Engineering for Intelligent Drone, Sejong University Seoul 05006, South Korea ]

참고문헌