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
Can You Really Pentest Any Site with ARTEX AI?
0dev.to
Keeping n8n maintainable as a small team: sub-workflows, naming and a few house rules
0dev.to

Claude Jira: Built for Tickets, Slow at Team Metrics
0dev.to
Rent, License or Build a Multi-Asset Trading Terminal: What the Company Owns and When to Switch
0dev.to
The AI Verification Gap: Review AI Code Without Rubber-Stamping It
0dev.to
Why Your Next.js App Overflows PostgreSQL Connections (And How to Fix It)
0dev.to