Event logs are the first place where to find useful information about application failures. Event logs are available at different system levels, such as application, middleware and operating system. In this paper we analyze the failure reporting capability of event logs collected at different levels of an industrial system in the Air Traffic Control (ATC) domain. The study is based on a data set of 3,159 failures induced in the system by means of software fault injection. Results indicate that the reporting ability of event logs collected at a given level is strongly affected by the type of failure observed at runtime. For example, even if operating system logs catch almost all application crashes, they are strongly ineffective in face of silent and erratic failures in the considered system.
What Logs Should You Look at When an Application Fails? Insights from an Industrial Case Study / Cinque, Marcello; Cotroneo, Domenico; DELLA CORTE, Raffaele; Pecchia, Antonio. - (2014), pp. 690-695. (Intervento presentato al convegno 2014 44th Annual IEEE/IFIP International Conference on Dependable Systems and Networks tenutosi a Giugno 2014) [10.1109/DSN.2014.69].
What Logs Should You Look at When an Application Fails? Insights from an Industrial Case Study
CINQUE, MARCELLO;COTRONEO, DOMENICO;Raffaele Della Corte;PECCHIA, ANTONIO
2014
Abstract
Event logs are the first place where to find useful information about application failures. Event logs are available at different system levels, such as application, middleware and operating system. In this paper we analyze the failure reporting capability of event logs collected at different levels of an industrial system in the Air Traffic Control (ATC) domain. The study is based on a data set of 3,159 failures induced in the system by means of software fault injection. Results indicate that the reporting ability of event logs collected at a given level is strongly affected by the type of failure observed at runtime. For example, even if operating system logs catch almost all application crashes, they are strongly ineffective in face of silent and erratic failures in the considered system.File | Dimensione | Formato | |
---|---|---|---|
What_Logs_Should_You_Look_at_When_an_Application_Fails_Insights_from_an_Industrial_Case_Study.pdf
solo utenti autorizzati
Tipologia:
Versione Editoriale (PDF)
Licenza:
Copyright dell'editore
Dimensione
388.3 kB
Formato
Adobe PDF
|
388.3 kB | Adobe PDF | Visualizza/Apri Richiedi una copia |
I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.