000 04425naa a22005297i 4500
001 UMUN-OA-20261005-SE-062
003 local
005 20261005174822.0
006 m o d
007 cr||||||||||||
008 261005s2023 xx o u000 0 eng d
024 7 _a10.1016/j.jksuci.2023.02.010
_2doi
035 _a(local)OpenAlex:W4320921281
040 _alocal
_beng
_clocal
041 0 _aeng
100 0 _aAhmed Hany Fawzy
_eauthor.
245 1 0 _aFramework for automatic detection of anomalies in DevOps /
_cAhmed Hany Fawzy; Khaled Wassif; Hanan Moussa.
264 1 _a[Place of publication not identified] :
_bElsevier BV,
_c2023.
300 _a1 online resource (1 article).
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
500 _aPublication type: Journal article.
500 _aLinked open-access copy: published version.
506 0 _aOpen access; no subscription required for the linked open-access version.
_fUnrestricted online access
_2star
520 3 _aLog-based anomaly detection is important for improving the reliability and availability of software systems, especially those evolving using DevOps, owing to the huge number of logs generated during continuous practices. However, DevOps practitioners typically inspect and interpret the generated data and logs manually on specific occasions as part of the troubleshooting process. This process of manual inspection is time consuming and challenging because these data and logs have grown to an unmanageable size owing to the increasing size and complexity of the systems. In this research paper, we introduce the DevOps Anomaly Detection Framework (DADF). DADF is composed of two components that rely on Machine Learning (ML) and Artificial Intelligence (AI) to analyze the data and logs generated during DevOps practices to automatically detect anomalies. The first component is Anomaly Detection Before Production (ADBP), which intends to detect anomalies in the prospective release before its operation in the production environment by adopting the Local Outlier Factor (LOF) technique on the data collected during implementation, building, testing, and deployment. The second component is Anomaly Detection After Staging (ADAS), which intends to detect anomalies after the operation of the released system by adopting the Vector Auto-Regression (VAR) technique on the data collected during monitoring from the system log, application log, and performance metrics (CPU and memory). We experimentally evaluated ADBP and ADAS in two different real-world industrial projects. The experimental results demonstrated that the accuracy, precision, recall, and F1-score of the ADBP component were 96%, 87.5%, 100%, and 93.3%, respectively, and the normalized Root Mean Squared Error (nRMSE) of the ADAS component was 2–19%. Hence, the results demonstrate the effectiveness of DADF in helping DevOps practitioners and researchers automatically detect anomalies throughout the lifecycle of DevOps by monitoring all DevOps’ practices.
540 _aCreative Commons Attribution-NonCommercial-NoDerivatives (licence family recorded by the source; version not supplied in metadata).
_uhttps://openalex.org/W4320921281
546 _aIn English.
588 0 _aDescription generated from OpenAlex bibliographic metadata retrieved on 5 October 2026; full text linked from the source.
590 _aCourse allocation: B. Sc. Software Engineering.
650 4 _aanomaly detection
650 4 _aDevOps
650 4 _alog analysis
650 4 _asoftware reliability
650 4 _alocal outlier factor
650 4 _asystem monitoring
653 _aB. Sc. Software Engineering
653 _aUMUN open access collection
653 _aDevOps
655 4 _aJournal articles.
700 0 _aKhaled Wassif
_eauthor.
700 0 _aHanan Moussa
_eauthor.
773 0 _tJournal of King Saud University - Computer and Information Sciences
_gVol. 35, no. 3, (2023), pages/article 8-19
_x1319-1578
856 4 0 _uhttps://doi.org/10.1016/j.jksuci.2023.02.010
_yRead open-access publication
_zOpen access. Access and licence reported by the source; this host could not be independently checked by automation.
_70
884 _aCourse selection and automated MARC21 enrichment from OpenAlex metadata.
_g20261005
_khttps://openalex.org/W4320921281
_qlocal
942 _n0
999 _c554
_d554