TWM580710U - Information Service Availability Management System - Google Patents

Information Service Availability Management System Download PDF

Info

Publication number
TWM580710U
TWM580710U TW108204436U TW108204436U TWM580710U TW M580710 U TWM580710 U TW M580710U TW 108204436 U TW108204436 U TW 108204436U TW 108204436 U TW108204436 U TW 108204436U TW M580710 U TWM580710 U TW M580710U
Authority
TW
Taiwan
Prior art keywords
monitoring
availability
data
capacity
report
Prior art date
Application number
TW108204436U
Other languages
Chinese (zh)
Inventor
吳柏慶
阮呂文欽
韓府錦
Original Assignee
臺灣銀行股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 臺灣銀行股份有限公司 filed Critical 臺灣銀行股份有限公司
Priority to TW108204436U priority Critical patent/TWM580710U/en
Publication of TWM580710U publication Critical patent/TWM580710U/en

Links

Abstract

本創作提供一種資訊服務可用性管理系統,依據設備型號判讀設備效能,以及不同的系統交易量計算不同的網路使用量,設計對應機制及程式模式改善設備監控之可用性,藉由依據服務可用性之相關元件類別,至各監控系統使用監控軟體定期收集效能數值資訊,透過本創作自動產出服務可用性相關所需數據,與業務負責人匯入之可用性資料結合,將每日監控資料彙整計算,以月為單位產出服務可用性報表,提供一種具有高準確度、且能自動、有效地管理資訊服務可用性的系統。 This creation provides an information service availability management system that calculates device performance based on device model and different system transaction volume to calculate different network usage, and designs corresponding mechanisms and program modes to improve device monitoring availability, based on service availability. For the component category, the monitoring system uses the monitoring software to collect the performance value information regularly. Through the creation of the automatic generation of the relevant data related to the availability of the service, combined with the availability data imported by the business owner, the daily monitoring data is calculated and calculated. Provides a system with high accuracy and automatic and efficient management of information service availability for unit output service availability reports.

Description

資訊服務可用性管理系統 Information Service Availability Management System

本創作係關於網路和設備監控系統服務領域,特別是關於一種資訊服務可用性之管理系統。 This creation is about the field of network and device monitoring system services, especially regarding a management system for the availability of information services.

現今銀行業隨著業務的發展,與資通技術的融合度逐漸地加深,因此對於網路和設備效能的依賴度不斷地提升,因此銀行的資訊人員需要瞭解執行各項業務服務時,網路和設備的可用性。 With the development of the business, the integration of the banking industry with the technology has gradually deepened, so the dependence on the performance of the network and equipment is constantly increasing. Therefore, the information personnel of the bank need to understand the network when performing various business services. And the availability of the equipment.

目前在處理資訊服務可用性的問題,係採用各監控系統的監控軟體定期蒐集效能數值資訊,但因交易量太大時會影響網路監控回應,以及設備效能高低會造成回應快慢等問題,影響系統可用性監控之準確度,此外,蒐集到的效能數值資訊,大多使用人工監控統計,容易造成錯誤,無法自動且有效地管理資訊服務之可用性。 At present, in dealing with the availability of information services, the monitoring software of each monitoring system is used to regularly collect performance information. However, when the transaction volume is too large, it will affect the network monitoring response, and the performance of the device will cause problems such as slow response and affect the system. The accuracy of the usability monitoring, in addition, the collected performance statistics information, mostly using manual monitoring statistics, is prone to errors, and can not automatically and effectively manage the availability of information services.

因此,如何提供一種具有高準確度、且能自動、有效地管理資訊服務可用性的方法,則成為一個亟待開發的技術。 Therefore, how to provide a method with high accuracy and automatic and effective management of information service availability becomes a technology to be developed.

本創作提供一種資訊服務可用性管理系統,該系統包括:複數個監控主機,用以蒐集複數個組態之複數個監控測量資料;一第一資料庫,係連接該些監控主機,用以儲存該些監控測量資料,該些資料包含複數個可用性監控資料以及複數個容量監控資料;一分析模組,係連接該 第一資料庫,用以分析該些可用性監控資料以及該些容量監控資料,評估判斷是否有異常訊息或事件發生,若是的話,進行事件與問題管理流程;以及一報表產生模組,係連接該分析模組,若該分析模組評估判斷沒有異常訊息或事件發生,則該報表產生模組產出一可用性監控表與一容量監控表。 The present invention provides an information service availability management system, the system includes: a plurality of monitoring hosts for collecting a plurality of configuration monitoring data; a first database is connected to the monitoring hosts for storing Some monitoring measurement data, the data includes a plurality of availability monitoring data and a plurality of capacity monitoring data; an analysis module is connected to the a first database for analyzing the availability monitoring data and the capacity monitoring data, evaluating whether an abnormal message or an event occurs, and if so, performing an event and problem management process; and a report generating module connecting the The analysis module, if the analysis module evaluates that there is no abnormal message or an event occurs, the report generation module outputs an availability monitoring table and a capacity monitoring table.

本創作依據設備型號判讀設備效能,以及不同的系統交易量計算不同的網路使用量,設計對應機制及程式模式改善設備監控之可用性,藉由依據服務可用性之相關元件類別,至各監控系統使用監控軟體定期收集效能數值資訊,透過本創作自動產出服務可用性相關所需數據,與業務負責人匯入之可用性資料結合,將每日監控資料彙整計算,以月為單位產出服務可用性報表,提供一種具有高準確度、且能自動、有效地管理資訊服務可用性的系統。 This creation is based on the device model to determine the device performance, and different system transaction volume to calculate different network usage, design the corresponding mechanism and program mode to improve the availability of device monitoring, by using the relevant component categories of service availability, to the monitoring system The monitoring software collects the performance value information on a regular basis, and automatically generates the required data related to the service availability through the creation, and combines the daily monitoring data with the availability data imported by the business owner, and outputs the service availability report on a monthly basis. Provide a system with high accuracy and automatic and efficient management of information service availability.

1‧‧‧資訊服務可用性管理系統 1‧‧‧Information Service Availability Management System

10‧‧‧分析模組 10‧‧‧Analysis module

20‧‧‧報表產生模組 20‧‧‧Report generation module

30‧‧‧整合模組 30‧‧‧Integrated module

40‧‧‧匯入模組 40‧‧‧ Import module

DB1‧‧‧第一資料庫 DB1‧‧‧ first database

DB2‧‧‧第二資料庫 DB2‧‧‧Second Database

DB3‧‧‧第三資料庫 DB3‧‧‧ third database

H1,H2,H3,H4‧‧‧監控主機 H1, H2, H3, H4‧‧‧ monitoring host

S110~S140‧‧‧資訊服務可用性管理方法流程步驟 S110~S140‧‧‧Information service availability management method process steps

第一圖係為本創作資訊服務可用性管理方法之流程圖。 The first picture is a flow chart of the method for managing the availability of the creative information service.

第二圖係為本創作產出之可用性監控表。 The second chart is the availability monitoring table for the creative output.

第三圖係為本創作產出之可用性監控報告。 The third picture is the availability monitoring report for the creative output.

第四圖係為本創作產出之容量監控表。 The fourth picture is the capacity monitoring table of the creation output.

第五圖係為本創作產出之容量監控報告。 The fifth picture is the capacity monitoring report of the creative output.

第六圖係為本創作資訊服務可用性管理系統之架構圖。 The sixth picture is the architecture diagram of the creation information service availability management system.

為令本創作所運用之技術內容、創作目的及其達成之功效 有更完整且清楚的揭露,茲於下詳細說明之,並請一併參閱所揭之圖式及圖號。 The technical content, creative purpose and effect achieved by this creation A more complete and clear disclosure is provided below, and please refer to the drawings and drawings.

請參照第一圖,其係為本創作資訊服務可用性管理方法之流程圖,首先,蒐集各組態之複數個監控測量資料(S110),係透過主機監控軟體工具蒐集各組態監控測量資料,此外,亦可由使用者(業務負責人)匯入複數個可用性資料和複數個容量資料,監控測量資料包含:頻寬使用率、處理器使用率、記憶體使用率、硬碟空間使用率;分析與評估該些監控測量資料(S120),係檢視是否達到預定的目標;判斷是否有異常訊息或補救(Remedy)事件發生(S130),若是的話,進行事件與問題管理流程(S135),此步驟係針對非預期性之組態項目失效或容量效能超過臨界值之異常訊息(Event)及事件(Incident)進行通報,進行事件及問題處理,若為事件應開立事件單並透過事件管理流程處理,若否的話,則產出可用性監控表與容量監控表(S140)。 Please refer to the first figure, which is a flow chart of the method for managing the availability of the information service. First, collect a plurality of monitoring and measurement data (S110) of each configuration, and collect monitoring and measurement data of each configuration through the host monitoring software tool. In addition, a plurality of availability data and a plurality of capacity data may be imported by the user (business person in charge), and the monitoring measurement data includes: bandwidth usage rate, processor usage rate, memory usage rate, and hard disk space usage rate; And evaluating the monitoring measurement data (S120), checking whether the predetermined target is reached; determining whether an abnormal message or a remedy event occurs (S130), and if so, performing an event and problem management process (S135), this step It notifies the event and problem of abnormality (Event) and event (Incident) of unexpected configuration project failure or capacity performance exceeding the critical value. If the event should be opened, the event ticket should be opened and processed through the event management process. If not, the availability monitoring table and the capacity monitoring table are output (S140).

在上述流程中,較佳地,事件管理流程處理由「事件通報受理窗口」受理使用者之事件通報,記錄相關資訊並分析事件,提出與執行解決方案或暫時解決方案以儘速恢復受影響之服務。 In the above process, preferably, the event management process processes the event notification of the user accepted by the "Event Notification Acceptance Window", records relevant information and analyzes the event, proposes and executes a solution or a temporary solution to recover the affected as soon as possible. service.

在上述流程中,較佳地,可依據可用性監控表(如第二圖)產出可用性監控報告(如第三圖),並可依據容量監控表(如第四圖)完成容量監控報告(如第五圖),交付服務負責人進行分析。此外,在上述流程中,可進一步依據可用性監控報告和容量監控報告產出一趨勢分析報告,判斷審查是否有潛在問題,審查所負責之服務、組態項目是否有潛在的問題,若是的話,則進行問題管理流程,對於未有暫時解決方案或需尋找根因之事 件開立問題單,將問題單交由負責進行問題分析的支援群組人員進行問題的分析,當調查完成後,進行結案前必須先送主管簽核,待簽核完成後方能進行結案。 In the above process, preferably, the availability monitoring report (such as the third figure) may be generated according to the availability monitoring table (such as the second figure), and the capacity monitoring report may be completed according to the capacity monitoring table (such as the fourth figure) (eg, Figure 5), the delivery service manager performs the analysis. In addition, in the above process, the trend analysis report may be further generated according to the availability monitoring report and the capacity monitoring report to determine whether the review has potential problems, and whether the service and the configuration project in question are potential problems, and if so, Conduct a problem management process for things that don’t have a temporary solution or need to find the root cause Open a questionnaire and submit the questionnaire to the support group responsible for the analysis of the problem. After the investigation is completed, the supervisor must first send the contract before the completion of the case, and the case can be closed after the signing is completed.

本創作可分為服務層(Service)和基礎設施層(Infrastructure)兩個區塊。在可用性計算模式,服務層係依據服務可用性事件(Incident)記錄與系統維護時間(Change)記錄計算資訊服務可用性;基礎設施層則依據服務可用性之相關元件,使用監控軟體與使用者(業務負責人)匯入之可用性資料,以計算服務可用性。進一步地,可用性計算模式包含六個組態分類,服務(Service)、應用(Application)、叢集(Cluster)、軟體伺服器(Software Sever)、電腦系統(Computer System)以及網路裝置(Network Device)。各組態分類依據流程特性訂定各類可量化之關鍵績效指標,可設定優先等級,用以作為具體評估資訊服務管理流程成效之依據。例如,服務(Service)和應用(Application)可將補救(Remedy)事件設定為優先等級1,而叢集(Cluster)、軟體伺服器(Software Sever)、電腦系統(Computer System)和網路裝置(Network Device)則可將使用者(業務負責人)填報設定為優先等級1。 This creation can be divided into two sections: Service Layer and Infrastructure Layer. In the availability calculation mode, the service layer calculates the information service availability based on the service availability event (Cc) record and the system maintenance time (Change) record; the infrastructure layer uses the monitoring software and the user according to the relevant components of the service availability (business leader) ) Importability data is imported to calculate service availability. Further, the availability calculation mode includes six configuration categories, Service, Application, Cluster, Software Sever, Computer System, and Network Device. . Each configuration category defines various quantifiable key performance indicators based on process characteristics, and can be prioritized as a basis for evaluating the effectiveness of the information service management process. For example, Service and Application can set Remedy events to priority level 1, and Cluster, Software Sever, Computer System, and Network Devices. Device) can set the user (business person in charge) to report as priority level 1.

而在容量計算模式,因服務層(Service)無容量定義,故不需要進行定義。而基礎設施層則使用監控軟體與業務負責人匯入之資料,以計算容量。進一步地,容量計算模式包含三個組態分類,軟體伺服器(Software Sever)、電腦系統(Computer System)以及網路裝置(Network Device)。各組態分類依據IT基礎架構的邏輯模型,以識別、管理並確認環境中所有組態項目,流程特性訂定各類可量化之關鍵績效指標,可設定優先等級,用以作為具體評估資訊服務管理流程成效之依據。例如,叢集 (Cluster)、軟體伺服器(Software Sever)、電腦系統(Computer System)和網路裝置(Network Device)可將使用者(業務負責人)填報設定為優先等級1,監控軟體所監控之容量設定為優先等級2。 In the capacity calculation mode, since the service layer has no capacity definition, it does not need to be defined. The infrastructure layer uses the information that the monitoring software and the business owner import to calculate the capacity. Further, the capacity calculation mode includes three configuration categories, a software server (Computer Sever), a computer system (Computer System), and a network device (Network Device). Each configuration classification is based on the logical model of the IT infrastructure to identify, manage and validate all configuration items in the environment. The process characteristics define various quantifiable key performance indicators, which can be prioritized for specific evaluation information services. The basis for managing the effectiveness of the process. For example, cluster (Cluster), Software Server (Computer Sever), Computer System (Computer System) and Network Device (Network Device) can set the user (business person in charge) to be set to priority level 1, and the monitoring software monitors the capacity setting to Priority level 2.

在一實施例中,組態中服務(Service)和應用(Application)係使用補救(Remedy)事件計算每月可用率,其中需先定義停機時間(Down Time),係為每月各服務優先等級(Priority)1與2事件之合計處理時間,因此服務(Service)的可用率定義為:(當月服務時間-停機時間)×100/當月服務時間,應用(Application)的可用率定義為:(當月服務時間-APP CAUSE事件的停機時間)×100/當月服務時間,其中APP CAUSE事件為應用程式換版更新維護、程式BUG導致結果錯誤等事件。 In an embodiment, the Service and Application are configured to calculate the monthly availability rate using a Remedy event, where the Down Time is defined first, which is the monthly service priority. (Priority) The total processing time of 1 and 2 events, so the service availability is defined as: (month service time - downtime) × 100 / current month service time, application (Application) availability rate is defined as: (in the month) Service time - downtime of APP CAUSE event) × 100 / current month service time, where APP CAUSE event is an event such as application update update maintenance, program BUG causing result error.

在一實施例中,組態中網路裝置(Network Device)包含網路交換器(Switch)、路由器(路由器)、負載平衡器(Load balancer)、第三層交換器(Layer 3 Switch)以及防火牆(Firewall)等五個元件分類。而網路裝置(Network Device)的可用率定義為以監控軟體監測,監控時間可為2分鐘,但本創作不以此為限,當可取得數值時,可用性為1,無法取取得數值時,可用性為0。網路裝置(Network Device)的容量定義則分為處理器使用率和頻寬使用率,處理器使用率以當月最大值及當月每日最大值之平均數值等兩個項目作為衡量指標;頻寬使用率則分別以全部使用中介面之最大可接受頻寬值、當月最大值及當月每日最大值之平均數值等三個項目作為衡量指標。監控時間可為1分鐘,但本創作不以此為限。 In an embodiment, the network device in the configuration includes a network switch (Switch), a router (router), a load balancer (Load balancer), a Layer 3 switch (Layer 3 Switch), and a firewall. (Firewall) and other five component categories. The network device (Network Device) availability is defined as monitoring software monitoring, the monitoring time can be 2 minutes, but this creation is not limited to this, when the value can be obtained, the availability is 1, when the value cannot be obtained, Availability is 0. The network device (Network Device) capacity definition is divided into processor usage rate and bandwidth usage rate. The processor usage rate is measured by two items, the maximum value of the current month and the average value of the daily maximum value of the current month; the bandwidth The usage rate is measured by three items, the maximum acceptable bandwidth value of the median, the maximum value of the current month, and the average value of the daily maximum of the current month. The monitoring time can be 1 minute, but this creation is not limited to this.

在一實施例中,組態中電腦系統(Computer System)可包含Unix和Windows兩種。可用率定義為以監控軟體監測,Unix可使用PATROL 監控軟體,監測Patrol data collect可用性,每10分鐘一次,但本創作不以此為限,Windows則可使用SCOM監控軟體,監測SCOM Agent可用性,每10分鐘一次,使用TEC收集Up/Down事件,但本創作不以此為限。容量定義同樣地以監控軟體監測,Unix可使用PATROL監控軟體,監測處理器使用率、記憶體使用率、硬碟空間使用率,依服務時間計算指標值與最大值,其中月指標值等於當月每日尖峰平均,但本創作不以此為限,Windows則可使用SCOM監控軟體,監測處理器使用率、記憶體使用率、硬碟空間使用率,依服務時間計算指標值與最大值,其中月指標值等於當月每日尖峰平均,但本創作不以此為限。 In an embodiment, the Computer System in the configuration may include both Unix and Windows. Availability is defined as monitoring software monitoring, Unix can use PATROL Monitor software and monitor the availability of Patrol data collect every 10 minutes, but this creation is not limited to this. Windows can use SCOM monitoring software to monitor the availability of SCOM Agent. Once every 10 minutes, use TEC to collect Up/Down events, but This creation is not limited to this. The capacity definition is similarly monitored by the monitoring software. Unix can use the PATROL monitoring software to monitor the processor usage, memory usage, and hard disk space usage. The index value and maximum value are calculated according to the service time. The monthly indicator value is equal to the current month. The daily peak average, but this creation is not limited to this, Windows can use SCOM monitoring software to monitor processor usage, memory usage, hard disk space usage, calculate the index value and maximum value according to service time, where month The indicator value is equal to the daily peak average of the month, but this creation is not limited to this.

在一實施例中,組態中軟體伺服器(Software Sever)進一步包含中介軟體(Middleware)、佇列管理器(Queue Manager)以及資料庫伺服器(Database Server)等三個組態。中介軟體(Middleware)可用率定義為以監控軟體監測,例如PATROL監控軟體,監測Appserver可用性,每10分鐘一次,但本創作不以此為限,成功時可用性為1,失敗時可用性為0,容量定義同樣地以監控軟體監測,例如PATROL監控軟體,監測執行緒池(Thread pool)大小,計算指標值與最大值。佇列管理器(Queue Manager)可用率定義為以監控軟體監測,例如PATROL監控軟體,監測Channel可用性,每10分鐘一次,但本創作不以此為限,成功時可用性為1,失敗時可用性為0,佇列管理器(Queue Manager)則無容量定義。資料庫伺服器(Database Server)可用率定義為以監控軟體監測,例如PATROL監控軟體,監測DB2 connect可用性,每10分鐘一次,但本創作不以此為限,成功時可用性為1,失敗時可用性為0,容量定義同樣地以監控軟體監測,例如PATROL監控軟體,監測db file system 大小,計算指標值與最大值。 In an embodiment, the software server (Swareware) in the configuration further includes three configurations of a middleware, a queue manager, and a database server. Middleware availability is defined as monitoring software monitoring, such as PATROL monitoring software, monitoring Appserver availability, once every 10 minutes, but this creation is not limited to this, the availability is 1 when successful, 0 is available when failure, capacity The definition is similar to monitoring software monitoring, such as PATROL monitoring software, monitoring the size of the Thread pool, and calculating the index value and maximum value. The Queue Manager availability rate is defined as monitoring software monitoring, such as PATROL monitoring software, monitoring channel availability, every 10 minutes, but this creation is not limited to this, the availability is 1 when successful, and the availability is 1 when it fails. 0, the Queue Manager has no capacity definition. The database server availability is defined as monitoring software monitoring, such as PATROL monitoring software, monitoring DB2 connect availability, every 10 minutes, but this creation is not limited to this, the availability is 1 when successful, availability at failure For 0, the capacity definition is similar to monitoring software monitoring, such as PATROL monitoring software, monitoring db file system Size, calculate the indicator value and maximum value.

請參照第六圖,其係為本創作資訊服務可用性管理系統之架構圖,資訊服務可用性管理系統1包括:複數個監控主機H1,H2,H3,H4,用以蒐集複數個組態之複數個監控測量資料;一第一資料庫DB1,係連接該些監控主機H1,H2,H3,H4,該第一資料庫DB1用以儲存該些監控測量資料,該些資料包含複數個可用性監控資料以及複數個容量監控資料;一分析模組10,係連接該第一資料庫DB1,該分析模組10用以分析該些可用性監控資料以及該些容量監控資料,評估判斷是否有異常訊息或事件發生,若是的話,進行事件與問題管理流程;以及一報表產生模組20,係連接該分析模組10,若該分析模組10評估判斷沒有異常訊息或事件發生,則該報表產生模組20產出一可用性監控表與一容量監控表。 Please refer to the sixth figure, which is the architecture diagram of the creation information service availability management system. The information service availability management system 1 includes: a plurality of monitoring hosts H1, H2, H3, and H4 for collecting a plurality of configurations. Monitoring the measurement data; a first database DB1 is connected to the monitoring hosts H1, H2, H3, H4, and the first database DB1 is used for storing the monitoring and measuring data, the data includes a plurality of availability monitoring data and A plurality of capacity monitoring data; an analysis module 10 is connected to the first database DB1, and the analysis module 10 is configured to analyze the availability monitoring data and the capacity monitoring data to evaluate whether an abnormal message or an event occurs. If yes, the event and problem management process is performed; and a report generation module 20 is connected to the analysis module 10. If the analysis module 10 evaluates that there is no abnormal message or an event occurs, the report generation module 20 produces An availability monitoring table and a capacity monitoring table are provided.

在一較佳實施例中,資訊服務可用性管理系統1進一步包含一整合模組30以及一第二資料庫DB2,該整合模組30用以將該些監控測量資料整合為一每日之監控測量資料以及一每月之監控測量資料,並儲存於該第二資料庫DB2,該第二資料庫DB2係連接該分析模組10,該分析模組10可進一步分析該每日之監控測量資料以及該每月之監控測量資料。 In a preferred embodiment, the information service availability management system 1 further includes an integration module 30 and a second database DB2 for integrating the monitoring and measurement data into a daily monitoring measurement. The data and a monthly monitoring measurement data are stored in the second database DB2, and the second database DB2 is connected to the analysis module 10, and the analysis module 10 can further analyze the daily monitoring measurement data and This monthly monitoring measurement data.

在一較佳實施例中,資訊服務可用性管理系統1進一步包含一匯入模組40,用以讓使用者匯入可用性資料和容量資料於該第二資料庫DB2。 In a preferred embodiment, the information service availability management system 1 further includes a import module 40 for allowing the user to import the availability data and the capacity data into the second database DB2.

在一較佳實施例中,資訊服務可用性管理系統1進一步包含一第三資料庫DB3,係連接該報表產生模組20,該第三資料庫DB3用以儲存複數個補救(Remedy)事件,該報表產生模組20用以依據該些補救事件更新 該可用性監控表與該容量監控表。 In a preferred embodiment, the information service availability management system 1 further includes a third database DB3 connected to the report generation module 20 for storing a plurality of Remedy events. The report generation module 20 is configured to update according to the remedial events The availability monitoring table and the capacity monitoring table.

較佳地,補救(Remedy)事件係為不屬於標準資訊服務運作之一部分,並且導致服務中斷或服務品質降低之異常狀況,影響使用者正常操作的事件。 Preferably, the Remedy event is an abnormal condition that is not part of the operation of the standard information service and causes a service interruption or a decrease in service quality, and affects the normal operation of the user.

本領域熟習技藝者應可理解本創作之分析模組10、報表產生模組20、整合模組30、匯入模組40、第一資料庫DB1、第二資料庫DB2、第三資料庫DB3、以及監控主機H1,H2,H3,H4等元件可具有足夠的硬體電路、元件及/或配合的軟體、韌體及其組合來實現各項所需的功能。 Those skilled in the art should be able to understand the analysis module 10, the report generation module 20, the integration module 30, the import module 40, the first database DB1, the second database DB2, and the third database DB3 of the present creation. And the monitoring host H1, H2, H3, H4 and other components can have enough hardware circuits, components and/or mated software, firmware and combinations thereof to achieve the desired functions.

在本創作資訊服務可用性管理系統1,監控主機H1,H2,H3,H4用以監控各項業務服務時之頻寬數值以及設備效能數值,進一步而言,係針對各項不同服務時的頻寬使用率、處理器使用率、記憶體使用率、硬碟空間使用率。 In the creation information service availability management system 1, the monitoring host H1, H2, H3, H4 is used to monitor the bandwidth value and device performance value of each service service, and further, the bandwidth for different services. Usage, processor usage, memory usage, hard disk space usage.

本創作依據設備型號判讀設備效能,以及不同的系統交易量計算不同的網路使用量,設計對應機制及程式模式改善設備監控之可用性,藉由依據服務可用性之相關元件類別,至各監控系統使用監控軟體定期收集效能數值資訊,透過本創作自動產出服務可用性相關所需數據,與業務負責人匯入之可用性資料結合,將每日監控資料彙整計算,以月為單位產出服務可用性報表,提供一種具有高準確度、且能自動、有效地管理資訊服務可用性的系統。 This creation is based on the device model to determine the device performance, and different system transaction volume to calculate different network usage, design the corresponding mechanism and program mode to improve the availability of device monitoring, by using the relevant component categories of service availability, to the monitoring system The monitoring software collects the performance value information on a regular basis, and automatically generates the required data related to the service availability through the creation, and combines the daily monitoring data with the availability data imported by the business owner, and outputs the service availability report on a monthly basis. Provide a system with high accuracy and automatic and efficient management of information service availability.

本創作之實施例確能達到所預期之使用功效,又其所揭露之技術內容,不僅未曾見諸於同類產品中,亦未曾公開於申請前,誠已完全符合專利法之規定與要求,爰依法提出新型專利之申請,懇請惠予審查, 並賜准專利,則實感德便。 The embodiment of the present invention can achieve the expected use effect, and the technical content disclosed by the present invention has not been seen in the same product, nor has it been disclosed before the application, and has fully complied with the requirements and requirements of the patent law. To file an application for a new type of patent in accordance with the law, please apply for review, And granting a patent, it is really sensible.

Claims (8)

一種資訊服務可用性管理系統,該系統包括:複數個監控主機,用以蒐集複數個組態之複數個監控測量資料;一第一資料庫,係連接該些監控主機,用以儲存該些監控測量資料,該些資料包含複數個可用性監控資料以及複數個容量監控資料;一分析模組,係連接該第一資料庫,用以分析該些可用性監控資料以及該些容量監控資料,評估判斷是否有異常訊息或事件發生,若是的話,進行事件與問題管理流程;以及一報表產生模組,係連接該分析模組,若該分析模組評估判斷沒有異常訊息或事件發生,則該報表產生模組產出一可用性監控表與一容量監控表。 An information service availability management system, the system comprising: a plurality of monitoring hosts for collecting a plurality of configured monitoring and measuring data; a first database connected to the monitoring hosts for storing the monitoring and measuring The information includes a plurality of availability monitoring data and a plurality of capacity monitoring data; an analysis module is connected to the first database for analyzing the availability monitoring data and the capacity monitoring data to evaluate whether there is any An abnormal message or event occurs, if yes, an event and problem management process; and a report generation module is connected to the analysis module, and if the analysis module evaluates that there is no abnormal message or an event occurs, the report generation module Output an availability monitoring table and a capacity monitoring table. 根據申請專利範圍第1項之系統,進一步包含一整合模組以及一第二資料庫,該整合模組用以將該些監控測量資料整合為一每日之監控測量資料以及一每月之監控測量資料,並儲存於該第二資料庫。 The system of claim 1 further includes an integration module and a second database for integrating the monitoring measurement data into a daily monitoring measurement data and a monthly monitoring The data is measured and stored in the second database. 根據申請專利範圍第2項之系統,進一步包含一匯入模組,用以讓使用者匯入可用性資料和容量資料於該第二資料庫。 According to the system of claim 2, a system further includes a import module for allowing the user to import the availability data and the capacity data into the second database. 根據申請專利範圍第1項之系統,進一步包含一第三資料庫,係連接該報表產生模組,用以儲存複數個補救事件, 該報表產生模組用以依據該些補救事件更新該可用性監控表與該容量監控表。 According to the system of claim 1, the third database further comprises a report generating module for storing a plurality of remedial events, The report generation module is configured to update the availability monitoring table and the capacity monitoring table according to the remediation events. 根據申請專利範圍第1項之系統,其中,該些組態包含:一服務、一應用、一叢集、一軟體伺服器、一電腦系統以及一網路裝置。 The system of claim 1, wherein the configurations comprise: a service, an application, a cluster, a software server, a computer system, and a network device. 根據申請專利範圍第1項之系統,其中,該些監控測量資料包含:一頻寬使用率、一處理器使用率、一記憶體使用率以及一硬碟空間使用率。 According to the system of claim 1, wherein the monitoring measurement data includes: a bandwidth usage rate, a processor usage rate, a memory usage rate, and a hard disk space usage rate. 根據申請專利範圍第1項之系統,進一步包含依據該可用性監控表產出一可用性監控報告,依據該容量監控表產出一容量監控報告。 According to the system of claim 1, the availability monitoring report is outputted according to the availability monitoring table, and a capacity monitoring report is generated according to the capacity monitoring table. 根據申請專利範圍第7項之系統,進一步包含依據該可用性監控報告和該容量監控報告產出一趨勢分析報告。 According to the system of claim 7 of the patent application, further comprising a trend analysis report based on the availability monitoring report and the capacity monitoring report output.
TW108204436U 2019-04-11 2019-04-11 Information Service Availability Management System TWM580710U (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW108204436U TWM580710U (en) 2019-04-11 2019-04-11 Information Service Availability Management System

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW108204436U TWM580710U (en) 2019-04-11 2019-04-11 Information Service Availability Management System

Publications (1)

Publication Number Publication Date
TWM580710U true TWM580710U (en) 2019-07-11

Family

ID=68050080

Family Applications (1)

Application Number Title Priority Date Filing Date
TW108204436U TWM580710U (en) 2019-04-11 2019-04-11 Information Service Availability Management System

Country Status (1)

Country Link
TW (1) TWM580710U (en)

Similar Documents

Publication Publication Date Title
JP6828096B2 (en) Server hardware failure analysis and recovery
US9152485B2 (en) Evaluating service degradation risk for a service provided by data processing resources
Birke et al. Failure analysis of virtual and physical machines: patterns, causes and characteristics
US8051162B2 (en) Data assurance in server consolidation
US8352867B2 (en) Predictive monitoring dashboard
US7783605B2 (en) Calculating cluster availability
US7500150B2 (en) Determining the level of availability of a computing resource
CA2788356C (en) Data quality analysis and management system
US20060277080A1 (en) Method and system for automatically testing information technology control
US7426736B2 (en) Business systems management solution for end-to-end event management using business system operational constraints
US8880560B2 (en) Agile re-engineering of information systems
US20130086429A1 (en) System and method for self-diagnosis and error reporting
US11093349B2 (en) System and method for reactive log spooling
US8725741B2 (en) Assessing application performance with an operational index
US10402298B2 (en) System and method for comprehensive performance and availability tracking using passive monitoring and intelligent synthetic transaction generation in a transaction processing system
KR101989330B1 (en) Auditing of data processing applications
CN113656174A (en) Resource allocation method, system, computer device and storage medium
US7617313B1 (en) Metric transport and database load
CN110647447A (en) Abnormal instance detection method, apparatus, device and medium for distributed system
US10708344B1 (en) Continuous performance management in information processing systems
TWM580710U (en) Information Service Availability Management System
TWI712880B (en) Information service availability management method and system
CN115543665A (en) Memory reliability evaluation method and device and storage medium
US20040117470A1 (en) Temporal service level metrics system and method
CN117130851B (en) High-performance computing cluster operation efficiency evaluation method and system