Automated Analysis of Distributed Tracing: Challenges and Research Directions

• Published in: Journal of grid computing 2021-03, Vol.19 (1), Article 9
• Main Authors: Bento, Andre, Correia, Jaime, Filipe, Ricardo, Araujo, Filipe, Cardoso, Jorge
• Format: Article
• Language: English
• Subjects: Anomalies; Automation; Computer Science; Context; Management of Computing and Information Systems; Processor Architectures; Scientific visualization; Software development; Tracing; User Interfaces and Human Computer Interaction
• ISSN: 1570-7873; 1572-9184
• DOI: 10.1007/s10723-021-09551-5

Microservice-based architectures are gaining popularity for their benefits in software development. Distributed tracing can be used to help operators maintain observability in this highly distributed context, and find problems such as latency, and analyse their context and root cause. However, exploring and working with distributed tracing data is sometimes difficult due to its complexity and application specificity, volume of information and lack of tools. The most common and general tools available for this kind of data, focus on trace-level human-readable data visualisation. Unfortunately, these tools do not provide good ways to abstract, navigate, filter and analyse tracing data. Additionally, they do not automate or aid with trace analysis, relying on administrators to do it themselves. In this paper we propose using tracing data to extract service metrics, dependency graphs and work-flows with the objective of detecting anomalous services and operation patterns. We implemented and published open source prototype tools to process tracing data, conforming to the OpenTracing standard, and developed anomaly detection methods. We validated our tools and methods against real data provided by a major cloud provider. Results show that there is an underused wealth of actionable information that can be extracted from both metric and morphological aspects derived from tracing. In particular, our tools were able to detect anomalous behaviour and situate it both in terms of involved services, work-flows and time-frame. Furthermore, we identified some limitations of the OpenTracing format—as well as the industry accepted tracing abstractions—, and provide suggestions to test trace quality and enhance the standard.