2008 11th IEEE High Assurance Systems Engineering Symposium 2008
DOI: 10.1109/hase.2008.16
|View full text |Cite
|
Sign up to set email alerts
|

Detection and Diagnosis of Recurrent Faults in Software Systems by Invariant Analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
6
0

Year Published

2009
2009
2012
2012

Publication Types

Select...
5
1
1

Relationship

3
4

Authors

Journals

citations
Cited by 10 publications
(6 citation statements)
references
References 16 publications
0
6
0
Order By: Relevance
“…In addition the observation probabilities need to be adjusted to reflect the expected symptoms for individual faults in Ω. Such observation probabilities can be obtained by analyzing historic monitoring data, as we have shown in previous work [13]- [15], or by incorporating expert knowledge. The reader should note that each action only generates one observation at a time, but individual faults can be identified by multiple symptoms.…”
Section: Incorporating Symptoms Of Known Faultsmentioning
confidence: 99%
See 1 more Smart Citation
“…In addition the observation probabilities need to be adjusted to reflect the expected symptoms for individual faults in Ω. Such observation probabilities can be obtained by analyzing historic monitoring data, as we have shown in previous work [13]- [15], or by incorporating expert knowledge. The reader should note that each action only generates one observation at a time, but individual faults can be identified by multiple symptoms.…”
Section: Incorporating Symptoms Of Known Faultsmentioning
confidence: 99%
“…The diagnostic approaches differ by monitoring data and overhead. To localize abnormal components from application traces we refer the reader to [16], for identifying recurrent faults from log-files to [13], [14], and finally for localizing faulty components the reader is referred to [15], [17]- [19].…”
Section: Incorporating Symptoms Of Known Faultsmentioning
confidence: 99%
“…By merging those samples into one class and then training a Naïve Bayes classifier, one can improve the performance of the Bayesian Classifier. Those particular faults then need to be diagnosed by other means [12,13,21].…”
Section: Dealing With Ambiguous Fault Manifestationsmentioning
confidence: 99%
“…Once a failure is validated (e.g., as described in previous work [12,13,21]), we seek to identify recurrent faults that underlie the observed failure. If the fault that triggered a failure has been seen before, we may be able to fast-track resolution by retrieving information about past actions to restore the failed component.…”
Section: Learning Fault Manifestationsmentioning
confidence: 99%
“…Typically, supervised learning is used such that any recurrent faults can be identified quickly if they were to occur again. Such methods [10], [11], [12] use either Bayesian or neural networks to learn fault symptoms from labeled data. While such efforts significantly improve diagnosis, they suffer from the important drawback that prior fault knowledge is required to diagnose a fault successfully.…”
Section: Fault Diagnosismentioning
confidence: 99%