{"title":"Proactive monitoring of the information system risk and quality","authors":"A. Trad, D. Kalpić, K. Fertalj","doi":"10.1109/ITI.2002.1024687","DOIUrl":null,"url":null,"abstract":"Proactive system monitoring is the search for potential problems in the Information Systems (IS) before they occur. With reference to IS, monitoring is always proactive. Watching for evidence of emerging or potential problems and identifying their source (factor), checking available disk space, the health of essential processes, probing systems to ensure that they are reachable, business requirement fulfilment; these are all examples of detecting problems before they disrupt the work/flow of an IS. Monitoring is not something that should be cavalierly put off until there's nothing else on the development team's schedule to be done. As soon as the IS is put in production, it is time to start to protect it against all possible types of problems.","PeriodicalId":420216,"journal":{"name":"ITI 2002. Proceedings of the 24th International Conference on Information Technology Interfaces (IEEE Cat. No.02EX534)","volume":"40 2 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2002-11-07","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"12","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"ITI 2002. Proceedings of the 24th International Conference on Information Technology Interfaces (IEEE Cat. No.02EX534)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ITI.2002.1024687","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 12
Abstract
Proactive system monitoring is the search for potential problems in the Information Systems (IS) before they occur. With reference to IS, monitoring is always proactive. Watching for evidence of emerging or potential problems and identifying their source (factor), checking available disk space, the health of essential processes, probing systems to ensure that they are reachable, business requirement fulfilment; these are all examples of detecting problems before they disrupt the work/flow of an IS. Monitoring is not something that should be cavalierly put off until there's nothing else on the development team's schedule to be done. As soon as the IS is put in production, it is time to start to protect it against all possible types of problems.