CoChat

Automatic abnormal log detection by analyzing log history for providing debugging insight

Kim, Jinhan, Savchenko, Valeriy, Shin, Kihyuck, Sorokin, Konstantin, Jeon, Hyunseok, Pankratenko, Georgiy, Markov, Sergey, Kim, Chul-Joo · 2020 · Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering: Software Engineering in Practice
Cited by 19

The DOI matches its Crossref record.

Abstract

As the size of software becomes larger and more complex, finding the cause of defects becomes increasingly difficult. Moreover, it is hard to reproduce defects when many components such as processes in platform environment or devices in IoT environment are involved. In this case, analyzing logs are the only way to get debugging insights, but manual log analysis is highly labor intensive work. In this paper, we propose a new log analysis system called historian which runs based on history of test logs. Our system first computes importance and noise scores of each log line by using statistical text mining techniques, and then highlights abnormal log lines based on computed scores for providing debugging insights. We applied historian to Tizen Native API test logs, and our system highlighted only about 4% log lines in average. We also provided highlighted failed logs to Tizen developers and the developers said that failure related log lines were highlighted well. These experimental results show that our system effectively highlights abnormal log lines and provides debugging insights to developers.

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3377813.3381371

Cites

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cited by

See all 19

Metadata

Authors
Kim, J., Savchenko, V., Shin, K., Sorokin, K., Jeon, H., Pankratenko, G., Markov, S., & Kim, C.-J.
Venue
Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering: Software Engineering in Practice
Publisher
ACM
Published
2020-06-27
Pages
71-80
OpenAlex
W3089589468
Cited by
19
References
0
FWCI
1.22
Type
conference paper
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Automatic abnormal log detection by analyzing log history for providing debugging insight. https://app.cochat.ai/papers/10.1145/3377813.3381371
The paper
Kim, J., Savchenko, V., Shin, K., Sorokin, K., Jeon, H., Pankratenko, G., Markov, S., & Kim, C.-J. (2020). Automatic abnormal log detection by analyzing log history for providing debugging insight. Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering: Software Engineering in Practice. https://doi.org/10.1145/3377813.3381371

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.