Who is to Blame? Runtime Verification of Distributed Objects with Active Monitors

TL;DR

This paper presents a practical approach for distributed runtime verification of object-oriented systems by extending Larva with active objects, enabling flexible monitoring architectures and blame assignment between objects and environment.

Contribution

It introduces a method to enhance Larva for distributed monitoring using active objects, and demonstrates property-based blame analysis in distributed systems.

Findings

Effective distributed monitoring architecture using active objects

Blame can be split between local objects and environment

Validated with a distributed key/value store case study

Abstract

Since distributed software systems are ubiquitous, their correct functioning is crucially important. Static verification is possible in principle, but requires high expertise and effort which is not feasible in many eco-systems. Runtime verification can serve as a lean alternative, where monitoring mechanisms are automatically generated from property specifications, to check compliance at runtime. This paper contributes a practical solution for powerful and flexible runtime verification of distributed, object-oriented applications, via a combination of the runtime verification tool Larva and the active object framework ProActive. Even if Larva supports in itself only the generation of local, sequential monitors, we empower Larva for distributed monitoring by connecting monitors with active objects, turning them into active, communicating monitors. We discuss how this allows for a variety of monitoring architectures. Further, we show how property specifications, and thereby the generated monitors, provide a model that splits the blame between the local object and its environment. While Larva itself focuses on monitoring of control-oriented properties, we use the Larva front-end StaRVOOrS to also capture data-oriented (pre/post) properties in the distributed monitoring. We demonstrate this approach to distributed runtime verification with a case study, a distributed key/value store.