Management device, management method, and computer program

Abstract

A management device according to the present invention manages a cloud system that is connected to an apparatus via a network. The management device comprises a reception unit that receives identification information for the apparatus, a connection relationship information acquisition unit that acquires connection relationship information for the apparatus and a plurality of resources associated with the cloud system on the basis of the identification information, and a display control unit that displays the plurality of resources on a screen on the basis of the connection relationship information in a manner that makes it possible to see the order in which data transits.

Description

Management device, management method, and computer program

[0001] This application claims priority to Japanese Patent Application No. 2024-022494, filed February 19, 2024, and incorporates by reference all of the contents of that application.

[0002] When developing a cloud system that connects various devices such as IoT (Internet of Things) devices, problems may occur in the cloud system due to various reasons such as insufficient resource performance in the development environment, changes to the development environment settings, the device installation environment, or device failure. For this reason, when unexpected behavior such as the inability to obtain data occurs, it is necessary to understand the status of the cloud system.

[0003] For example, a tool has been developed that visualizes log data in a cloud environment (see, for example, Non-Patent Document 1).

[0004] "An observability platform with all the necessary features", [online], 2024, Dynatrace, Inc., [Retrieved January 22, 2024], Internet <URL: https: / / www.dynatrace.com / ja / >

[0005] A management device according to one aspect of the present disclosure is a management device that manages a cloud system, wherein the cloud system is connected to equipment via a network, and the management device includes: a reception unit that receives identification information of the equipment; a connection relationship information acquisition unit that acquires connection relationship information between the equipment and multiple resources related to the cloud system based on the identification information; and a display control unit that displays the multiple resources on a screen in a manner that allows the order in which data passes to be recognized based on the connection relationship information.

[0006] The present invention can be realized not only as a management device having such a characteristic processing unit, but also as a management method having such characteristic processing steps, a computer program for causing a computer to execute such steps, a semiconductor integrated circuit that realizes part or all of the management device, or a cloud system that includes the management device.

[0007] FIG. 1 is a block diagram illustrating a configuration of a cloud system according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of a first malfunction that occurs in a cloud system. FIG. 3 is a diagram illustrating an example of a second malfunction that occurs in a cloud system. FIG. 4 is a diagram illustrating an example of a third malfunction that occurs in a cloud system. FIG. 5 is a diagram illustrating an example of a fourth malfunction that occurs in a cloud system. FIG. 6 is a diagram illustrating an example of a functional configuration of a cloud system. FIG. 7 is a diagram illustrating an example of a related resource DB. FIG. 8 is a diagram illustrating an example of an operation history DB. FIG. 9 is a diagram illustrating an example of a metrics DB. FIG. 10 is a diagram illustrating an example of a log DB. FIG. 11 is a diagram illustrating an example of a configuration of a cloud system. FIG. 12 is a diagram illustrating an example of a screen of a display device connected to an input / output I / F unit. FIG. 13 is a diagram illustrating an example of a screen of the display device. FIG. 14 is a sequence diagram illustrating an example of a process for implementing a function of displaying a list of resources related to a device. FIG. 15 is a diagram illustrating an example of a screen of the display device. FIG. 16 is a diagram illustrating an example of a screen of the display device. FIG. 17 is an enlarged view of the area within the dashed line in the screen illustrated in FIG. 16. Fig. 18 is a sequence diagram showing an example of processing for realizing a function for displaying the change history of resources related to a device. Fig. 19 is a diagram showing an example of a screen of a display device. Fig. 20 is a diagram showing an example of a screen of a display device. Fig. 21 is a diagram showing an example of a screen of a display device. Fig. 22 is a diagram showing an example of a screen of a display device. Fig. 23 is a sequence diagram showing an example of processing for realizing a function for displaying metrics information of resources related to a device. Fig. 24 is a diagram showing an example of a screen of a display device. Fig. 25 is a sequence diagram showing an example of processing for realizing a function for displaying log information of resources related to a device.

[0008] [Problem to be Solved by the Present Disclosure] With conventional techniques, even if data can be visualized, it is difficult to efficiently identify the cause of a problem in a cloud system.

[0009] The present disclosure has been made in consideration of these circumstances, and aims to provide a management device, a management method, and a computer program for efficiently identifying the cause of a malfunction in a cloud system connected to a device.

[0010] Effect of the Present Disclosure According to the present disclosure, it is possible to efficiently identify the cause of a malfunction in a cloud system connected to a device.

[0011] [Outline of Embodiments of the Present Disclosure] First, an outline of embodiments of the present disclosure will be listed and described. (1) A management device according to an embodiment of the present disclosure is a management device that manages a cloud system, the cloud system is connected to devices via a network, and the management device includes: a reception unit that receives identification information of the devices; a connection relationship information acquisition unit that acquires connection relationship information between the devices and multiple resources related to the cloud system based on the identification information; and a display control unit that displays the multiple resources on a screen in a manner that allows the order in which data passes through to be recognized based on the connection relationship information.

[0012] With this configuration, multiple resources related to the cloud system connected to the device are displayed on the screen in a manner that allows the user to recognize the order in which data passes through. Therefore, if a problem occurs in the cloud system, the user can check the path the data passed through by specifying the device's identification information. This allows the user to predict the resource that is causing the problem and efficiently identify the cause of the problem in the cloud system connected to the device.

[0013] (2) In (1) above, the management device may further include an operation history information acquisition unit that acquires, for each of the resources indicated by the connection relationship information, operation history information including operations related to the resource and the time at which the operations were performed, and the display control unit may further display on the screen, based on the operation history information, the operations related to the resource and the time at which the operations were performed, corresponding to each of the resources.

[0014] With this configuration, operation history information, including resource-related operations and the times at which those operations were performed, is displayed for each resource. This allows the user to confirm what operations were performed and when for each resource while checking the order in which data passed through the resource. This allows the user to efficiently identify the operation that may have caused the problem and the resource related to that operation.

[0015] (3) In (2) above, the receiving unit may further receive a first period, and the display control unit may display on the screen the operation performed during the first period and the time at which the operation was performed.

[0016] With this configuration, the operations to be displayed on the screen can be narrowed down to operations performed during the first period, thereby enabling the user to efficiently identify the cause of the malfunction.

[0017] (4) In any of (1) to (3) above, the management device may further include a metrics information acquisition unit that acquires metrics information including one or more metrics values ​​related to each of the resources, and the display control unit may further display the metrics values ​​related to each of the resources on the screen, corresponding to each of the resources based on the metrics information.

[0018] This configuration allows the metrics values ​​related to a resource to be displayed in association with the resource. This allows the user to check the metric values ​​of each resource while checking the order in which data passes through the resource. This allows the user to efficiently identify the resource in which a problem is occurring.

[0019] (5) In (4) above, the reception unit may further receive a second period, the metrics information may further include the time at which each of the metrics values ​​was measured, and the display control unit may display the metrics values ​​measured during the second period on the screen.

[0020] With this configuration, the metrics values ​​displayed on the screen can be narrowed down to those measured during the second period, allowing the user to efficiently identify the resource in which the problem is occurring.

[0021] (6) In the above (4) or (5), the display control unit may display a graph showing the change in the metrics value over time on the screen.

[0022] This configuration allows the user to detect, for example, an event in which a metrics value has suddenly changed, thereby enabling the user to efficiently identify a resource in which a problem has occurred.

[0023] (7) In any of (1) to (6) above, the management device may further include a log information acquisition unit that acquires log information for each resource, the log information including log content related to the resource and the time for the log content, and the display control unit may further display the log content and the time on the screen in association with each other based on the log information.

[0024] This configuration allows the user to check the log content related to the resource in association with the time, thereby enabling the user to efficiently identify the resource in which the problem has occurred.

[0025] (8) A management method according to another embodiment of the present disclosure is a management method for managing a cloud system, wherein the cloud system is connected to equipment via a network, and the management method includes the steps of: receiving identification information of the equipment; acquiring connection relationship information between the equipment and multiple resources related to the cloud system based on the identification information; and displaying the multiple resources on a screen in a manner that allows the order in which data passes through to be recognized based on the connection relationship information.

[0026] This configuration includes the characteristic processing steps of the above-described management device, and therefore provides the same functions and effects as the above-described management device.

[0027] (9) A computer program according to another embodiment of the present disclosure is a computer program for causing a computer to function as a management device for managing a cloud system, wherein the cloud system is connected to equipment via a network, and the computer program causes the computer to function as a reception unit that receives identification information of the equipment, a connection relationship information acquisition unit that acquires connection relationship information of multiple resources related to the equipment and the cloud system based on the identification information, and a display control unit that displays the multiple resources on a screen in a manner that allows the order in which data passes to be recognized based on the connection relationship information.

[0028] According to this configuration, the computer can function as the above-described management device, thereby achieving the same functions and effects as the above-described management device.

[0029] [Details of the Embodiments of the Present Disclosure] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that each of the embodiments described below represents a specific example of the present disclosure. The numerical values, shapes, materials, components, component placement and connection configurations, steps, and step order shown in the following embodiments are examples and do not limit the present disclosure. Furthermore, among the components in the following embodiments, components not recited in independent claims are components that can be added arbitrarily. Furthermore, each figure is a schematic diagram and is not necessarily a precise illustration.

[0030] The same components are denoted by the same reference numerals, and their functions and names are also the same, so their explanations will be omitted where appropriate.

[0031] [Overall Configuration of Cloud System] Fig. 1 is a block diagram showing the configuration of a cloud system according to an embodiment of the present disclosure. The cloud system 1 includes a single-tenant resource configuration. A tenant refers to an individual or business that uses the cloud system 1. The cloud system 1 includes multiple resources occupied by each of three tenants, Tenant A to Tenant C. However, the number of tenants is not limited to three.

[0032] For example, the system of tenant A in cloud system 1 includes a data lake 2A, a primary processing unit 3A, and a data database (hereinafter referred to as "data DB") 4A.

[0033] The data lake 2A is a resource for storing data. The data lake 2A is connected to a device 5A external to the cloud system 1 via a network such as the Internet. The data lake 2A receives data output by the device 5A and stores the received data without processing it.

[0034] The primary processing 3A is a resource that performs predetermined processing on data. The primary processing 3A is connected to the data lake 2A and the data DB 4A. The primary processing 3A reads data stored in the data lake 2A and performs predetermined processing on the read data. The primary processing 3A outputs processing result information to the data DB 4A.

[0035] The processing performed by the primary processing unit 3A is not limited to a specific type. For example, the processing may be a process of converting binary data into decimal physical quantity data and creating a database, or a process of extracting data from the most recent predetermined period of time from the data.

[0036] The data DB 4A is a resource that stores data. The data DB 4A receives and stores processing result information from the primary processing unit 3A. The data stored in the data DB 4A is used, for example, in processing executed by other resources.

[0037] The resources included in the systems of Tenant B and Tenant C of cloud system 1 are also similar to those of Tenant A. That is, the system of Tenant B of cloud system 1 includes a data lake 2B, a primary processing process 3B, and a data DB 4B, and the data lake 2B is connected to equipment 5B. The system of Tenant C of cloud system 1 includes a data lake 2C, a primary processing process 3C, and a data DB 4C, and the data lake 2C is connected to equipment 5C.

[0038] [Examples of Malfunctions] Next, examples of malfunctions occurring in the cloud system 1 will be described. FIG. 2 is a diagram illustrating an example of a first malfunction occurring in the cloud system 1. The first malfunction is a malfunction caused by insufficient resource performance in the development environment of the cloud system 1. For example, a quota function can be used to set an upper limit on performance for each resource. Setting this upper limit too low may result in insufficient performance in the cloud system 1.

[0039] As an example, suppose the quota function sets an upper limit on the data writing speed to the data DB 4A. If this upper limit is too low, a problem occurs in which the throughput of data written from the primary processing unit 3A to the data DB 4A decreases. This causes the amount of unprocessed data stored in the data lake 2A to gradually increase, and there may be a shortage of storage space for data uploaded from the device 5A.

[0040] For example, if the number of write requests to the data DB 4A falls below a threshold value or drops suddenly, there is a possibility that the first problem has occurred.

[0041] FIG. 3 is a diagram illustrating an example of a second malfunction that occurs in the cloud system 1. The second malfunction is a malfunction caused by a change in the settings of the development environment of the cloud system 1. For example, suppose that a developer of the cloud system 1 changes the setting value of some parameter of the primary processing process 3A to an incorrect value. In such a case, the primary processing process 3A may not operate normally, causing a malfunction in the cloud system 1. For example, a malfunction may occur in which the primary processing process 3A suddenly becomes unable to write the result information of the processing process to the data DB 4A.

[0042] For example, if the number of write requests to the data DB 4A suddenly becomes 0 after the developer changes the parameter setting value of the primary processing process 3A, there is a possibility that the second problem has occurred.

[0043] FIG. 4 is a diagram illustrating an example of a third malfunction that may occur in the cloud system 1. The third malfunction is a malfunction associated with the installation environment of devices connected to the cloud system 1. For example, assume that device 5A communicates wirelessly with a wireless base station 8 and uploads data to the cloud system 1 via the wireless base station 8. Assume also that device 5A is installed at an event venue, and numerous communication devices 6 communicate wirelessly with the wireless base station 8. In such a case, congestion may occur on the communication path from device 5A to the cloud system 1, resulting in delays or missing data being uploaded from device 5A to the data lake 2A. Furthermore, if device 5A is located in a shielded space, communication on the above communication path may become unstable, resulting in a similar problem.

[0044] For example, if the number of data sent by device 5A suddenly decreases, if device 5A fails to write data, or if the number of data received by data lake 2A suddenly decreases, the third malfunction may have occurred.

[0045] FIG. 5 is a diagram illustrating an example of a fourth malfunction that may occur in the cloud system 1. The fourth malfunction is a malfunction associated with a problem with a device connected to the cloud system 1. For example, a sensor 7 is connected to device 5A, and measurement data from the sensor 7 is uploaded to the cloud system 1. In such a case, if a malfunction occurs, such as the sensor 7 and device 5A being improperly connected, or if the cable connecting the sensor 7 and device 5A is properly connected but is disconnected from device 5A due to vibration, device 5A will not be able to acquire the measurement data from the sensor 7. This causes a malfunction in which device 5A cannot upload the measurement data to the cloud system 1. A similar malfunction may also occur if the communication circuit of device 5A is faulty.

[0046] For example, if the number of pieces of data transmitted by the device 5A becomes 0, or if the device 5A fails to write data, the fourth problem may have occurred.

[0047] [Display Dashboard] When a problem occurs in the cloud system 1 as described above, the cloud system 1 is provided with a display dashboard function to identify the cause of the problem.

[0048] 6 is a diagram showing an example of the functional configuration of the cloud system 1. The cloud system 1 includes a data lake 2A, a primary processing unit 3A, a data DB 4A, a related resource database (hereinafter referred to as the "related resource DB") 21, an operation history database (hereinafter referred to as the "operation history DB") 22, a metrics database (hereinafter referred to as the "metrics DB") 23, a log database (hereinafter referred to as the "log DB") 24, and a display dashboard 25.

[0049] As described above, the data lake 2A, the primary processing unit 3A, and the data DB 4A are included in the system of tenant A. Although not shown in Fig. 6, the cloud system 1 also includes resources that constitute the system of tenant B and the system of tenant C.

[0050] The related resource DB 21 is a database that shows connection relationship information between multiple resources included in each tenant system and devices connected to the system. A developer sets the connection relationship information in the related resource DB 21 in advance. However, the cloud system 1 may set the connection relationship information in the related resource DB 21. For example, for data passing through a device or resource, the device or resource may write its own ID into the data, and the cloud system 1 may automatically identify the connection relationship information from the device or resource ID written in the data and set it in the related resource DB 21. Details of the related resource DB 21 will be described later.

[0051] The operation history DB 22 is a database that indicates, for each resource included in each tenant's system, operation history information including operations related to the resource and the time when the operation was performed. For example, each time an operation is performed, a resource related to the operation may write the operation and the time to the operation history DB 22. Details of the operation history DB 22 will be described later.

[0052] The metrics DB 23 is a database that indicates metrics information including one or more metrics values ​​related to each resource included in each tenant system. For example, the cloud system 1 may calculate the metrics values ​​of each resource at a predetermined interval and write the calculated metrics values ​​to the metrics DB 23. Details of the metrics DB 23 will be described later.

[0053] The log DB 24 is a database that indicates log information for each resource included in each tenant system, including log content including the operation status or error content related to the resource and the time for the log content. The log DB 24 stores information on the log content and time uploaded from the device 5A. Details of the log DB 24 will be described later.

[0054] The display dashboard 25 controls the display of information about the resources of the tenant system related to the device selected by the user on the screen of a display device such as an LCD display, based on the related resource DB 21, operation history DB 22, metrics DB 23, and log DB 24. The developer uses the information displayed on the screen as a clue to identify the cause of the problem.

[0055] [Related Resource DB 21] Fig. 7 is a diagram showing an example of the related resource DB 21. The related resource DB 21 includes a plurality of records, each of which includes a "device ID," a "resource name," and a "sequence in the system."

[0056] "Device ID" indicates identification information of a device connected to the cloud system 1. Here, device ID "A" indicates device 5A, device ID "B" indicates device 5B, and device ID "C" indicates device 5C.

[0057] "Resource name" indicates the name of a resource related to a device identified by a device ID or the name of a device identified by a device ID. Here, the names of devices 5A, 5B, and 5C are assumed to be device A, device B, and device C, respectively. The names of data lake 2A, data lake 2B, and data lake 2C are assumed to be data lake A, data lake B, and data lake C, respectively. The names of primary processing process 3A, primary processing process 3B, and primary processing process 3C are assumed to be primary processing process A, primary processing process B, and primary processing process C, respectively. The names of data DB4A, data DB4B, and data DB4C are assumed to be data DBA, data DBB, and data DBC, respectively.

[0058] Resources and devices with a common device ID indicate resources belonging to the system of the tenant identified by the device ID and devices connected to the system of the tenant. For example, resources with device ID "A" include Data Lake A, Primary Processing A, and Data DBA, which belong to the system of Tenant A. Furthermore, the device with device ID "A" is Device A, which is connected to the system of Tenant A.

[0059] The "order within a system" indicates the connection order of resources and devices connected to the system within the same tenant system, and means that resources or devices are connected in ascending order within the system. Here, the order "0" within the system refers to a device connected to the tenant system.

[0060] For example, for the system of tenant A, the devices and resources are connected in the order of device A → data lake A → primary processing A → data DBA. Similarly, for the system of tenant B identified by device ID "B", the devices and resources are connected in the order of device B → data lake B → primary processing B → data DBB.

[0061] [Operation History DB 22] Fig. 8 is a diagram showing an example of the operation history DB 22. The operation history DB 22 contains multiple records, each of which includes a "developer name," a "timestamp," a "resource name," an "operation name," and an "operation content." The "developer name" indicates the name of the developer who performed an operation related to a resource. The "timestamp" indicates the date and time when the operation was performed.

[0062] "Resource name" indicates the name of the resource that is the target of the operation. Specific examples of resource names are the same as those in FIG.

[0063] The "operation name" indicates the operation performed on the resource, and includes create, update, view, and delete. The operation name "create" indicates an operation to create a new resource, for example, by registering a new script or allocating a new data area. The operation name "update" indicates an operation to update an already created resource, for example, by updating a script or changing a setting value. The operation name "view" indicates an operation to view a resource, for example, by obtaining the resource's setting value from the resource. The operation name "delete" indicates an operation to delete a resource, for example, by deleting a script or freeing up allocated data area. The "operation content" indicates the detailed content of the operation performed on the resource.

[0064] For example, the operation history DB 22 shows that developer "UX" created primary processing process A by registering a new script at 15:00:00 on November 25, 2023. It also shows that developer "UZ" updated the data DBA by changing the value of parameter α set in the data DBA to 1000 at 15:15:00 on November 30, 2023.

[0065] 9 is a diagram showing an example of the metrics DB 23. The metrics DB 23 includes a plurality of records, each of which includes a "resource name," a "timestamp," a "metric name," and a "metric value."

[0066] "Resource name" indicates the name of the device or resource. Specific examples of names are the same as those in Figures 7 and 8. "Resource name" indicates the name of the device or resource from which the metrics value is to be obtained. "Timestamp" indicates the date and time when the metrics value was obtained.

[0067] "Metric name" indicates the name of the metric acquired by the device or resource. "Number of sent data" indicates the number of data sent from the device or resource. "Number of received data" indicates the number of data received by the device or resource. "Total size of received data" indicates the total size of data received by the device or resource. "Number of completed processes" indicates the number of processes that the device or resource has completed. "Number of write requests" indicates the number of data write process requests made to the device or resource. "Metric value" indicates the value of the acquired metric.

[0068] For example, the metrics DB 23 indicates that device A sent 100 pieces of data at 03:14:02 on Dec. 1, 2023. It also indicates that data lake A received 150 pieces of data at 03:14:07 on Dec. 1, 2023.

[0069] 10 is a diagram showing an example of the log DB 24. The log DB 24 contains a plurality of records, each of which includes a "resource name," a "timestamp," and a "log message."

[0070] "Resource name" indicates the name of the device or resource. Specifically, "resource name" indicates the name of the device or resource related to the "log message." Specific examples of device or resource names are the same as those in Figures 7 to 9. "Timestamp" indicates the date and time when the "log message" was acquired. "Log message" indicates the log content, such as the operating status of the device or resource, or the content of any errors that occurred in the device or resource.

[0071] For example, the log DB 24 indicates that a log message regarding an error (ERROR) from device A was acquired at 03:14:00 on Dec. 1, 2023. The log message includes log content indicating that the data transmission process timed out and a transmission retry was performed.

[0072] It also shows that a log message regarding the operational status (INFO) of Data Lake A was acquired at 03:14:02 on Dec. 1, 2023. The log message includes log content indicating that data transmission has been completed.

[0073] 11 is a diagram showing an example of the configuration of the cloud system 1. The cloud system 1 includes a communication I / F (interface) unit 11, an input / output I / F unit 12, a storage device 13, a control device 14, and an internal bus 15.

[0074] The communication I / F unit 11 is an interface for communicating with external devices, and includes, for example, a wireless communication module. The communication I / F unit 11 communicates with the devices 5A, 5B, and 5C via the wireless base station 8.

[0075] The input / output I / F unit 12 is an interface for connecting input / output devices, such as a display device such as a liquid crystal display and an input device such as a keyboard or a mouse.

[0076] The storage device 13 is composed of a volatile memory element such as an SRAM (Static Random Access Memory) or a DRAM (Dynamic Random Access Memory), a non-volatile memory element such as a flash memory or an EEPROM (Electrically Erasable Programmable Read-Only Memory), or a magnetic storage device such as a hard disk.

[0077] The storage device 13 stores computer programs executed by the control device 14. The storage device 13 also stores a related resource DB 21, an operation history DB 22, a metrics DB 23, and a log DB 24. The storage device 13 also has storage areas for realizing data lake 2A, data lake 2B, and data lake 2C. The storage device 13 also stores data DB 4A, data DB 4B, and data DB 4C.

[0078] The control device 14 is configured with various processors suitable for controlling the cloud system 1, such as a central processing unit (CPU), a micro processing unit (MPU), and a graphics processing unit (GPU). The control device 14 reads and executes a computer program stored in the storage device 13. The control device 14 may be a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or the like configured to execute a processing procedure indicated by the computer program.

[0079] The control device 14 executes a computer program to functionally realize primary processing steps 3A, 3B, and 3C, and a display dashboard 25. Note that different computer programs are used to realize each of the primary processing steps and the display dashboard 25.

[0080] The display dashboard 25 functionally includes a reception unit 31, a connection relationship information acquisition unit 32, a display control unit 33, an operation history information acquisition unit 34, a metrics information acquisition unit 35, and a log information acquisition unit 36. Details of each of these processing units will be described later.

[0081] The internal bus 15 connects the communication I / F unit 11, the input / output I / F unit 12, the storage device 13, and the control device 14.

[0082] Below, each processing unit provided in the display dashboard 25 will be described in detail, while giving examples of four functions provided in the display dashboard 25.

[0083] [First Function Example of Display Dashboard 25] The display dashboard 25 has, as a first function, a function of displaying a list of resources related to devices.

[0084] 12 is a diagram showing an example of a screen 100 of a display device connected to the input / output I / F unit 12. The display control unit 33 generates an image to be displayed on the screen 100 and outputs it to the display device, thereby displaying the image on the screen 100. A device selection field 110 is displayed on the screen 100. The device selection field 110 is a field for receiving a user's selection of a device connected to the cloud system 1.

[0085] The reception unit 31 receives data input by a user such as a developer using an input device via the input / output I / F unit 12. Specifically, the reception unit 31 receives identification information of devices connected to the cloud system 1.

[0086] For example, the user operates the input device to select "Device ID A" from the device selection field 110. The accepting unit 31 accepts the device ID "A" corresponding to the selection result from the input device as device identification information.

[0087] The connection relationship information acquiring unit 32 acquires, from the related resource DB 21, connection relationship information between the device and a plurality of resources related to the cloud system 1 connected to the device, based on the device identification information (here, device ID "A") accepted by the accepting unit 31. With reference to Fig. 7, for example, if the device identification information is device ID "A", the connection relationship information acquiring unit 32 acquires four records including device ID "A" (the first to fourth records in Fig. 7) as connection relationship information.

[0088] The display control unit 33 displays the devices and the multiple resources on the screen 100 in a manner that allows the user to recognize the order in which data passes, based on the connection relationship information acquired by the connection relationship information acquisition unit 32 .

[0089] 13 is a diagram showing an example of a screen 100 of a display device. In addition to a device selection field 110, a resource display field 120 is displayed on the screen 100. The resource display field 120 lists icons 121 to 124 representing devices and resources based on connection relationship information based on device ID "A," sorting them in ascending order within the system, and indicates the flow of data with arrows. That is, icons 121, 122, 123, and 124 represent device A, data lake A, primary processing process A, and data DBA, respectively. Furthermore, data is sent from device A to data lake A, data is sent from data lake A to primary processing process A, and data is sent from primary processing process A to data DBA.

[0090] FIG. 14 is a sequence diagram illustrating an example of a process for realizing a function of displaying a list of resources related to a device.

[0091] When the user selects a device ID while the screen 100 shown in FIG. 12 is displayed, the display dashboard 25 accepts the device ID (step S11).

[0092] The display dashboard 25 queries the related resource DB 21 for connection relationship information based on the received device ID (step S12).

[0093] In response to the inquiry from the display dashboard 25, the related resource DB 21 searches for the corresponding connection relationship information and transmits it to the display dashboard 25. The display dashboard 25 receives the connection relationship information (step S13).

[0094] The display dashboard 25 performs a display process of the screen 100 shown in FIG. 13 based on the received connection relationship information (step S14).

[0095] By selecting a device ID, the user can check the data path, which allows the user to predict the resource causing the problem and efficiently identify the cause of the problem in the cloud system connected to the device.

[0096] [Second Function Example of Display Dashboard 25] The display dashboard 25 has, as a second function, a function of displaying the change history of resources related to devices.

[0097] 15 is a diagram showing an example of a screen 100 of the display device. The screen 100 includes a device selection field 110, a start time specification field 130, and an end time specification field 140.

[0098] The device selection field 110 is the same as that shown in Fig. 12. The start time specification field 130 and the end time specification field 140 are fields for the user to specify the start time and end time, respectively, of the period of the change history to be displayed.

[0099] For example, the user operates the input device to select "Device ID A" from the device selection field 110. The accepting unit 31 accepts the device ID "A" corresponding to the selection result from the input device as device identification information.

[0100] Furthermore, the user operates the input device to specify a start time of "2023-11-30 00:00:00" in the start time specification field 130, and an end time of "2023-12-02 12:00:00" in the end time specification field 140. The reception unit 31 receives information about a period including the specified start time of "2023-11-30 00:00:00" and end time of "2023-12-02 12:00:00".

[0101] The connection relationship information acquisition unit 32 acquires connection relationship information between the device and multiple resources related to the cloud system 1 connected to the device from the related resource DB 21 based on the device identification information (here, device ID ``A'') received by the reception unit 31.

[0102] The operation history information acquisition unit 34 acquires, for each resource indicated by the connection relationship information acquired by the connection relationship information acquisition unit 32, operation history information including operations related to the resource and the times at which the operations were performed, from the operation history DB 22, the operation history information including the above-mentioned times within the period accepted by the acceptance unit 31.

[0103] For example, the resources indicated by the connection relationship information are Data Lake A, Primary Processing Process A, and Data DBA. Referring to Fig. 8 , the operation history information acquisition unit 34 extracts records (five records, first to fifth, in Fig. 8 ) that include Data Lake A, Primary Processing Process A, or Data DBA in the "resource name." Of the extracted records, the operation history information acquisition unit 34 acquires, as operation history information, records (four records, second to fifth, in Fig. 8 ) that have timestamps within the period from the start time "November 30, 2023, 00:00:00" to the end time "December 2, 2023, 12:00:00."

[0104] The display control unit 33 displays the operations and times corresponding to the resources on the screen in association with each resource based on the operation history information acquired by the operation history information acquisition unit 34 .

[0105] 16 is a diagram showing an example of a screen 100 of a display device. In addition to a device selection field 110, a start time specification field 130, and an end time specification field 140, the screen 100 displays a resource display field 120. Icons 121 to 124 shown in the resource display field 120 are the same as those shown in FIG. 13 .

[0106] 16, operation display columns 150A to 150D are displayed. Each operation display column shows the operation content related to the resource indicated by the icon connected by a line. For example, operation display column 150A is connected to icon 122, so it shows the operation content related to the data lake. Furthermore, operation display column 150B is connected to icon 123, so it shows the operation content related to the primary processing process. Furthermore, operation display columns 150C and 150D are connected to icon 124, so it shows the operation content related to the data DB.

[0107] Fig. 17 is an enlarged view of the area within dashed line 160 on screen 100 shown in Fig. 16. Operation display field 150B includes information included in the second record of operation history DB 22 shown in Fig. 8. Operation display field 150C and operation display field 150D include information included in the fourth and fifth records of operation history DB 22 shown in Fig. 8, respectively.

[0108] FIG. 18 is a sequence diagram showing an example of a process for realizing a function for displaying the change history of resources related to a device.

[0109] When the screen 100 shown in FIG. 15 is displayed, the user selects a device ID and specifies a start time and an end time, and the display dashboard 25 accepts the device ID, start time, and end time (step S21).

[0110] The display dashboard 25 queries the related resource DB 21 for connection relationship information based on the received device ID (step S22).

[0111] In response to the inquiry from the display dashboard 25, the related resource DB 21 searches for the corresponding connection relationship information and transmits it to the display dashboard 25. The display dashboard 25 receives the connection relationship information (step S23).

[0112] The display dashboard 25 queries the operation history DB 22 for operation history information based on the list of resources included in the received connection relationship information and the received start time and end time (step S24).

[0113] In response to the inquiry from the display dashboard 25, the operation history DB 22 searches for the corresponding operation history information and transmits it to the display dashboard 25. The display dashboard 25 receives the operation history information (step S25).

[0114] The display dashboard 25 performs a display process of the screen 100 shown in FIGS. 16 and 17 based on the received operation history information (step S26).

[0115] In this way, operation history information, including resource-related operations and the times at which those operations were performed, is displayed for each resource. This allows the user to confirm what operations were performed and when for each resource while checking the order in which data passes through the resource. This allows the user to efficiently identify the operation that may have caused the problem and the resource related to that operation.

[0116] [Third Function Example of Display Dashboard 25] The display dashboard 25 has, as a third function, a function of displaying metrics information of resources related to devices.

[0117] 19 is a diagram showing an example of a screen 100 of a display device. The screen 100 includes a device selection field 110, a start time specification field 130, and an end time specification field 140. These are similar to those shown in FIG.

[0118] For example, the user operates the input device to select "Device ID A" from the device selection field 110. The accepting unit 31 accepts the device ID "A" corresponding to the selection result from the input device as device identification information.

[0119] The connection relationship information acquisition unit 32 acquires connection relationship information between the device and multiple resources related to the cloud system 1 connected to the device from the related resource DB 21 based on the device identification information (here, device ID ``A'') received by the reception unit 31.

[0120] The metrics information acquisition unit 35 acquires, for each resource included in the connection relationship information acquired by the connection relationship information acquisition unit 32, metrics corresponding to the resource from the metrics DB 23. For example, the metrics information acquisition unit 35 acquires, from the related resource DB 21, metrics names (hereinafter also referred to as "metrics") corresponding to each of the resource names Device A, Data Lake A, Primary Processing Process A, and Data DB A included in the connection relationship information. Referring to FIG. 9 , the metrics information acquisition unit 35 acquires the metric name "Number of Transmitted Data Items" corresponding to the resource name "Device A," and the metric names "Number of Receptions" and "Total Size of Received Data Items" corresponding to the resource name "Data Lake A." The metrics information acquisition unit 35 also acquires the metric name "Number of Completed Processing Items" corresponding to the resource name "Primary Processing Process A," and the metric name "Number of Write Requests" corresponding to the resource name "Data DB A."

[0121] The display control unit 33 displays a plurality of resources and metrics names on the screen 100 based on the connection relationship information acquired by the connection relationship information acquisition unit 32 and the metrics names acquired by the metrics information acquisition unit 35 .

[0122] FIG. 20 is a diagram showing an example of a screen 100 of a display device. The screen 100 displays a resource display field 120 in addition to a device selection field 110, a start time specification field 130, and an end time specification field 140. Similar to the example shown in FIG. 13 , the resource display field 120 displays icons 121, 122, 123, and 124 representing devices and resources based on connection relationship information based on device ID "A." In addition, the resource display field 120 displays metrics selection fields 171, 172, 173, and 174 corresponding to the icons 121, 122, 123, and 124, respectively. The metrics selection field 171 includes a check box for selecting the metric "number of transmissions" corresponding to device A. The metrics selection field 172 includes check boxes for selecting the metrics "number of receptions" and "total size of received data" corresponding to data lake A. The metrics selection field 173 has a check box for selecting the metric "number of processes completed" corresponding to the primary processing process A. The metrics selection field 174 has a check box for selecting the metric "number of write requests" corresponding to the data DBA.

[0123] 21 is a diagram showing an example of a display device screen 100. For example, suppose that a user operates an input device to check all check boxes provided in metrics selection fields 171, 172, 173, and 174, thereby specifying all metrics.

[0124] Also, assume that the user inputs the start time and end time of the metrics value to be displayed in the start time specification field 130 and the end time specification field 140. The start time specification field 130 and the end time specification field 140 are fields where the user can specify the start time and end time of the metrics value to be displayed.

[0125] The metrics information acquisition unit 35 acquires from the metrics DB 23 metrics values ​​of the specified metrics, whose timestamps are included within the period specified by the specified start time and end time.

[0126] The display control unit 33 generates an image based on the acquired metrics values ​​and displays it on the screen 100. For example, the display control unit 33 may display the metrics values ​​themselves on the screen 100, or may display a graph generated based on the metrics values ​​on the screen 100.

[0127] 22 is a diagram showing an example of a screen 100 of a display device. The screen 100 includes a device selection field 110, a start time specification field 130, an end time specification field 140, and a resource display field 120. The resource display field 120 includes graphs 181, 182, 183, and 184, respectively, instead of the metrics selection fields 171, 172, 173, and 174 shown in FIG.

[0128] Graph 181 is a graph showing the change over time in the metric "number of transmissions" corresponding to device A. The horizontal axis represents time, and the vertical axis represents the number of transmissions.

[0129] Graph 182 is a graph showing the time changes in the metrics "number of receptions" and "total size of received data" corresponding to Data Lake A. The horizontal axis represents time, and the vertical axis represents the number of receptions or the total size of received data. The solid curve represents the time change in the number of receptions, and the dashed curve represents the time change in the total size of received data.

[0130] Graph 183 is a graph showing the change over time in the metric "number of completed processes" corresponding to primary processing A. The horizontal axis indicates time, and the vertical axis indicates the number of completed processes.

[0131] Graph 184 is a graph showing the change over time in the metric "number of write requests" corresponding to data DBA. The horizontal axis represents time, and the vertical axis represents the number of write requests.

[0132] FIG. 23 is a sequence diagram showing an example of a process for realizing a function for displaying metrics information of resources related to a device.

[0133] When the user selects a device ID while the screen 100 shown in FIG. 19 is displayed, the display dashboard 25 accepts the device ID (step S31).

[0134] The display dashboard 25 queries the related resource DB 21 for connection relationship information based on the received device ID (step S32).

[0135] In response to the inquiry from the display dashboard 25, the related resource DB 21 searches for the corresponding connection relationship information and transmits it to the display dashboard 25. The display dashboard 25 receives the connection relationship information (step S33).

[0136] The display dashboard 25 queries the metrics DB 23 for metrics based on the list of resources included in the received connection relationship information (step S34).

[0137] In response to an inquiry from the display dashboard 25, the metrics DB 23 searches for the relevant metrics and transmits them to the display dashboard 25. The display dashboard 25 receives the list of metrics (step S35).

[0138] The display dashboard 25 performs a display process of the screen 100 shown in FIG. 20 based on the received list of metrics (step S36).

[0139] As shown in FIG. 21, on screen 100, the user selects metrics for each resource and specifies the start time and end time, and then display dashboard 25 accepts the metrics, start time, and end time (step S37).

[0140] Based on the combination of resources and metrics and the start and end times, the display dashboard 25 queries the metrics DB 23 for the metric values ​​of the metrics for each resource specified by the combination during the period specified by the start and end times (step S38).

[0141] In response to the inquiry from the display dashboard 25, the metrics DB 23 searches for the corresponding metrics value and transmits it to the display dashboard 25. The display dashboard 25 receives the metrics value (step S39).

[0142] The display dashboard 25 performs a display process of the screen 100 shown in FIG. 22 based on the received metrics values ​​(step S40).

[0143] In this way, the metrics values ​​related to the resources or the changes in the metrics values ​​over time can be displayed in correspondence with the resources. This allows the user to check the metrics values ​​of each resource or the changes in the metrics values ​​over time while checking the order in which data passes through the resources. This allows the user to efficiently identify resources that are experiencing problems.

[0144] [Fourth Example of Function of Display Dashboard 25] The display dashboard 25 has a fourth function of displaying log information of resources related to devices.

[0145] As shown in FIG. 15, a device selection field 110, a start time specification field 130, and an end time specification field 140 are displayed on a screen 100 of the display device.

[0146] For example, the user operates the input device to select "Device ID A" from the device selection field 110. The accepting unit 31 accepts the device ID "A" corresponding to the selection result from the input device as device identification information.

[0147] Furthermore, the user operates the input device to specify "2023-11-30 00:00:00" in the start time specification field 130 and "2023-12-02 12:00:00" in the end time specification field 140. The reception unit 31 receives information about the period including the specified start time "2023-11-30 00:00:00" and end time "2023-12-02 12:00:00".

[0148] The connection relationship information acquisition unit 32 acquires connection relationship information between the device and multiple resources related to the cloud system 1 connected to the device from the related resource DB 21 based on the device identification information (here, device ID ``A'') received by the reception unit 31.

[0149] The log information acquisition unit 36 ​​acquires, for each resource indicated by the connection relationship information acquired by the connection relationship information acquisition unit 32, log information related to the resource, which includes a timestamp within the period accepted by the acceptance unit 31, from the log DB 24.

[0150] The display control unit 33 displays the log content and the timestamp on the screen in association with each other based on the log information acquired by the log information acquisition unit 36 ​​.

[0151] 24 is a diagram showing an example of a screen 100 of the display device. In addition to a device selection field 110, a start time specification field 130, and an end time specification field 140, the screen 100 displays a log display field 190. The log display field 190 includes the acquired log contents. Note that, if all the log contents cannot be displayed at once, the display control unit 33 may scroll the log contents.

[0152] FIG. 25 is a sequence diagram showing an example of a process for realizing a function for displaying log information of resources related to a device.

[0153] When the screen 100 shown in FIG. 15 is displayed, the user selects a device ID and specifies a start time and an end time, and the display dashboard 25 accepts the device ID, start time, and end time (step S41).

[0154] The display dashboard 25 queries the related resource DB 21 for connection relationship information based on the received device ID (step S42).

[0155] In response to the inquiry from the display dashboard 25, the related resource DB 21 searches for the corresponding connection relationship information and transmits it to the display dashboard 25. The display dashboard 25 receives the connection relationship information (step S43).

[0156] The display dashboard 25 queries the log DB 24 for log information based on the list of resources included in the received connection relationship information and the received start time and end time (step S44).

[0157] In response to the inquiry from the display dashboard 25, the log DB 24 searches for the corresponding log information and transmits it to the display dashboard 25. The display dashboard 25 receives the log information (step S45).

[0158] The display dashboard 25 performs a display process of the screen 100 shown in FIG. 25 based on the received log information (step S46).

[0159] The user can check the log content related to the resource in association with the timestamp, which allows the user to efficiently identify the resource in which the problem is occurring.

[0160] [Note] In the above-described embodiment, each tenant's system includes resources of the cloud system 1. However, the system may also include devices connected to the cloud system 1. Each process (each function) in the above-described embodiment is realized by a processing circuit including one or more processors. The processing circuit may be configured with an integrated circuit or the like that combines one or more memories, various analog circuits, and various digital circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each process. The one or more processors may execute each process according to the program read from the one or more memories, or according to a logic circuit designed in advance to execute each process. The processor may be any of various processors suitable for computer control, such as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a field programmable gate array (FPGA), or an application-specific integrated circuit (ASIC). The physically separated processors may cooperate with each other to execute the processes. For example, the processors installed in the physically separated computers may cooperate with each other via a network such as a local area network (LAN), a wide area network (WAN), or the Internet to execute the processes. The program may be installed in the memory from an external server device or the like via the network, or may be distributed in a state stored on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a semiconductor memory, and installed in the memory from the recording medium.

[0161] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

[0162] 1 Cloud system 2A, 2B, 2C Data lake 3A, 3B, 3C Primary processing 4A, 4B, 4C Data DB 5A, 5B, 5C Equipment 6 Communication equipment 7 Sensor 8 Wireless base station 11 Communication I / F unit 12 Input / output I / F unit 13 Storage device 14 Control device 15 Internal bus 21 Related resource DB 22 Operation history DB 23 Metrics DB 24 Log DB 25 Display dashboard 31 Reception unit 32 Connection relationship information acquisition unit 33 Display control unit 34 Operation history information acquisition unit 35 Metrics information acquisition unit 36 ​​Log information acquisition unit 100 Screen 110 Equipment selection field 120 Resource display field 121, 122, 123, 124 Icon 130 Start time specification field 140 End time specification field 150A, 150B, 150C, 150D Operation display field 160 Dashed line 171, 172, 173, 174 Metrics selection field 181, 182, 183, 184 Graph 190 Log display field

Claims

1. A management device that manages a cloud system, the cloud system being connected to devices via a network, the management device comprising: a reception unit that receives identification information of the devices; a connection relationship information acquisition unit that acquires connection relationship information between the devices and multiple resources related to the cloud system based on the identification information; and a display control unit that displays the multiple resources on a screen in a manner that allows the order in which data passes to be recognized based on the connection relationship information.

2. The management device of claim 1, further comprising an operation history information acquisition unit that acquires, for each resource indicated by the connection relationship information, operation history information including operations related to the resource and the time at which the operations were performed, and the display control unit further displays on the screen, based on the operation history information, the operations related to the resource and the time at which the operations were performed, corresponding to each resource.

3. The management device according to claim 2, wherein the reception unit further receives a first period, and the display control unit displays on the screen the operations performed during the first period and the times at which the operations were performed.

4. A management device as described in any one of claims 1 to 3, further comprising a metrics information acquisition unit that acquires metrics information including one or more metrics values ​​related to each of the resources, and the display control unit further displays the metrics values ​​related to each of the resources on the screen, corresponding to each of the resources based on the metrics information.

5. The management device described in claim 4, wherein the receiving unit further receives a second period, the metrics information further includes the time at which each of the metrics values ​​was measured, and the display control unit displays the metrics values ​​measured during the second period on the screen.

6. The management device according to claim 4 or 5, wherein the display control unit displays a graph showing the change in the metrics value over time on the screen.

7. A management device as described in any one of claims 1 to 6, further comprising a log information acquisition unit that acquires log information for each resource, the log information including log content related to the resource and the time for the log content, and the display control unit further displays the log content and the time on the screen in association with each other based on the log information.

8. A management method for managing a cloud system, wherein the cloud system is connected to equipment via a network, the management method comprising: a step of receiving identification information of the equipment; a step of obtaining connection relationship information between the equipment and multiple resources related to the cloud system based on the identification information; and a step of displaying the multiple resources on a screen in a manner that allows the order in which data passes to be recognized based on the connection relationship information.

9. A computer program for causing a computer to function as a management device for managing a cloud system, wherein the cloud system is connected to equipment via a network, and the computer program causes the computer to function as: a reception unit that receives identification information of the equipment; a connection relationship information acquisition unit that acquires connection relationship information of multiple resources related to the equipment and the cloud system based on the identification information; and a display control unit that displays the multiple resources on a screen in a manner that allows the order in which data passes to be recognized based on the connection relationship information.

Images