The Trace Compass move to the cloud
summary
Eclipse Trace Compass moves to a cloud architecture with a decoupled backend and Theia-based frontend, aiming to handle gigabytes or terabytes of traces by processing events with filtering and aggregation to reduced to kilobytes or megabytes before persistence on the server. The cut sits at the view level (not the widget), so views carry minimal intelligence. A Trace Server Protocol (TSP), inspired by LSP and using REST/JSON, is implemented; the data model already exists in classic Trace Compass and is being exposed for cloud use.
AI-written summary · about
chapters (7)
- 0:00Trace Compass Lightning Talk
- 1:00What is Trace Compass
- 1:43Migrating to a distributed approach
- 2:34Trace Compass is a Special Case...
- 3:01A Look at the Data Flow
- 3:50Rationale
- 4:48References
related talks
25mCDT Cloud, Embedded SIG, Cloud Dev Tools, OpenVSX and how they all play together
47mThrough the Looking Glass: Effective Observability for Cloud-Native Applications
29mIntroducing Astrolabe: Open-Source Cloud Infrastructure Mapping
27mVisualizing Cloud Systems
26mPerformance Analysis of Cloud Applications
45mVisualizing Cloud Systems
33mSpeed is key: Leveraging the Cloud for Forensic Artifact Collection & Processing
46mObservability best practices for hybrid environments
