log anomaly detection via BERT
active 2023-08-16 → 2026-07-01 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1051 days from 2023-08-16 to 2026-07-01. Pushes: 1 total, peak 1 in a day. Pull requests: 4 total, peak 1 in a day. Issues: 10 total, peak 2 in a day. Comments: 22 total, peak 3 in a day. Stars: 168 total, peak 3 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| LINBEIXL | 6 | 0 | 0 | 3 |
| 2718455213wcx | 4 | 0 | 0 | 3 |
| AvaIon | 2 | 0 | 0 | 2 |
| PT-DKNS | 2 | 0 | 0 | 0 |
| cristianohello | 1 | 0 | 0 | 1 |
| AYUSH1382 | 1 | 0 | 0 | 1 |
| vnaticzhock | 1 | 0 | 0 | 1 |
| martinsonorah | 1 | 0 | 0 | 1 |
| kodefoundry | 1 | 0 | 0 | 1 |
| TareqKomboz | 1 | 0 | 0 | 0 |
| yebo852058 | 1 | 0 | 0 | 1 |
| andrus801 | 1 | 0 | 0 | 1 |
| NightBaRron1412 | 1 | 0 | 1 | 0 |
| YifeiLin0226 | 1 | 0 | 0 | 1 |
| srinivaskiranj | 1 | 0 | 0 | 0 |
| Shown842 | 1 | 0 | 0 | 1 |
| gssajith | 1 | 0 | 1 | 0 |
| Ainecop | 1 | 0 | 0 | 0 |
| GarvitSinghal13 | 1 | 0 | 0 | 0 |
| LazyCr0w | 1 | 0 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#9WenTesla2025-08-30 03:02Results are far from the values reported in the paper
- Issue#49PT-DKNS2025-08-22 03:16anomaly_label.csv not found
- Issue comment#47AvaIon2025-08-11 02:09How to use LogBERT on a custom dataset?
- Issue comment#49AvaIon2025-08-11 02:08anomaly_label.csv not found
- Pull request#55NightBaRron14122025-05-08 16:07
- Pull request#54LazyCr0w2025-04-13 11:57
- Issue comment#53yebo8520582025-03-16 07:40"python logbert.py train" fails with message "requested array has an inhomogeneous shape after 1 dimensions"
- Issue comment#49kodefoundry2025-02-25 16:26anomaly_label.csv not found
- Pull request#52pheonixdev2025-02-17 09:37
- Issue comment#49martinsonorah2025-02-08 20:44anomaly_label.csv not found
- Issue#51srinivaskiranj2025-02-07 13:31HDFS Train is failing
- Issue#50TareqKomboz2025-01-24 09:32LogBERT train-loss depends on #GPUs
- Issue comment#49cristianohello2024-12-27 03:56anomaly_label.csv not found
- Issue comment#39Cloudsedger2024-12-14 13:56test_size=68 should be either positive and smaller than the number of samples 34 or a float in the (0, 1) range
- Issue#49PT-DKNS2024-11-12 13:34anomaly_label.csv not found
- Pull request#48gssajith2024-06-21 21:45
- Issue#47GarvitSinghal132024-06-20 06:44How to use LogBERT on a custom dataset?
- Issue comment#43YifeiLin02262024-06-07 20:57Why was the WordVocab generated using only the training set data？
- Issue comment#39andrus8012024-04-22 22:34test_size=68 should be either positive and smaller than the number of samples 34 or a float in the (0, 1) range
- Issue comment#42vnaticzhock2024-03-29 17:13HDFS/python logbert train
- Issue#45Ainecop2024-03-09 12:50Linux log files prediction
- Issue#44LINBEIXL2024-02-28 17:35Seems cannot be applied to detection scenarios where normal logs are mixed with abnormal logs
- Issue#44LINBEIXL2024-02-28 15:45Seems cannot be applied to detection scenarios where normal logs are mixed with abnormal logs
- Issue#43LINBEIXL2024-02-27 15:11Why was the WordVocab generated using only the training set data？
- Issue comment#28LINBEIXL2024-02-26 09:43关于log key中的<*>如何参与Bert的MLM训练
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 168 stars here means stars gained during the window, not the repo's star count.