
arXiv: 1708.07232
handle: 10281/177127 , 11383/2118522
Field data is an invaluable source of information for testers and developers because it witnesses how software systems operate in real environments, capturing scenarios and configurations relevant to end-users. Unfortunately, collecting traces might be resource-consuming and can significantly affect the user experience, for instance causing annoying slowdowns. Existing monitoring techniques can control the overhead introduced in the applications by reducing the amount of collected data, for instance by collecting each event only with a given probability. However, collecting fewer events limits the amount of information extracted from the field and may fail in providing a comprehensive picture of the behavior of a program. In this paper we present fragmented monitoring, a monitoring technique that addresses the issue of collecting information from the field without annoying users. The key idea of fragmented monitoring is to reduce the overhead by recording partial traces (fragments) instead of full traces, while annotating the beginning and the end of each fragment with state information. These annotations are exploited offline to derive traces that might be likely observed in the field and that could not be collected directly due to the overhead that would be introduced in a program.
In Proceedings PrePost 2017, arXiv:1708.06889
Software Engineering (cs.SE), FOS: Computer and information sciences, Software, runtime monitoring, software engineering, field data collection, user experience, symbolic execution,, Computer Science - Software Engineering, D.2.5, Electronic computers. Computer science, Software; runtime monitoring; software engineering; field data collection; user experience; symbolic execution, QA1-939, QA75.5-76.95, Mathematics
Software Engineering (cs.SE), FOS: Computer and information sciences, Software, runtime monitoring, software engineering, field data collection, user experience, symbolic execution,, Computer Science - Software Engineering, D.2.5, Electronic computers. Computer science, Software; runtime monitoring; software engineering; field data collection; user experience; symbolic execution, QA1-939, QA75.5-76.95, Mathematics
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 3 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
