Papers › Loghub: A Large Collection of System Log Datasets for AI-driven Log Analytics

Loghub: A Large Collection of System Log Datasets for AI-driven Log Analytics

14 Aug 2020arXiv:2008.06448links table onlyarchive 2025-07-28

Jieming Zhu, Shilin He, Pinjia He, Jinyang Liu, Michael R. Lyu

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Logs have been widely adopted in software system development and maintenance because of the rich runtime information they record. In recent years, the increase of software size and complexity leads to the rapid growth of the volume of logs. To handle these large volumes of logs efficiently and effectively, a line of research focuses on developing intelligent and automated log analysis techniques. However, only a few of these techniques have reached successful deployments in industry due to the lack of public log datasets and open benchmarking upon them. To fill this significant gap and facilitate more research on AI-driven log analytics, we have collected and released loghub, a large collection of system log datasets. In particular, loghub provides 19 real-world log datasets collected from a wide range of software systems, including distributed systems, supercomputers, operating systems, mobile systems, server applications, and standalone software. In this paper, we summarize the statistics of these datasets, introduce some practical usage scenarios of the loghub datasets, and present our benchmarking results on loghub to benefit the researchers and practitioners in this field. Up to the time of this paper writing, the loghub datasets have been downloaded for roughly 90,000 times in total by hundreds of organizations from both industry and academia. The loghub datasets are available at https://github.com/logpai/loghub.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

The archive's official repository (logpai/loghub) was not harvested; the 7 samples below come from 2 community repositories.

Syntology 7 code samples harvested from 2 repositories linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 7 samples from 2 repositories, 7 ran (6 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

logpai/loghub officialmentioned in papermentioned on GitHubNOASSERTIONSyntology: not harvested report
Netflix/derand mentioned on GitHubpytorchApache-2.0Syntology: not harvested report
R-SPIRIT/Domain-LOA mentioned on GitHubtfSyntology: not harvested report
WraySmith/log-anomaly mentioned on GitHubtfMITSyntology: 6 samples, 6 ran (0 instrument-failed) · 0 unverified report
forallx94/log_anomaly_detection mentioned on GitHubtfSyntology: not harvested report
logpai/loghub-2.0 mentioned on GitHubSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
logpai/logpub mentioned on GitHubNOASSERTIONSyntology: not harvested report
spilabkorea/Domain-LOA mentioned on GitHubtfSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
6ran

Licence: 1 of the 7 samples is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

WraySmith/log-anomaly community (archive-listed) 6 samples, 6 ran (0 instrument-failed) · 0 unverified
collect_event_ids process/sliding_window_processor.py ran MIT (permissive) · c1d297b6d97af37d · report fixture: signature data_frame:DataFrame/0/?, regex_pattern:str/0/str, column_names:list/1/str · returned DataFrame · level recorded 2026-09-24
comExit parse/logparser/LKE/LKE.py ran MIT (permissive) · 081605aaa2a31f86 · report fixture: signature commonPart:set/0/?, seq:list/1/int · returned bool · level recorded 2026-09-24
listContained parse/logparser/LKE/LKE.py ran fingerprinted MIT (permissive) · 18ea37d0aa8f9bca · report fixture: signature group:list/1/int · returned bool · level recorded 2026-09-24
posiToSplit parse/logparser/LKE/LKE.py ran MIT (permissive) · 1fb2cf516043ba9f · report fixture: signature eachGroup:list/1/list, split_threshold:int/0/int · returned dict · level recorded 2026-09-24
sequence_padder process/sliding_window_processor.py ran fingerprinted MIT (permissive) · 1d16cdb68d278df7 · report fixture: signature sequence:ndarray/1/int, required_length:int/0/int · returned ndarray · level recorded 2026-09-24
windower process/sliding_window_processor.py ran fingerprinted MIT (permissive) · 535ebf130648bbc5 · report fixture: signature sequence:ndarray/1/float, window_size:int/0/int · returned ndarray · level recorded 2026-09-24
logpai/loghub-2.0 community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
get_accuracy in 52 papers
census: 4 implementations from 6 papers, 4 distinct outputs across 4 buckets, one shared input per bucket
benchmark/LogPPT/logppt/evaluation/evaluator.py ran · our draft was wrong licence not identified · pointer only · 04e9124a19f95d56 · report fixture: signature series_groundtruth:Series/1/int, series_parsedlog:Series/1/int, debug:bool/0/bool · returned tuple · level recorded 2026-09-22

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections