- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper introduces MCDD, a production-derived VM-level dataset for concurrent degradation detection, and M³-DD, a multi-modal multi-instance detector. MCDD contains 22 metric channels, 122 low-level anomaly-event types, and 25 degradation categories annotated as overlapping, time-bounded intervals. M³-DD combines an anomaly-event encoder, a temporal-signal encoder, interval-aware attention Transformer (IAAT), cross-modal fusion, and an object-query decoder with Hungarian set matching.
Critical strengths
- Existing cloud/microservice benchmarks mostly use binary or point labels, single root causes, or window-level annotations. MCDD preserves overlapping, typed, time-bounded degradation events per VM, which is closer to practice diagnosis.
- M³-DD combines multiple-instance learning with temporal-boundary regression to identify the categories and recorded intervals of overlapping faults.
Critical weaknesses
- The constructed dataset lacks a considerable amount of details. For instance, there is no detailed description of the 25 degradation categories, and the full paper also lacks visualizations related to the dataset.
- This method utilizes low-level metric-derived anomaly events as auxiliary inputs. In real-world scenarios, where these data should be obtained?
- The references are completely outdated and seriously lack research conducted in 2025-2026.
Questions for authors
- Why low-level metric-derived anomaly events can be utilized in an anomaly task scenario? Although these annotations are present in the benchmark proposed in this paper, in real-world scenarios, these data should all be missing.
- Are the auxiliary inputs also required during testing?
- Given that no additional materials were provided, could a complete and detailed explanation to the dataset be offered?