Backend
Mine Locally, Verify Globally: Exact Recovery, Compilation, and Distortion of Mined Temporal Rules
arXiv cs.DC0 views
arXiv:2611.24902v1 Announce Type: new Abstract: Specification mining extracts temporal rules that describe relationships between events in recorded system traces. Applying these rules in distributed monitoring systems is more difficult because observations come from different nodes, whose clocks may not be synchronized, and events may be lost or reordered during transmission. In this paper, we study how to aggregate the coverage of mined rules across observers, determine whether their temporal windows are needed during monitoring, and characterize their detection under event loss. Our evaluation uses IPv6 packet traces collected from 21 receivers across four continents. We show that local mining followed by global confirmation recovers centralized rule coverage under suitable conditions while substantially reducing communication overhead. In contrast, merging traces with unaligned clocks can distort coverage by introducing incorrect temporal matches. A window-gain criterion identifies rules that require temporal state, while our loss analysis and broker experiments demonstrate why contiguous losses can be more damaging than independent losses. The results identify separate requirements for aggregating observations, selecting monitor state, and handling event loss.
Source:https://arxiv.org/abs/2611.24902PreviousA Runtime System for Mitigating Crossbar Port Contention on SM-Partitioned GPUsNextModel Discovery for Virtual Chaos Engineering with Incomplete Tracing: An eBPF Study
Related posts
Project Contour's zero title count does not clear an ingress policy review
0dev.to

MCP vs API: one task took 5 operations direct and 9 through MCP
0dev.to
Build a cross-marketplace sold-price checker in Python (eBay, Reverb, Poshmark, Mercari)
0dev.to
IFBench on Hugging Face: 0 of 23 Rows Are Verified, and Ranks 1 to 6 Sit Inside One 300-Prompt Error Band
0dev.to
Shipped an Android App with AI? 6 Security Flaws You Must Fix Before Release
0dev.to
Grok translated a Morse code reply and its wallet sent 3 billion tokens. Five agent wallet attacks to run locally, with fixes
0dev.to