CoChat

The DOI matches its Crossref record; 95 of the 95 references it cites were found in a registry or an index; 12 of the 32 sources its claims cite were checked for support.

Practitioners’ Expectations on Log Anomaly Detection

Open access
Ma, Xiaoxue, Li, Yishu, Keung, Jacky, Yu, Xiao, Zou, Huiqi, Yang, Zhen, Sarro, Federica, Barr, Earl T. · 2025 · IEEE Transactions on Software Engineering

Abstract

Log anomaly detection has become a common practice for software engineers to analyze software system behavior. Despite significant research efforts in log anomaly detection over the past decade, it remains unclear what are practitioners’ expectations on log anomaly detection and whether current research meets their needs. To fill this gap, we conduct an empirical study, surveying 312 practitioners from 36 countries about their expectations on log anomaly detection. In particular, we investigate various factors influencing practitioners’ willingness to adopt log anomaly detection tools. We then perform a literature review on log anomaly detection, focusing on publications in premier venues from 2015 to 2025, to compare practitioners’ needs with the current state of research. Based on this comparison, we highlight the directions for researchers to focus on to develop log anomaly detection techniques that better meet practitioners’ expectations.

Overview

CoChat Summary

TL;DR

This empirical study surveys 312 practitioners from 36 countries and interviews 15 professionals to identify expectations for log anomaly detection, then compares those expectations with 36 premier-venue papers from 2014–2024. It finds strong practitioner demand for automated tools but major gaps in interpretability, generalizability, customization, privacy, and use of metrics/traces.

Key findings

  • 95.5% of surveyed practitioners consider automated log anomaly detection tools essential or worthwhile, yet only 55.8% currently use log monitoring tools for anomaly detection; one-third of those tools cannot automatically identify anomalies.
  • Practitioners prioritize correct detection: over 70% expect recall and precision above 60%, and 70.5% prefer log sequence-level detection, with 29.5% preferring log event-level detection.
  • Data availability exceeds research use: 83.7% and 74.9% of practitioners report metrics and traces as always or sometimes available, but only 4 of 36 reviewed papers incorporate metrics or traces.
  • The literature review finds only 6 papers explicitly perform log event-level detection, over half do not mention detection time, and few or no papers address interpretability, generalizability, customization, or privacy protection.

Methods

  • Mixed-methods design: semi-structured interviews with 15 professionals from eight IT companies (average 8.07 years experience), followed by an online survey of 312 practitioners from 36 countries.
  • Survey analysis used percentages for single/multiple-choice questions and Likert-scale charts; open-ended responses were qualitatively analyzed, with “I don’t know” ratings excluded (<1% of valid responses).
  • Literature review searched IEEE, ACM, DBLP, and Google Scholar for 2014–2024 premier-venue publications, applied inclusion criteria and forward snowballing, and identified 36 papers; two authors analyzed capabilities across nine factors.

Limitations

  • The paper states that some practitioners may not fully comprehend the questions, mitigated by instructions, a flow chart, and excluding “I don’t know” responses.
  • The paper states the sample does not encompass all software engineers, is limited to company practitioners and GitHub contributors, and excludes practitioners not proficient in English or Chinese; additional adoption factors may exist.
  • Evident from the text: recruitment through social/professional circles and GitHub contributors may introduce selection bias, and the literature review is restricted to premier venues and specific inclusion criteria, so it may not represent all log anomaly detection research.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1109/tse.2025.3586700

Cites

95 of 95 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Figures

Fig. 1 The overview of the research methodology.
Fig. 1 The overview of the research methodology.CC-BY-NC-SA · From the PDF
Fig. 2 The percentages of tool usage for log anomaly detection.
Fig. 2 The percentages of tool usage for log anomaly detection.CC-BY-NC-SA · From the PDF
Fig. 3 Data resource availability for log anomaly detection.
Fig. 3 Data resource availability for log anomaly detection.CC-BY-NC-SA · From the PDF
Fig. 4 The current issues with log monitoring tools for log anomaly detection.
Fig. 4 The current issues with log monitoring tools for log anomaly detection.CC-BY-NC-SA · From the PDF
Fig. 5 The importance of automated log anomaly detection tools.
Fig. 5 The importance of automated log anomaly detection tools.CC-BY-NC-SA · From the PDF
Fig. 6 The granularity of automated log anomaly detection tools.
Fig. 6 The granularity of automated log anomaly detection tools.CC-BY-NC-SA · From the PDF
Fig. 7 The factors affecting practitioners' acceptance of using automated log anomaly detection tools.
Fig. 7 The factors affecting practitioners' acceptance of using automated log anomaly detection tools.CC-BY-NC-SA · From the PDF
Fig. 8 The surveyed practitioners' satisfaction rate in terms of effectiveness.
Fig. 8 The surveyed practitioners' satisfaction rate in terms of effectiveness.CC-BY-NC-SA · From the PDF
Fig. 9 The surveyed practitioners' satisfaction rate with various capability ranges in terms of efficiency and scalability.
Fig. 9 The surveyed practitioners' satisfaction rate with various capability ranges in terms of efficiency and scalability.CC-BY-NC-SA · From the PDF
Fig. 10 The surveyed practitioners' satisfaction in terms of privacy protection.
Fig. 10 The surveyed practitioners' satisfaction in terms of privacy protection.CC-BY-NC-SA · From the PDF

Verification

Claims the paper makes

3 Valid · 9 Not valid · 9 Not checked · 163 Own results and interpretations

123 more claims

Create a free account to see all 184 claims and to verify the 4 references still open.

See all claims — free account
  • Probably not a substantial claim. 29
  • It may state two separate claims as one. 33
  • The quote only partly states this claim. 2

Create a free account to see these claims.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 95 references

Research works printed but not linked: 2

  1. Leavy, 2022, Research Design: Quantitative, Qualitative, Mixed Methods, Arts-Based, and Community-Based Participatory Research Approaches
  2. Spencer, 2009, Card Sorting: Designing Usable Categories

Cited by

See all 21

Metadata

Authors
Ma, X., Li, Y., Keung, J., Yu, X., Zou, H., Yang, Z., Sarro, F., & Barr, E. T.
Affiliations
  • Hong Kong Metropolitan University (HK)
  • City University of Hong Kong (HK)
  • Zhejiang University (CN)
  • Johns Hopkins University (US)
  • Shandong University (CN)
  • University College London (GB)
Venue
IEEE Transactions on Software Engineering
Published
2025-09
Volume
51
Issue
9
Pages
2455-2471
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W4413478212
Cited by
21
References
84
Citations by year
2026: 16 · 2025: 5
FWCI
6.57
Type
journal article
Language
en
Open access
Locations
  • IEEE Transactions on Software Engineering (publishedVersion)
  • arXiv (Cornell University) (submittedVersion, cc-by-nc-sa)
  • UCL Discovery (University College London) (submittedVersion)
  • arXiv (Cornell University)
Funders
Research Ethics Committee of the Hong Kong Metropolitan University (HE-SF2025/19)
Topics
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
log anomaly detection, practitioner expectations, technology adoption, software logging, software monitoring, research-practice gap

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.

The claim verdicts this report counts are experimental: their accuracy is not yet measured.

A language model drew the claims from the paper on 2026-11-10, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-11-10 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

Cited sources are checked with a language model’s help (qwen3.8-omni-flash and gpt-6-sol).

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: Practitioners’ Expectations on Log Anomaly Detection. https://app.cochat.ai/papers/10.1109/tse.2025.3586700
The paper
Ma, X., Li, Y., Keung, J., Yu, X., Zou, H., Yang, Z., Sarro, F., & Barr, E. T. (2025). Practitioners’ Expectations on Log Anomaly Detection. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2025.3586700

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.