Skip to main navigation Skip to search Skip to main content

Automated error log resolution: A case study

  • Mark Fuller
  • , Elizabeth Brighton
  • , Micah Schiewe
  • , Dipta Das
  • , Tomas Cerny
  • , Pavel Tisnovsky

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

Abstract

Debugging and error resolution has become increasingly time-consuming and difficult for all domains of software development. Error logs have become very important when it comes to debugging and error resolution. To remedy the problems presented in the logs, typically, a search on online forums would shed light on the solution. We present a novel approach to utilizing these logs in conjunction with external Question and Answer forums to compute and expedite resolution by suggesting a solution to runtime errors. Since log format is non-standard and use cases can vary widely, our architecture allows for extreme customization for the intended ecosystem as well as a great degree of fine-tuning. We evaluated our solution in a case study and made our implementation open-source for the community.

Original languageEnglish (US)
Title of host publicationProceedings of the 36th Annual ACM Symposium on Applied Computing, SAC 2021
PublisherAssociation for Computing Machinery
Pages1298-1304
Number of pages7
ISBN (Electronic)9781450381048
DOIs
StatePublished - Mar 22 2021
Externally publishedYes
Event36th Annual ACM Symposium on Applied Computing, SAC 2021 - Virtual, Online, Korea, Republic of
Duration: Mar 22 2021 → Mar 26 2021

Publication series

NameProceedings of the ACM Symposium on Applied Computing

Conference

Conference36th Annual ACM Symposium on Applied Computing, SAC 2021
Country/TerritoryKorea, Republic of
CityVirtual, Online
Period3/22/21 → 3/26/21

Keywords

  • defect resolution
  • error logs
  • log analysis
  • StackOverflow

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Automated error log resolution: A case study'. Together they form a unique fingerprint.

Cite this