KR20190047284A - Metering and monitoring data integration management apparatus and method for cloud service - Google Patents

Abstract

Photoresist an integrated metering and monitoring data management apparatus for a cloud service, to allow each portal device to manage and inquire of data with the same value even if a screen template is different, and a method thereof. According to the present invention, the integrated metering and monitoring data management apparatus comprises: a data collection engine collecting raw data generated in a cloud service environment; a communication interface communicating with a plurality of cloud service portal devices managing at least one from providing, use, and intermediation of a cloud service; a memory storing an integrated metering and monitoring management program integrally managing raw data (hereinafter, referred to as metering raw data) for a metering index collected from a data collection engine and raw data (hereinafter, referred to as monitoring raw data) for a monitoring index; and a processor executing a stored integrated metering and monitoring management program to collect the metering and monitoring raw data from the data collection engine to integrally manage and store metering and monitoring tables, and using data stored in a metering status table and the monitoring table to provide a plurality of cloud service portal devices to a metering inquiry service, a monitoring inquiry service, and a report service.

Description

[0001] Metering and monitoring data integration management apparatus and method for cloud service [

The present invention relates to an apparatus and method for integrated management of metering and monitoring data for a cloud service, and more particularly, to a system and method for collecting and collecting data required by a CSP management system, a CSB management system, and a CSC management system in a cloud service environment And to a management apparatus and method for integrated management of metering and monitoring data for a cloud service that can be provided to each management system.

As the IT environment shifts to the cloud center, demand for existing IT services is gradually declining. On the other hand, demand for CSB management system (ie, CSB (Cloud Service Brokerage) portal, CSP (Cloud Service Provider) portal, CSC (Cloud Service Consumer) portal) that supports various cloud services as the use of cloud service spreads Is on the rise.

CSP is a cloud service provider that registers and sells cloud services, CSC is a cloud service user who requests and uses cloud services, and CSB is a service that integrates and intervenes in cloud services by matching solutions and requirements between multiple CSPs and CSCs. It is a business that provides services.

Accordingly, a method for solving various problems such as various regulatory compliance management and security risk management that are caused by introducing various cloud services including CSB, CSC, and CSP has been proposed.

In the past, the systems that constitute the CSB, namely, the cloud service provider management system (or CSP portal), the cloud service manager management system (or CSB portal), and the cloud service user management system The data is retrieved using the Repository DB.

Accordingly, in order to inquire the corresponding data in the other system, it is necessary to follow the complicated procedure of defining an interface capable of interlocking with the existing system. Thus, different data are inquired or displayed for each data integration inquiry and interworking system And the like.

Korean Patent Publication No. 10-2017-0000567 (Feb.

SUMMARY OF THE INVENTION In order to solve the above-described problems, the technical problem to be solved by the present invention is that each portal device of the CSB management system does not separately manage (collect, process) the monitoring and metering data, And an apparatus and method for integrated management of metering and monitoring data for a cloud service capable of solving the problem of erroneous data being displayed or displayed.

The solution of the present invention is not limited to those mentioned above, and other solutions not mentioned can be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, there is provided an apparatus for managing integrated metering and monitoring data for a cloud service, the apparatus comprising: a data collection engine for collecting raw data generated in a cloud service environment; And a communication interface for communicating with a plurality of cloud service portal devices that are responsible for at least one of providing, using and mediating cloud services; (Hereinafter, referred to as 'metering low data') and metrology and monitoring integration (hereinafter referred to as 'monitoring low data') integrated management of metering metrics collected from the data acquisition engine A memory in which the management program is stored; Collecting the metering row data from the data collection engine and integrating management and storing the metering row data in the metering table, collecting the monitoring row data from the data collection engine, And a processor for providing a metering inquiry service, a monitoring inquiry service, and a report service to the plurality of cloud service portal devices using the metering status table and the data stored in the monitoring table.

Wherein the metering table includes a metering status table and a metering history table, and the processor compares the metering row data with the metering status table, and if the metering row data is new data or changed data, Storing the collected metering row data in a table and the metering history table, and storing the metering row data in the metering status table if the collected metering row data is the same as the previously stored metering row data.

The processor integrates the collected monitoring raw data and processes it in units of minutes, hours, days, and months, and stores the data in the monitoring table.

Wherein the monitoring table includes a real-time data storage table, a time data storage table, a data data storage table, and a monthly data storage table, and the processor collects the monitoring row data in units of minutes and stores the monitoring row data in the real- , Monitoring low data collected for 60 minutes is collected to generate 1-hour monitoring data, and then the monitoring 1-hour data is stored in the time data storage table, and monitoring 1-hour data stored for 24 hours is collected to generate daily 1-day monitoring data Stored in the day data storage table, and the monitoring day data collected for 30 days may be collected and stored in the monthly data storage table.

The processor integrates and manages the metering table and the monitoring table as a common table provided for the plurality of cloud service portal devices, and stores the metering table and the monitoring table in a database.

Wherein the plurality of cloud service portal devices access the database and request at least one of the metering inquiry service, the monitoring inquiry service, and the report service, and the database stores data corresponding to the requested at least one service And provides it to the plurality of cloud service portal devices in a displayable form.

According to another embodiment of the present invention, there is provided a method of managing metering and monitoring data of a metering and monitoring data integrated management device for a large cloud service, the method comprising: (A) (Hereinafter referred to as " metering row data ") from a data collection engine that collects raw data; (B) the integrated management apparatus integrating and managing the collected metering row data in a metering table of the database; (C) the integrated management apparatus collecting row data (hereinafter referred to as 'monitoring row data') for the monitoring index from the data collection engine; (D) the integrated management device collectively managing and storing the collected monitoring raw data in a monitoring table of the database; And (E) the integrated management apparatus further includes a metering status table and a plurality of cloud service portal apparatuses that are responsible for at least one of providing, using, and brokering cloud services, Providing a query service, a monitoring query service, and a report service.

Wherein the step (B) comprises the steps of: (B1) comparing the metering row data collected in the step (A) with the metering status table, and if the collected metering row data is new data or changed data, Storing the collected metering row data in a table; And (B2) storing the collected metering row data in the metric state table if the collected metering row data is the same as previously stored data.

In step (D), the monitoring raw data collected in step (C) are integrated and processed in units of minutes, hours, days, and months, and then the time data storage table, And stores it in the storage table.

Wherein the step (E) comprises the steps of: when the plurality of cloud service portal devices access the database and request at least one of the metering inquiry service, the monitoring inquiry service, and the report service, And processes the data corresponding to the service in a displayable form and provides the data to the plurality of cloud service portal devices.

According to the present invention, each portal device of the CSB management system can manage and collect metering data separately by various metering tables and monitoring tables, and by integrally managing the monitoring and metering data in the data integration management device without separately managing (collecting and processing) Portal devices can manage and query data of the same value even if the screen template is different.

The effects of the present invention are not limited to those mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the following description.

FIG. 1 is a diagram illustrating a metering and monitoring data integrated management system for a cloud service according to an embodiment of the present invention; FIG.
2 is a block diagram illustrating an integrated management apparatus for metering and monitoring data according to an embodiment of the present invention.
Figure 3 illustrates an application management layer of an integrated metering and monitoring management program;
FIG. 4 and FIG. 5 are conceptual diagrams showing an operation of collecting, managing, and storing metering row data and monitoring row data,
FIG. 6 is a flowchart illustrating a method for managing integrated data of metering and monitoring data of an integrated management apparatus according to an exemplary embodiment of the present invention. FIG.
FIG. 7 is a flowchart showing the step S620 of FIG. 6 in more detail,
8 is a flowchart showing the step S660 of FIG. 6 in more detail.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features, and advantages of the present invention will become more readily apparent from the following description of preferred embodiments with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described herein but may be embodied in other forms. Rather, the embodiments disclosed herein are provided so that the disclosure can be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

Also, when it is mentioned that the first element (or component) is operated or executed on the second element (or component) ON, the first element (or component) It should be understood that it is operated or executed in an operating or running environment or is operated or executed through direct or indirect interaction with a second element (or component).

It is to be understood that when an element, component, apparatus, or system is referred to as comprising a program or a component made up of software, it is not explicitly stated that the element, component, (E.g., memory, CPU, etc.) or other programs or software (e.g., drivers necessary to drive an operating system or hardware, etc.)

It is also to be understood that the elements (or elements) may be implemented in software, hardware, or any form of software and hardware, unless the context requires otherwise.

Hereinafter, the present invention will be described in detail with reference to the drawings. In describing the specific embodiments below, various specific details have been set forth in order to explain the invention in greater detail and to assist in understanding it. However, it will be appreciated by those skilled in the art that the present invention may be understood by those skilled in the art without departing from such specific details.

In some instances, it should be noted that portions of the invention that are not commonly known in the description of the invention and are not significantly related to the invention do not describe confusing reasons for explaining the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

Each of the configurations of the metering and monitoring data integrated management device 200 for the cloud service shown in FIG. 1 indicates that the configuration can be functionally and logically separated, and each configuration may be divided into separate physical devices, It is to be appreciated that the average expert in the field of the present invention can easily deduce that it is not meant to be written in code.

In this specification, a module may mean a functional and structural combination of hardware for carrying out the technical idea of the present invention and software for driving the hardware. For example, the module may mean a logical unit of a predetermined code and a hardware resource for executing the predetermined code, and it does not necessarily mean a physically connected code or a kind of hardware. Can be easily deduced to the average expert in the field of < / RTI >

Also, in this specification, a DB may mean functional and structural combination of software and hardware for storing information corresponding to each DB. The DB may be implemented as at least one table, and may further include a separate DBMS (Database Management System) for searching, storing, and managing information stored in the DB. In addition, it can be implemented in various ways such as a linked-list, a tree, and a relational DB, and includes all data storage media and data structures capable of storing information corresponding to the DB.

The program for implementing the integrated metering and monitoring data management apparatus 200 for the cloud service may be installed in a predetermined data processing apparatus to implement the technical idea of the present invention.

FIG. 1 is a diagram illustrating an integrated management system for metering and monitoring data for a cloud service according to an embodiment of the present invention. Referring to FIG.

1, the integrated metering and monitoring data management system for a cloud service according to an exemplary embodiment of the present invention includes a plurality of cloud service portal devices 10, 20 and 30, a data collection engine 100, A data integration management device 200 and a database 300. [

A plurality of cloud service portal apparatuses 10, 20 and 30 which are responsible for at least one of providing, using and brokering a cloud service are installed in systems constituting a CSB (Cloud Service Brokerage) management system, that is, a CSP portal apparatus 10 ), A CSC portal device 20 and a CSB portal device 30. The CSP portal device 10 is a cloud service provider management system, the CSC portal device 20 is a cloud service user management system, and the CSB portal device 30 is a cloud service manager management system.

The data collection engine 100 collects all the raw data that occurs in the cloud service environment. Since cloud services typically provide virtual machines by assigning them to users, the raw data can contain data related to the virtual machine.

The metering and monitoring data integrated management device 200 manages (collects or queries) different data for the same data in a different manner with respect to the CSP portal device 10, the CSC portal device 20, and the CSB portal device 30, The same raw data can be collected and managed and distributed to each CSP portal apparatus 10, the CSC portal apparatus 20, and the CSB portal apparatus 30 in order to solve the problem of solving the problem.

Therefore, the CSP portal device 10, the CSC portal device 20, and the CSB portal device 30 can perform metering inquiry, monitoring inquiry, and monitoring inquiry by the integrated managed metering data and the monitoring data without separately managing the metering data and the monitoring data. , Metering and monitoring report requests.

Meanwhile, the database 300 is a DBMS (Database Management System), which can store a metering code information table, a metering code information, a monitoring data table information table, a monitoring code information table, and monitoring code information linked with the integrated metering and monitoring management program have.

Table 1 shows the metering code information table.

[Table 1] Referring to Table 1, the metering code information table (MTR_CODE_INFO) shows information on the metering status table, the metering history table, the metering status view table, and the codes used in the metric history view table. The indicator code (or indicator name) in [Table 1] is a metering indicator used when the data collection engine 100 collects metering row data.

Table 2 shows the metering code information.

[Table 2] Referring to Table 2, the metering code information shows the item names for each item code listed in [Table 1], the kind of the indicator code for each item name, and the kind of indicator name. For example, the indicator codes belonging to the item code called virtual machine (VM) include SVCTIME and CNT, which indicate the virtual machine service time and the number of virtual machines, respectively.

Thus, metering row data may include data for SVCTIME, CNT, ALLOC, OUTTRAFFIC.

 [Table 1] and [Table 2] collect metering row data and collectively manage the collected metering row data to generate a metering status table, a metering history (history) table, a metering status view table (and a metering history view table) Stored or updated.

[Table 3] shows the monitoring data table information table.

Referring to Table 3, the monitoring data table information table (MNT_TABLE_INFO) shows information related to one monitoring table generated from the monitoring row data. For example, if the monitoring table is a real-time data storage table, the name of this table (table_name) is of the form 'MNT_R_YYYYMMDDHH', where actual numbers may be written in place of Y, M, D and H, The creation date of the table is known from create_date.

Table 4 shows the monitoring code information table.

Referring to Table 4, the monitoring code information table MNT_CODE_INFO includes a monitoring table, that is, a real time data storage table MNT_R_YYYYMMDDHH, a time data storage table MNT_H_YYYYMMDD, a one data storage table MNT_D_YYYYMM, MNT_M_YYYY) of the code used in this example. The indicator code (or indicator name) is a monitoring indicator code used when collecting monitoring row data from the data collection engine 100, and is listed in Table 5 in detail.

Table 5 shows the monitoring code information.

[Table 5], the monitoring code information shows the item names for each item code listed in [Table 4], the kind of indicator code for each item name, and the kind of indicator name.

For example, the item name of the item code of the CPU is the CPU, and the index codes belonging to this item code include USER, SYSTEM, NICE and IDLE, and the index name of the USER index code is the use rate of the User. CPU average usage rate.

[Table 1] to [Table 5] collect the monitoring row data and collectively manage the collected monitoring row data by the processor 240, which will be described later, to generate a real-time data storage table, a time data storage table, A storage table, a real-time data view table, a time data view table, a work data view table, and a month data view table.

In addition, the database 300 stores metering tables, metering view tables, monitoring tables, and monitoring view tables as shown in [Table 7] to [Table 18] generated by the metering and monitoring data integrated management apparatus 200. The metering view table and the monitoring view table can be used when portal devices () request metering inquiries, monitoring inquiries, reporting, and so on.

The metering table includes a metering status table and a metering history table, and the metering view table includes a metering status view table and a metering history view table.

The monitoring table includes a real-time data view table, a time data view table, a work data view table, and a month data view table. The monitoring view table includes a real-time data storage table, a time data storage table, .

FIG. 2 is a block diagram illustrating an integrated metering and monitoring data management apparatus 200 according to an embodiment of the present invention.

2, the integrated metering and monitoring data management apparatus 200 may include a bus 210, a communication interface 220, a memory 230, and a processor 240, and may be an electronic device such as a Personal Computer For example.

The bus 210 may include circuitry for interconnecting the communication interface 220, the memory 230 and the processor 240 and for conveying various signals such as control messages, status information, and / or data.

The communication interface unit 220 is a device for wired / wireless communication with the data collection engine 100 and the database 300. The communication interface unit 220 may also communicate with the CSP portal apparatus 10, the CSC portal apparatus 20 and the CSB portal apparatus 30. [

The communication interface 220 can collect metering row data for metering metrics and monitoring log data for the metrics via the RESTful API from the data collection engine 100. Here, 'REST' is an abbreviation of 'Representational state transfer'.

The communication interface unit 220 transmits a metering table, a metering view table, a monitoring table, or a monitoring view table to the database 300 through, for example, JDBC (Java DataBase Connectivity) You can also load the table. To this end, the communication interface 220 may include a communication circuit for RESTful API or JDBC.

Memory 230 may include volatile memory and / or non-volatile memory. The memory 230 may store instructions or data related to the components, one or more programs and / or software, an operating system, etc., to implement and / or provide the operations, functions, and the like provided by the integrated metering and monitoring data management apparatus 200 Can be stored.

The program stored in the memory 230 is used to store the metering row data collected from the data collection engine 100 and the metering data collected from the data collection engine 100 in order to provide the collected and managed data to the plurality of cloud service portal devices 10, And an integrated metering and monitoring management program that unified management of monitoring low data.

The metering and monitoring integrated management program invokes tables such as [Table 1] to [Table 5] stored in the database 300, confirms the designated metering index, collects the metering row data for the confirmed metering metrics, Collects monitoring low data for the monitored monitoring indices, integrates and manages the collected metering row data and monitoring low data, and generates corresponding tables of [Table 7] to [Table 18] to be described later Or stored in the corresponding table.

In addition, the integrated metering and monitoring management program can be used to manage a plurality of cloud service portal apparatuses (not shown) using data stored in metering tables and monitoring tables such as [Table 7] to [Table 18] 10, 20, 30) to provide at least one of a metering inquiry service, a monitoring inquiry service, a statistical service, and a report service.

To this end, the application management layer of the integrated metering and monitoring management program may include a metering service module, a monitoring service module, a statistical service module and a report service module, as shown in FIG.

[Table 6] is a table for describing the metering service module, the monitoring service module, the statistical service module, and the report service module

In Table 6, the monitoring data and the metering data include the monitoring row data and the metering row data, and each work space refers to each of the cloud service portal apparatuses 10, 20, and 30 and the integrated management apparatus 200, The DB server means the database 300.

Meanwhile, the processor 240 executes one or more programs stored in the metering and monitoring data integrated management apparatus 200 to control the overall operation of the metering and monitoring data integrated management apparatus 200.

In an embodiment of the present invention, the processor 240 executes a metering and monitoring integrated management program stored in the memory 230 to collect metering row data from the data acquisition engine 100 to create a metering status table and a metering history table Integrated management and storage, and collects monitoring raw data from the data collection engine 100 to create, manage, and store monitoring tables.

In addition, the processor 240 provides the metering inquiry service, the monitoring inquiry service, the statistical service, and the report to the plurality of cloud service portal devices 10, 20, and 30 using the data stored in the metering table and the monitoring table, Services to be provided.

In the following, the processor 240 executes the integrated metering and monitoring management program to manage the integrated management and storage of the metering table, the metering view table, the monitoring table, and the monitoring view table.

First, an operation of collecting metering row data and performing integrated management and storing will be described with reference to FIG.

Processor 240 identifies metering indicators (i. E., Indicator codes or indicator names) specified in the metering code information of Table 2 and provides metering row data for the metering metrics to the data acquisition engine 100). ≪ / RTI >

Processor 240 may compare the historical data for the same metric code stored in the pre-stored metering status table with the metering row data collected.

As a result of the comparison, if the currently collected metering row data is new data or changed data, the processor 240 newly stores information on the metering row data currently collected in the metering status table as shown in [Table 7] The metering history table can be updated by additionally storing the metering row data collected in the metering history table of FIG. Therefore, only the changed information is stored in the metric history table so that the change history corresponding to the indicator code can be managed.

On the other hand, if the currently collected metering row data is the same as the previous data, the processor 240 may store the metering row data collected in the metering status table. Processor 240 may keep the old data pre-stored in the metering status table and update update_date to the time the current metering row data is stored.

[Table 7] shows the metering status table among the metering tables.

[Table 7] Referring to Table 7, the metering status table (MTR_STATUS) includes the ID of the user using the virtual machine, the item code, the indicator code for each item, the value of the character type, the value of the numeric value, And may include a storage date and time and an update date and time. For example, if the item code of the collected metering row data is a virtual machine (VM) and the indicator code of the virtual machine includes SVCTIME and CNT, the processor 240 may compare the metering row data for the SVCTIME of the VM with the CNT Can be stored in the metering status table in the form of [Table 6].

Table 8 shows the Metering History Table (MTR_HISTORY).

[Table 7] Referring to Table 7, the metering history table includes the ID of the virtual server generated by the CSC unit service application, the item code, the indicator code for each item, the value of the character type, the value of the numeric value, And may include an update date and time (save_date) of the data.

For example, if the indicator code of the collected metering row data is 'ALLOC (disk quota)' of the DISK and compared to the ALLOC of the DISK stored in the metering status table, the processor 240, (Vm_id, object_code, attribute_code, str_value, num_value, save_date) of the currently collected DISK in the metering status table and the metering history table.

As a result of comparison with the ALLOC of the DISK stored in the metering status table, if the disk quota is equal to the previous value, the processor 240 can store the update date and time (update_date) of the metering status table as the current storage date and time.

Next, an operation of collecting monitoring integrated data and managing and storing it will be described with reference to FIG.

Processor 240 identifies the monitoring indications (i.e., indicator code or indicator name) specified in the monitoring code information in Table 5, and collects monitoring raw data for the identified monitoring indications from data collection engine 100 .

The processor 240 may integrate the collected monitoring raw data and process it in units of minutes, hours, days, and months, and then store the data in the monitoring table.

In more detail, the processor 240 collects the monitoring row data on a minute-by-minute basis and stores it in a real-time data storage table as shown in [Table 9].

[Table 9] shows the real-time data storage table (MNT_R_YYYYMMDDHH) stored in minutes in the monitoring table.

Referring to Table 9, the name of the real-time data storage table in which the monitoring raw data collected in minutes is stored is 'MNT_R_YYYYMMDDHH', and the ID of the virtual machine in which the row data occurred, the item code, (Save_date) < / RTI > and monitoring values stored in the real-time data storage table for the first time.

In addition, the processor 240 collects the monitoring row data collected for 60 minutes, generates monitoring 1 hour data, and stores it in the time data storage table as shown in [Table 10].

[Table 10] shows the time data storage table (MNT_H_YYYYMMDD) stored in minutes of the monitoring table.

Referring to Table 10, min_value in the time data storage table means the minimum value among the monitoring row data collected for the same index for 60 minutes (for example, CACHED of the MEMORY item), and the maximum value is the opposite , If the CACHED of the MEMORY item is collected continuously for 60 minutes, the number of the collected items may be '60'.

In addition, the processor 240 collects monitoring 1-hour data stored for 24 hours, generates daily 1-day monitoring data, and stores it in a data storage table as shown in [Table 11].

[Table 11] shows one data storage table (MNT_D_YYYYMM) which is stored in minutes among the monitoring tables.

Referring to Table 11, one data storage table collects data collected for 24 hours in the form of [Table 10], and stores the data in units of one day.

In addition, the processor 240 collects the monitoring 1-day data collected for 30 days and stores it in the monthly data storage table as shown in [Table 12].

[Table 12] shows the monthly data storage table (MNT_M_YYYY) stored in the monitoring table on a monthly basis.

[Table 12] Referring to Table 12, the monthly data storage table collects data collected for one month in the form of [Table 11], and stores the data in units of one month.

Each of the tables shown in [Table 9] to [Table 12] in which the monitoring row data is stored in real time or processed is a table generated for each cycle in minutes, hours, days, months or years, The monitoring row data can be processed and stored in the corresponding table at a predetermined time (for example, 5 minutes every hour, 15 minutes every day, 25 minutes per day every month) as shown in Fig.

The processor 240 provides the same metering tables and monitoring tables (or data in the tables) to the plurality of cloud service portal apparatuses 10, 20 and 30 as shown in [Table 7] to [Table 12] (Or common data) to be stored in the database 300. In addition,

Meanwhile, the plurality of cloud service portal devices 10, 20, and 30 access the database 300 to request at least one of a metering inquiry service, a monitoring service, and a report service, 20, and 30 in a form that can display the data corresponding to at least one service received from the plurality of cloud service portal devices 10, 20, and 30.

That is, each of the cloud service portal devices 10, 20, and 30 may receive data according to a predetermined interface method and utilize a dashboard, a monitoring inquiry, a metering inquiry, or a report output function according to a main function and a screen configuration . The predetermined interface method can be exemplified by RESTful API or DB View interface.

To this end, the processor 240 may generate the metering view table and the monitoring view table as shown in [Table 13] to [Table 18] and provide the metering view table and the monitoring view table to the database 300. The metering view table and the monitoring view table are views used for metering inquiry, monitoring inquiry, metering report site, or monitoring report generation. The database 300 includes a metering view table or a monitoring view table, and each of the cloud service portal devices 10, 20, and 30 through the interface to the cloud service portal devices 10, 20, and 30, respectively.

[Table 13] shows the metering status view table (V_MTR_STATUS).

In Table 13, the query indicates a query requested by the CSP portal apparatus 10, for example. When the user inputs the item code, the index code, and the search start date-end year-and-month as a query in the CSP portal apparatus 10, the database 300 transmits the corresponding data to the CSP portal apparatus 10 .

Table 14 shows the metering history view table (V_MTR_HISTORY).

Table 15 shows the real-time data view table (V_MNT_R).

Table 16 shows the time data view table (V_MNT_H).

Table 17 shows one data view table (V_MNT_D).

Table 18 shows the monthly data view table (V_MNT_M).

The various portal devices 10, 20, and 30 can manage the monitoring and metering data (collecting, processing, and processing) of the portal devices 10, 20, 200, the portal devices 10, 20, and 30 can manage and query data of the same value even if the screen templates are different.

Hereinafter, an integrated management method of metering and monitoring data of the integrated management device 200 according to an embodiment of the present invention will be described with reference to FIGS. 6 to 8

FIG. 6 is a flowchart illustrating a method of managing integrated data of metering and monitoring data of the integrated management apparatus 200 according to an embodiment of the present invention.

The data collection engine 100, the metering and monitoring data integrated management device 200, the database 300 and the CSP / CSB / CSC 10, 20, 30 shown in FIG. The data collection engine 100, the metering and monitoring data integrated management apparatus 200, the database 300, and the plurality of cloud service portal apparatuses 10, 20, and 30,

Referring to FIG. 6, the data collection engine 100 collects and stores row data generated when a user uses the cloud service (S600).

The metering and monitoring data integrated management apparatus 200 collects data (metering row data) about the metering metrics from the data acquisition engine 100 (S610), processes the collected metering row data (S620) ) (S630, S640). Step S620 will be described later with reference to Fig.

In addition, the metering and monitoring data integrated management apparatus 200 collects row data (monitoring row data) for the monitoring indexes from the data collection engine 100 (S650), processes the collected monitoring row data (S660) Integrated management and storage in the monitoring table of the database 300 (S670, S680).

In addition, the metering and monitoring data integrated management apparatus 200 generates view tables for metering and monitoring reports (S690) and provides them to the database 300 (S700).

When a metering inquiry, a monitoring inquiry or a report data request is received from one of the CSP / CSB / CSC 10, 20 and 30 (S710), that is, when a query is inputted, And the data corresponding to the query are provided to one of the CSP / CSB / CSC 10, 20, and 30 (S720).

One of the CSP / CSB / CSC 10, 20, and 30 generates and displays a desired metering screen, a monitoring screen, or a report screen using the received view table and data (S730).

7 is a flowchart showing the step S620 of FIG. 6 in more detail.

Referring to FIG. 7, the metering and monitoring data integrated management apparatus 200 collects metering row data from the data collection engine 100 in units of m minutes (S622). The m-minute may be, for example, 10 minutes, and the metering data is the data on which the billing is based. Therefore, since the data change does not occur from time to time, that is, the data change period is long, the value of m minutes is 10 minutes to 60 minutes in the embodiment of the present invention.

The metering and monitoring data integrated management apparatus 200 may compare the metering row data collected and the metering status table by a metric index (S624).

If the currently collected metering row data is the same as the already stored data (S626-No), the metering and monitoring data integrated management apparatus 200 determines the currently collected time in the area related to the metering row data The update can be stored (S628).

On the other hand, if the comparison result is new data or changed data (Yes in S626), the integrated monitoring and metering data management device 200 newly stores the information on the metering row data currently collected in the metering status table, The metering history table may be updated by additionally storing the collected metering row data (S629).

8 is a flowchart showing the step S660 of FIG. 6 in more detail.

Referring to FIG. 8, the metering and monitoring data integrated management apparatus 200 collects the monitoring row data every n minutes (S662). The n minutes can be, for example, 1 minute, but is not limited thereto. Monitoring row data is performance data used for monitoring performance check and failure monitoring, and is changed from time to time. Therefore, the collection period of the monitoring row data may be shorter than the period of the metering row data.

In addition, since the monitoring low data is mainly used for monitoring performance check and fault monitoring, it is necessary to store the statistical data format in a specific unit (minute, day, hour, month) since all the target indicators are stored and used as statistical information.

To this end, the metering and monitoring data integrated management apparatus 200 stores the monitoring raw data collected in step S662 in real time to generate and / or update the real-time data storage table in units of minutes (S664).

In addition, the metering and monitoring data integrated management apparatus 200 collects monitoring raw data collected for 60 minutes to generate and store a time data storage table (S666).

In addition, the metering and monitoring data integrated management apparatus 200 collects monitoring 1-hour data stored for 24 hours, generates monitoring 1-day data, and stores the 1-day monitoring data in a data storage table (S668).

In addition, the metering and monitoring data integrated management apparatus 200 collects the monitoring 1-day data collected for 30 days and stores it in the monthly data storage table (S669).

Meanwhile, the method of managing integrated data of metering and monitoring data of the integrated management apparatus 200 according to the present invention may be provided in a recording medium that can be read by a computer by tangibly embodying a program of instructions for implementing the metering and monitoring data. And can be easily understood by a person skilled in the art.

That is, the integrated management device 200 according to the present invention may be implemented in a form of a program that can be executed through various computer means, and may be recorded on a computer-readable recording medium. Possible recording media may include program commands, data files, data structures, etc., alone or in combination.

Accordingly, the present invention can provide a program stored in a computer-readable recording medium that is executed on a computer that controls the system to implement the metering and monitoring data integrated management method using the integrated management apparatus 200. [

10, 20, 30: multiple cloud service portal devices
100: Data collection engine
200: Integrated management of metering and monitoring data
300: Database

Claims (10)

A data collection engine for collecting raw data occurring in a cloud service environment; a communication interface for communicating with a plurality of cloud service portal devices that are responsible for at least one of providing, using and mediating cloud services;
(Hereinafter, referred to as 'metering low data') and metrology and monitoring integration (hereinafter referred to as 'monitoring low data') integrated management of metering metrics collected from the data acquisition engine A memory in which the management program is stored;
Collecting the metering row data from the data collection engine and integrating management and storing the metering row data in the metering table, collecting the monitoring row data from the data collection engine, And a processor for providing a metering inquiry service, a monitoring inquiry service, and a report service to the plurality of cloud service portal devices using the metering status table and the data stored in the monitoring table, And monitoring data integrated management device. The method according to claim 1,
Wherein the metering table includes a metering status table and a metering history table,
The processor comprising:
Comparing the collected metering row data with the metering status table and storing the collected metering row data in the metering status table and the metering history table if the metering row data is new data or changed data, And if the metering row data is the same as the previously stored data, stores the metering data in the metering status table. The method according to claim 1,
The processor comprising:
Integrating the collected monitoring raw data, processing the collected monitoring raw data in units of minutes, hours, days, and months, and then storing the processed monitoring data in the monitoring table. The method of claim 3,
Wherein the monitoring table includes a real-time data storage table, a time data storage table, a one-data storage table, and a monthly data storage table,
The processor comprising:
The monitoring raw data is collected in units of minutes and stored in the real-time data storage table, the monitoring raw data collected for 60 minutes is collected to generate monitoring 1 hour data, the data is stored in the time data storage table, The monitoring 1-hour data is collected to generate monitoring 1-day data in a day unit, and the monitored 1-day data is stored in the 1-day data storage table. The monitoring 1-day data collected for 30 days is collected and stored in the monthly data storage table Integrated management of metering and monitoring data for cloud services featuring. The method according to claim 1,
The processor comprising:
Wherein the metering table and the monitoring table are integrated and managed as common tables provided equally to the plurality of cloud service portal devices and are stored in the database. 6. The method of claim 5,
Wherein the plurality of cloud service portal devices access the database and request at least one of the metering inquiry service, the monitoring inquiry service, and the report service,
Wherein the database provides the data corresponding to the requested at least one service to the plurality of cloud service portal devices in a displayable form. METHOD AND METHOD FOR INTEGRATED MANAGEMENT OF METROLOGY AND MONITORING DATA FOR MANAGING THE CLOUD SERVICES [
(A) collecting raw data (hereinafter, referred to as 'metering row data') for a metering index from a data collection engine collecting raw data generated in a cloud service environment;
(B) the integrated management apparatus integrating and managing the collected metering row data in a metering table of the database;
(C) the integrated management apparatus collecting row data (hereinafter referred to as 'monitoring row data') for the monitoring index from the data collection engine;
(D) the integrated management device collectively managing and storing the collected monitoring raw data in a monitoring table of the database; And
(E) the integrated management apparatus transmits a metering inquiry message to a plurality of cloud service portal apparatuses responsible for at least one of providing, using, and brokering a cloud service, using the metering status table and data stored in the monitoring table, Providing a service, a monitoring query service, and a report service. 8. The method of claim 7,
Wherein the metering table includes a metering status table and a metering history table,
The step (B)
(B1) comparing the metering row data collected in the step (A) with the metering status table, and if the collected metering row data is new data or changed data, the metering status table and the metering history table Storing data; And
And (B2) storing the collected metering row data in the metering status table if the collected metering row data is the same as the previously stored metering data. 8. The method of claim 7,
Wherein the monitoring table includes a real-time data storage table, a time data storage table, a one-data storage table, and a monthly data storage table,
The step (D)
The monitoring low data collected in the step (C) is integrated and processed in units of minutes, hours, days, and months, and then stored in the time data storage table, the data data storage table, and the monthly data storage table, respectively A method for managing integrated data of metering and monitoring data of an integrated management device. 8. The method of claim 7,
The step (E)
Wherein the plurality of cloud service portal devices access the database and request at least one of the metering inquiry service, the monitoring inquiry service, and the report service, the database displays data corresponding to the requested at least one service And providing the collected data to the plurality of cloud service portal devices.

Images