JP2017068296A - Monitor, monitoring method and monitoring program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a monitor capable of comprehending a billing status relevant to plural public clouds in use.SOLUTION: The monitor is connected to the respective public clouds 10 to 30 via a network 50. A monitor 100 logs in each of the portals 11 to 31 of the public clouds 10 to 30, and detects a billing tag of screen information displayed on each of the portals 11 to 31. The monitor 100 aggregates pieces of billing information written in the areas relevant to the billing tag to display the same.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a monitoring device and the like.

  In recent years, public clouds have been provided for users of various companies and organizations. A public cloud is a cloud service provided to users among services operated by cloud computing. There are various usage forms in public clouds, such as IaaS (Infrastructure as a Service), PaaS (Platform as a Service), and SaaS (Software as a Service).

  When the user starts the service, the initial investment can be suppressed by using the public cloud as compared with the case where the user himself / herself constructs a new server. The user continues to use the public cloud by paying the public cloud provider the usage amount according to the size and performance of the public cloud being used. Generally, the form of billing related to the usage amount of a public cloud differs depending on the provider of the public cloud, and the user uses a plurality of public clouds simultaneously according to the situation.

  The public cloud also has a function of preventing the influence of service degradation due to an increase in processing load by automatically adding a new server when the processing load on the server being used increases.

JP2013-20298A JP 2013-069237 A

  However, the above-described conventional technology has a problem that it is not possible to grasp the billing status regarding a plurality of public clouds being used.

  The usage amount of the public cloud is determined by the size and performance of the public cloud, and the form of charging varies depending on the provider of the cloud, so it is complicated for the user to grasp the usage amount in advance. For this reason, it is common for a user to grasp the amount of usage by referring to the usage details periodically notified from the provider of the public cloud. For this reason, the usage amount may exceed the user's budget, or unnecessary usage may occur due to continued use of a server with low usage frequency.

  In one aspect, an object of the present invention is to provide an apparatus that can grasp a billing state regarding a public cloud that is being used.

  In the first plan, the monitoring device includes a collection unit, a detection unit, and a display unit. The collection unit accesses each portal site of a plurality of public clouds using the user identification information, and collects the usage information for the user identification information from the portal site. The detection unit scans each usage information collected from each portal site of a plurality of public clouds to detect a charging tag, and detects charging information included in an area related to the charging tag for each public cloud. The display unit totals the billing information detected from each public cloud and displays the total result.

  You can understand the status of billing for multiple public clouds in use.

FIG. 1 is a diagram illustrating a configuration of a system according to the present embodiment. FIG. 2 is a functional block diagram illustrating the configuration of the monitoring apparatus according to the present embodiment. FIG. 3 is a diagram illustrating an example of the data structure of the ID management table. FIG. 4 is a diagram illustrating an example of the data structure of the usage information table. FIG. 5 is a diagram illustrating an example of the data structure of the operating status information table. FIG. 6 is a diagram illustrating an example of a login screen. FIG. 7 is a diagram (1) illustrating an example of each screen notified by the portal after login. FIG. 8 is a diagram (2) illustrating an example of each screen notified by the portal after login. FIG. 9 is a diagram (3) illustrating an example of each screen notified by the portal after login. FIG. 10 is a diagram (1) illustrating another example of each screen notified by the portal after login. FIG. 11 is a diagram (2) illustrating another example of each screen notified by the portal after login. FIG. 12 is a diagram illustrating an example of a billing information screen. FIG. 13 is a diagram illustrating an example of the image possession count totaling screen. FIG. 14 is a diagram illustrating an example of the stopped instance totaling screen. FIG. 15 is a diagram illustrating an example of a high load server count screen. FIG. 16 is a flowchart illustrating the processing procedure of the monitoring apparatus according to the present embodiment.

  Embodiments of a monitoring device, a monitoring method, and a monitoring program disclosed in the present application will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 is a diagram illustrating a configuration of a system according to the present embodiment. As shown in FIG. 1, this system includes a monitoring device 100 and public clouds 10, 20, and 30. The monitoring device 100 and the public clouds 10 to 30 are connected to each other via the network 50.

  Here, the public clouds 10 to 30 are shown as an example, but the system according to the present embodiment may have other public clouds. Moreover, the monitoring apparatus 100 may be incorporated in a part of a system used in a company or organization.

  The public clouds 10 to 30 provide cloud services to users. For example, the public clouds 10 to 30 provide users with cloud services such as IaaS (Infrastructure as a Service), PaaS (Platform as a Service), and SaaS (Software as a Service).

  The public cloud 10 includes a portal 11, an API (Application Programming Interface) 12, and a server 13. The portal 11 is a device that provides information for guiding various services to an access source terminal device in response to access to the public cloud 10. For example, when the portal 11 receives a login using a user ID (Identification Data) from a terminal device and receives a selection of a service, the portal 11 displays a screen indicating the content of the selected service on the terminal device. For example, the portal 11 causes the terminal device to display a screen corresponding to the content of the service currently provided to the user and information on the bill corresponding to the service.

  The API 12 is an interface provided by the public cloud 10 so that the function of the public cloud 10 and data to be managed can be collected by an external terminal device.

  The server 13 is a server that executes assigned processing in the public cloud 10. The public cloud 10 may have a server other than the server 13.

  Here, the public cloud 10 manages the contents of the cloud service provided to the user in association with the user ID. For example, the public cloud 10 stores information on the number of instances, the number of images, network I / O (Input / Output), and disk I / O in association with the user ID.

  The instance indicates a virtual dedicated server for providing a predetermined cloud service. For example, the virtual dedicated server includes a set of hardware, OS (Operating System), software, and data used when providing a predetermined cloud service. When a user receives provision of a plurality of cloud services, a plurality of instances are used.

  In addition, the public cloud 10 automatically increases the number of instances in the process of providing cloud services to users, and if the situation exceeds the load of the virtual dedicated server currently in use, Continue offering.

  The image indicates data used for starting a predetermined virtual dedicated server. If multiple instances are used, the number of images will increase accordingly. The network I / O is information indicating a network flow rate used according to a cloud service provided to the user. The disk I / O is information indicating the number of accesses to the disk used according to the cloud service provided to the user.

  The public cloud 10 compares the billing table set in advance by the company with the number of instances, the number of images, the network I / O, and the data I / O associated with the user ID, and the usage amount of the user ID To generate invoice information. For example, an amount corresponding to the number of instances, an amount corresponding to the number of images, an amount corresponding to the data network I / O, and an amount corresponding to the data I / O are defined in the accounting table.

  The public cloud 20 includes a portal 21, API 22, and server 23. The description regarding the public cloud 20, the portal 21, the API 22, and the server 23 is the same as that of the public cloud 10, the portal 11, the API 12, and the server 13 described above.

  The public cloud 30 includes a portal 31, API 32, and server 33. The description regarding the public cloud 30, the portal 31, the API 32, and the server 33 is the same as the public cloud 10, the portal 11, the API 12, and the server 13 described above.

  The monitoring device 100 logs in to the portals 11 to 31 of the public clouds 10 to 30, and totals the charging information based on the charging tags included in the information on the display screen displayed when each portal 11 to 31 is accessed. It is a device that displays the total results. A billing tag is a tag with an id indicating the location that describes the billing that constitutes the screen described in the html file of each management screen of the public cloud, and the location where the enclosed amount is described It shall be a combination of character strings to be specified.

  In addition, the monitoring apparatus 100 acquires data managed in the public clouds 10 to 30 via the APIs 12 to 32 of the public clouds 10 to 30. For example, the monitoring apparatus 100 acquires data related to the number of instances, the number of images, network I / O, and data I / O as data managed in the public clouds 10 to 30.

  In addition, the monitoring apparatus 100 accesses the servers 13 to 33 that operate in the public clouds 10 to 30 and acquires data regarding the load status and the operating status of the servers 13 to 33.

  Next, the configuration of the monitoring apparatus 100 according to the present embodiment will be described. FIG. 2 is a functional block diagram illustrating the configuration of the monitoring apparatus according to the present embodiment. As illustrated in FIG. 2, the monitoring device 100 includes a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150.

  The communication unit 110 is a processing unit that performs data communication with the public clouds 10 to 30 via the network 50. Further, the communication unit 110 may communicate with each terminal device of a system used by a company or organization (not shown). The communication unit 110 corresponds to a communication device, for example. The control unit 150 described later exchanges data with the public clouds 10 to 30 and the terminal devices in the system via the communication unit 110.

  The input unit 120 is an input device that inputs various types of information to the monitoring device 100. The input unit 120 corresponds to a keyboard, a mouse, a touch panel, an input button, and the like.

  The display unit 130 is a display device that displays information output from the control unit 150. The display unit 130 corresponds to, for example, a display or a touch panel.

  The storage unit 140 includes an ID management table 141, a usage information table 142, and an operation status information table 143. The storage unit 140 corresponds to a storage device such as a semiconductor memory element such as a random access memory (RAM), a read only memory (ROM), and a flash memory.

  The ID management table 141 is a table that holds information in which a public cloud used by each department belonging to a company is associated with a user ID. FIG. 3 is a diagram illustrating an example of the data structure of the ID management table. As illustrated in FIG. 3, the ID management table 141 associates department identification information, a provider public cloud, and a user ID.

  The department identification information is information that uniquely identifies a department. The provider public cloud is information indicating a public cloud that provides a cloud service to the corresponding department. The user ID is information for each public cloud to identify each department that provides the cloud service. For example, the user ID is used when the department accesses the public cloud.

  For example, the department of the department identification information “first department” receives a cloud service from the public clouds 10 and 20. In addition, the combination of the user ID and the public cloud corresponding to the department of the department identification information “first department” is a pair of “A101” and “public cloud 10”, and a pair of “B101” and “public cloud 20”. There is a pair. Therefore, the public cloud 10 identifies the first department as the user ID “A101”. Further, the public cloud 20 identifies the first department as the user ID “B101”.

  The usage information table 142 is a table that holds usage information of each public cloud by each department. For example, the usage information includes information on the usage amount according to the usage of the cloud service.

  FIG. 4 is a diagram illustrating an example of the data structure of the usage information table. As shown in FIG. 4, this usage information table associates department identification information, a provider public cloud, and usage information. The explanation about the department identification information, the provider public cloud, and the usage information is the same as the above explanation.

  The operating status information table 143 is a table that holds operating status information of each public cloud used by each department. For example, the operation status information includes information on the number of high load servers, the transition of the number of owned images, and the number of stopped instances.

  FIG. 5 is a diagram illustrating an example of the data structure of the operating status information table. As illustrated in FIG. 5, the operating status information table 143 associates department identification information, a provider public cloud, and operating status information. Information related to the department identification information, the provider public cloud, and the operation status information is the same as described above.

  Returning to the description of FIG. The control unit 150 includes a collection unit 151, a detection unit 152, and a display unit 153. The control unit 150 corresponds to an integrated device such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The control unit 150 corresponds to an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

  The collection unit 151 is a processing unit that collects usage information and operation status information from the public servers 10 to 30. Hereinafter, an example of a process for collecting the usage information by the collection unit 151 and a process for collecting the operation status information will be described.

  An example of processing in which the collection unit 151 collects usage information will be described. Based on the ID management table 141, the collection unit 151 acquires a user ID corresponding to a public cloud that provides unselected department identification information. Using the acquired user ID, the collection unit 151 accesses the corresponding public cloud and collects usage information. The collection unit 151 registers the collected usage information in the usage information table 142 in association with the department identification information and the provider public cloud. As described above, the collection unit 151 acquires the user ID and then acquires the usage information using the user ID and repeatedly executes the process of registering the usage information in the usage information table 142.

  For example, if the collection unit 151 selects the combination of the department identification information “first department” and the provider public cloud “public cloud 10” in FIG. 3, the collection unit 151 sets the user ID “A101” corresponding to this combination. get. The collection unit 151 uses the user ID “A101” to log in to the portal 11 of the public cloud 10 and acquires the usage information corresponding to the user ID “A101” provided by the portal 11. The collection unit 151 registers the acquired usage information in the usage information table 142 in association with the department identification information “first department” and the provider public cloud “public cloud 10”.

  Here, an example of a display screen that is notified when the collection unit 151 accesses a portal of a public cloud will be described. Here, as an example, a case where the collection unit 151 accesses the portal 11 of the public cloud 10 will be described. When the collection unit 151 accesses the portal 11, a login screen is displayed by the portal 11.

  FIG. 6 is a diagram illustrating an example of a login screen. For example, the collection unit 151 logs in to the portal 11 by inputting the user ID in the user ID input area 60 a existing on the login screen 60.

  7 to 9 are diagrams showing examples of each screen notified by the portal 11 after login. As illustrated in FIG. 7, when the collection unit 151 logs in to the portal 11, the service menu screen 61 is displayed by the portal 11. The collection unit 151 selects and expands the account pull-down menu 61 a included in the service menu screen 61. For example, the selection of the pull-down menu 61 a by the collection unit 151 is the same as the selection of the screen information area 61 b corresponding to the service menu screen 61.

  Shifting to the description of FIG. The collection unit 151 selects and expands the account pull-down menu 61 a included in the service menu screen 61. When the collection unit 151 selects “billing and cost management” included in the pull-down menu 61 a, the billing and cost management dashboard screen 62 is displayed by the portal 11. For example, the selection of “billing and cost management” in the pull-down menu 61 a by the collection unit 151 is the same as the selection of the screen information area 61 c corresponding to the service menu screen 61.

  When the collection unit 151 selects “Bill” from the side menu 62 a of the claim and cost management dashboard screen 62, the bill screen 63 shown in FIG. 9 is displayed by the portal 11. For example, the collection unit 151 selecting “invoice” from the side menu 62 a is the same as selecting the screen information area 62 b corresponding to the claim and the cost management dashboard screen 62.

  The description shifts to the description of FIG. When the bill screen 63 is displayed, the collection unit 151 collects screen information corresponding to the bill screen 63 as usage information. For example, the collection unit 151 collects the usage information 63a illustrated in FIG. 9 and registers the collected usage information 63a in the usage information table 142 in association with the department identification information and the provider public cloud. For example, the usage information 63a includes a predetermined billing tag. To collect the billing tag on the invoice screen 63, it is surrounded by the tag “span” of the value near “table id =“ totalAmount ”” in the html file corresponding to the invoice screen 63. To get the specified string. The number “$ 0.00” described in the billing tag is billing information to be obtained. The reason for collecting the billing tag as described above is that only the total billing information that is unique is displayed on the invoice screen 63. Therefore, by finding a numeric value that is considered to be billing information, the numeric value is collected. This is because it can be determined that the total billing information is desired. In addition, since the procedure for finding the billing tag including the billing information is different for each public cloud, the procedure for collecting the billing tag for each public cloud is defined in advance and collected. The area indicated by the billing tag includes billing information indicating fee information charged to the department corresponding to the user ID. Although illustration is omitted, it is assumed that the billing information is associated with the date information.

  By the way, in the description of FIG. 7 to FIG. 9, the collection unit 151 performs “invoice screen 63” in the order of “service menu screen 61”, “claim and cost management dashboard screen 62”, and “invoice screen 63”. However, the present invention is not limited to this. When the collection unit 151 accesses the portal 11 with the user ID, the collection unit 151 directly accesses the usage information 63a including the charging tag on the bill screen 63 from the information provided by the portal 11 and corresponding to the user ID. 63a may be collected.

  Moreover, each screen shown in FIGS. 7-9 is an example, and it changes with portals of a public cloud. 10 and 11 are diagrams showing other examples of each screen notified by the portal after login.

  10 and 11, as an example, a case where the collection unit 151 accesses the portal 21 of the public cloud 20 will be described. In addition, description of the login screen displayed when the collection part 151 accesses the portal 21 is abbreviate | omitted.

  When the collection unit 151 logs in to the portal 21, the dashboard screen 71 is displayed by the portal 21. In FIG. 10, the collection unit 151 selects and expands a pull-down menu 71 a included in the dashboard screen 71. For example, the collection unit 151 selecting the pull-down menu 71 a is the same as selecting the screen information area 71 b corresponding to the dashboard screen 71.

  When the collection unit 151 selects “charge details” included in the pull-down menu 71 a, the fee detail screen 72 shown in FIG. 11 is displayed by the portal 21. For example, the collection unit 151 selecting “charge details” in the pull-down menu 71 a is the same as selecting the screen information area 71 c corresponding to the dashboard 71.

  The description shifts to the description of FIG. When the fee detail screen 72 is displayed, the collection unit 151 collects screen information corresponding to the fee detail screen 72 as usage information. For example, the collection unit 151 collects the usage information 72a illustrated in FIG. 11 and registers the collected usage information 72a in the usage information table 142 in association with the department identification information and the provider public cloud. For example, the usage information 72a includes a predetermined billing tag. The area indicated by the charging tag includes charging information. As for how to collect the billing tags on the fee detail screen 72, the fee detail screen 72 also includes subtotal amounts other than the total amount information in the table. Therefore, since only the total amount information to be acquired is uniquely described in an area other than the “table tag”, the portion including the amount information described in the area other than the “table tag” is defined as a charging tag. Determine and collect as usage information 72a.

  By the way, in the description of FIGS. 10 and 11, the collection unit 151 has been described by taking the case where the collection unit 151 arrives at the charge detail screen 72 in the order of the “dashboard screen 71” and the “charge detail screen 72”. It is not something. When the collection unit 151 accesses the portal 21 with the user ID, the collection unit 151 directly accesses the usage information 72a including the charging tag on the fee description screen 72 from the information corresponding to the user ID provided by the portal 21 and uses the information. Information 72a may be collected.

  Next, an example of a process in which the collection unit 151 collects operating status information will be described. For example, the collection unit 151 acquires operation status information included in each of the public clouds 10 to 30 via APIs 12 to 32 provided by the public clouds 10 to 30. The collection unit 151 acquires, as the operation status information, the transition of the number of image possessions corresponding to the user ID, the number of stopped instances, and the number of high load servers. Note that the collection unit 151 acquires operating status information using predetermined monitoring software for operating status information that cannot be acquired via the APIs 12 to 32. The collection unit 151 registers the collected operation status information in the operation status information table 143.

  Returning to the description of FIG. The detection unit 152 is a processing unit that scans the usage information for each public cloud stored in the usage information table 142 and detects the charging information included in the area related to the charging tag for each public cloud. The detection unit 152 outputs the detected charging information for each public cloud to the display unit 153.

  The display unit 153 is a processing unit that counts the billing information detected from each of the public clouds 10 to 30 and displays the count result. In addition, the display unit 153 aggregates the operation status information collected from each of the public clouds 10 to 30 and displays the aggregation result.

  An example of a process in which the display unit 153 displays the accounting information aggregation result will be described. The display unit 153 calculates the usage amount of each public cloud by totaling the usage fees included in the charging information of each public cloud notified from the detection unit 152 for each public cloud. Further, the display unit 153 calculates the usage amount for each date. For example, the display unit 153 calculates the usage amount of the public cloud 10, the usage amount of the public cloud 20, and the usage amount of the public cloud 30 for each date. The display unit 153 similarly calculates other public cloud usage amounts. Furthermore, the display unit 153 may also calculate a total usage amount that is the sum of the usage amounts of all public clouds.

  For example, when calculating the usage amount of the public cloud 10, the display unit 153 calculates the usage amount of the public cloud 10 by the first department, the usage amount of the public cloud 10 by the second department, and the public cloud by the third department. Total 10 usage charges. In addition, when the usage amount of the public cloud 10 by another department exists, the display unit 153 adds the usage amount by the other department to the usage amount of the public cloud 10 of the first to third departments.

  The display unit 153 generates a billing information screen 80 based on the billing information tabulation result. FIG. 12 is a diagram illustrating an example of a billing information screen. The billing information screen 80 in FIG. 12 includes billing screen areas 80a to 80f.

  The billing screen area 80 is a screen area showing the transition of the total usage amount of each public cloud. The vertical axis of the graph of the billing screen area 80 indicates the usage amount, and the horizontal axis indicates the date. The line segment 10 </ b> A is a line segment indicating a change in the usage amount of the public cloud 10. A line segment 10 </ b> B is a line segment indicating a change in the usage amount of the public cloud 20. The line segment 10 </ b> C is a line segment indicating a change in the usage amount of the public cloud 30. A line segment 10 </ b> D is a line segment showing a change in the usage amount of other public cloud (not shown).

  The billing screen areas 80b to 80e are areas that indicate usage amounts of public clouds 10 to 30 (or other public clouds not shown) for a certain month. For example, the billing screen area 80b is an area indicating the usage amount of the public cloud 10 in a certain month. The billing screen area 80c is an area indicating the usage amount of the public cloud 20 in a certain month. The billing screen area 80d is an area indicating the usage amount of the public cloud 30 for a certain month. The billing screen area 80e is an area showing the usage amount of a certain public cloud (not shown) for a certain month.

  The billing screen area 80f is an area indicating the total usage amount obtained by summing up the usage amounts of each public cloud in a certain month.

  The display unit 153 may display the charging information screen 80 on the display unit 130, or may notify and display the charging information screen 80 on a terminal device designated in advance.

  Subsequently, an example of a process in which the display unit 153 displays the operation result information aggregation result will be described. Here, as an example, a case will be described in which an aggregation result of the transition of the number of owned images, an aggregation result of the transition of the number of stopped instances, and an aggregation result of the transition of the number of high-load servers are displayed.

  The results of counting the number of image holdings will be described. For example, the display unit 153 calculates the number of images held in each public cloud by summing the number of images held in each public cloud based on the operating status information table 143 for each public cloud. . Further, the display unit 153 sums up the number of images held for each date.

  For example, the display unit 153 calculates the number of images held in the public cloud 10, the number of images held in the public cloud 20, and the number of images held in the public cloud 30 for each date. The display unit 153 similarly calculates the number of images held in other public clouds. The display unit 153 generates an image possession count totaling screen showing the totalization result of the transition of the image possession count.

  FIG. 13 is a diagram illustrating an example of the image possession count totaling screen. As shown in FIG. 13, the vertical axis of the graph of the image possession count tabulation screen 81 indicates the image possession count, and the horizontal axis indicates the date. A line segment 81A is a line segment indicating the transition of the number of images held in the public cloud 10. A line segment 81B is a line segment indicating the transition of the number of images held in the public cloud 20. A line segment 81 </ b> C is a line segment indicating the transition of the number of images held in the public cloud 30. A line segment 81D is a line segment indicating the transition of the number of images held in other public clouds (not shown).

  The display unit 153 may display the image possession number totaling screen 81 on the display unit 130 or may notify the image possession number totaling screen 81 to a predetermined terminal device for display.

  Next, the result of counting the transition of the number of stopped instances will be described. For example, the display unit 153 sums the number of stopped instances included in the operation status information of each public cloud based on the operation status information table 143 for each public cloud.

  For example, for each date, the display unit 153 calculates the number of stopped instances of the public cloud 10, the number of stopped instances of the public cloud 20, and the number of stopped instances of the public cloud 30. The display unit 153 similarly calculates the number of stopped instances of other public clouds. The display unit 153 generates a stopped instance totaling screen showing the totaling result of the transition of the number of stopped instances.

  FIG. 14 is a diagram illustrating an example of the stopped instance totaling screen. As shown in FIG. 14, the vertical axis of the graph of the stopped instance totaling screen 82 indicates the number of stopped instances, and the horizontal axis indicates the date. The line segment 82A is a line segment indicating the transition of the number of stopped instances of the public cloud 10. A line segment 82B is a line segment indicating the transition of the number of stopped instances of the public cloud 20. A line segment 82 </ b> C is a line segment indicating a transition of the number of stopped instances of the public cloud 30. The line segment 82D is a line segment indicating the transition of the number of stopped instances of other public clouds (not shown).

  The display unit 153 may display the stopped instance totaling screen 82 on the display unit 130 or may notify the terminal instance designated in advance to display the stopped instance totaling screen 82.

  Next, the result of counting the number of high load servers will be described. For example, the display unit 153 adds up the number of high-load servers included in the operation status information of each public cloud based on the operation status information table 143 for each public cloud.

  For example, the display unit 153 calculates the number of high-load servers in the public cloud 10, the number of high-load servers in the public cloud 20, and the number of high-load servers in the public cloud 30 for each date. The display unit 153 similarly calculates the number of other high-load servers in the public cloud. The display unit 153 generates a high load server number totaling screen showing the total result of the number of high load servers.

  FIG. 15 is a diagram illustrating an example of a high load server count screen. As shown in FIG. 15, the vertical axis of the graph of the high load server count tabulation screen 83 indicates the number of high load servers, and the horizontal axis indicates the date. A line segment 83 </ b> A is a line segment showing a transition of the number of high-load servers in the public cloud 10. A line segment 83 </ b> B is a line segment indicating the transition of the number of high-load servers in the public cloud 20. A line segment 83 </ b> C is a line segment indicating a change in the number of high-load servers in the public cloud 30.

  The display unit 153 may display the high load server number totaling screen 83 on the display unit 130 or may notify and display the high load server number totaling screen 83 on a terminal device designated in advance.

  Next, an example of a processing procedure of the monitoring apparatus 100 according to the present embodiment will be described. FIG. 16 is a flowchart illustrating the processing procedure of the monitoring apparatus according to the present embodiment. As illustrated in FIG. 16, the collection unit 151 of the monitoring device 100 determines whether to acquire usage information (step S101). When acquiring the usage information (step S101, Yes), the collection unit 151 logs in to the portals 11 to 31 of the public clouds 10 to 30 using the user ID (step S102).

  The collection unit 151 collects usage information corresponding to the user ID (step S103) and registers the usage information in the usage information table 142 (step S104). The detection unit 152 of the monitoring device 100 scans the user information, detects the charging tag, and acquires the charging information of the area corresponding to the charging tag (step S105).

  The display unit 153 of the monitoring device 100 aggregates the billing information for each public cloud (Step S106) and generates a billing information screen (Step S107). The display unit 153 displays the generated screen (step S108).

  Returning to the description of step S101. If the collection unit 151 does not acquire the usage information and acquires the operation status information (No at Step S101), the collection unit 151 proceeds to Step S109. The collection unit 151 collects the operation status information by using the APIs 12 to 32 or the monitoring software provided by the public clouds 10 to 30 (Step S109).

  The display unit 153 aggregates the number of images held, the number of stopped instances, and the number of high-load servers based on the operational status information of the public clouds 10 to 30 (step S110). The display unit 153 generates an image possession count total screen, a stopped instance count screen, and a high load server count total screen (step S111), and proceeds to step S108.

  Next, effects of the monitoring device 100 according to the present embodiment will be described. The monitoring apparatus 100 logs in to each portal 11 to 31 of each public cloud 10 to 30 and detects a charging tag of screen information displayed by each portal 11 to 31. The monitoring apparatus 100 aggregates and displays the charging information described in the area related to the charging tag. For this reason, the user can grasp | ascertain the charging condition regarding each public cloud 10-30.

  The monitoring device 100 collects the operation status information of each public cloud via the API provided by each public cloud, and displays the total result of the operation status information. For example, the totaling result of the operation status information includes the number of images held in each public cloud, the number of stopped instances, and the number of high load servers. For this reason, the user can efficiently execute a measure for suppressing the billing amount by referring to the operation status information together with the billing information. For example, when the number of stopped instances is large and the number of high-load servers is small, the charge amount can be reduced by reducing the number of instances under contract, the number of images, and the like.

  In the example shown in FIG. 12, the display unit 153 of the monitoring device 100 has shown an example of displaying the usage amount for each public cloud, but is not limited to this. For example, the usage amount for each department is displayed. An aggregated display screen may be generated. For example, with reference to FIG. 4, the display unit 153 aggregates the usage amounts of the first department based on the usage information of the public clouds 10 and 20 used by the first department. The display unit 153 aggregates the usage amount of the second department based on the usage information of the public clouds 20 and 30 used by the second department. The display unit 153 aggregates the usage amount of the third department based on the usage information of the public clouds 10 to 30 used by the third department. And the display part 153 produces | generates the display screen which shows the total result of the usage amount of a 1st-3rd department, and displays it on the display part 130. FIG. By executing such processing, the user can easily grasp the usage amount for each department.

  Further, the monitoring apparatus 100 may generate and display other display screens based on the operation status information. For example, when the operation status information includes network I / O information, the display unit 153 generates a display screen indicating the network I / O information for each public cloud. Further, when the operation status information includes data I / O information, the display unit 153 generates a display screen indicating the data I / O information for each public cloud.

  In addition, when generating the image possession count tabulation screen, the monitoring apparatus 100 displays the transition of the image possession count for each date, but may display the transition of the image possession count for each hour. The monitoring apparatus 100 displays the transition of the number of stopped instances for each date when generating the stopped instance totaling screen, but may display the transition of the number of stopped instances for each time. When the monitoring apparatus 100 generates the high load server count screen, the change in the number of high load servers for each date is displayed. However, the monitoring apparatus 100 may display the change in the number of high load servers for each time. good.

  By the way, among the processes described in the present embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Furthermore, each processing function performed by each device may be realized by a CPU and a program that is analyzed and executed by the CPU, or may be realized as hardware by wired logic.

10, 20, 30 Public cloud 11, 21, 31 Portal 12, 22, 32 API
13, 23, 33 Server 50 Network 100 Monitoring device

Claims (7)

A collection unit that accesses each portal site of a plurality of public clouds using user identification information and collects usage information for the user identification information from the portal site,
A detecting unit that detects each billing tag by scanning each usage information collected from each portal site of a plurality of public clouds, and detects billing information included in an area related to the billing tag for each public cloud;
A monitoring device, comprising: a display unit that aggregates billing information detected from each public cloud and displays the aggregation result.   The collection unit obtains information on the operating status of servers included in the plurality of public clouds via an API (Application Programming Interface) provided by the plurality of public clouds, and the display unit The monitoring apparatus according to claim 1, further displaying operation status information.   The display unit specifies usage information for the department from usage information collected by the collection unit based on a table in which the department and a plurality of user identification information used by the department are associated with each other. The monitoring apparatus according to claim 1, wherein accounting information for each department is displayed by aggregating accounting information detected from the specified usage information.   The table further associates public cloud information used by the department, and the display unit uses the usage information collected by the collecting unit based on the table to be used by the department. The monitoring apparatus according to claim 3, wherein the monitoring information is specified and counted for each public cloud, and billing information for each public cloud is displayed.   3. The display unit displays a server operating status for each date and a server operating status for each hour based on information on operating statuses of servers included in the plurality of public clouds. The monitoring device described in 1. A monitoring method performed by a computer,
Using the user identification information, access each portal site of a plurality of public clouds, collect the usage information for the user identification information from the portal site,
Scans each usage information collected from each portal site of a plurality of public clouds to detect a billing tag, detects billing information included in an area related to the billing tag for each public cloud,
A monitoring method characterized in that billing information detected from each public cloud is aggregated and each process for displaying the aggregated result is executed. On the computer,
Using the user identification information, access each portal site of a plurality of public clouds, collect the usage information for the user identification information from the portal site,
Scans each usage information collected from each portal site of a plurality of public clouds to detect a billing tag, detects billing information included in an area related to the billing tag for each public cloud,
A monitoring program characterized by causing billing information detected from each public cloud to be aggregated and displaying each aggregate result.

Images