JP2023129154A - Remote operation system, timestamp correction method, and timestamp correction program - Google Patents

Abstract

To modify the time series of data in a time series DB that has multiple time stamps according to requirements.SOLUTION: A remote operation system that uses a computer to manage data obtained via a network from an infrastructure base that operates one or more infrastructure devices, includes a time-series DB that accumulates and maintains operational information in which a timestamp of the infrastructure base or the infrastructure device is given to data obtained from the infrastructure device, a time difference detection unit that calculates a difference between a timestamp obtained from the infrastructure base or the infrastructure device and a time stamp of a time synchronization server of an operation base owned by the remote operation system, and a timestamp correction unit that corrects the timestamp of the data in the acquisition range using the difference in accordance with a data acquisition request received from an application, which includes the time series and data acquisition range specified by the data of the infrastructure device used in the application when the timestamp and the difference of the data in the acquisition range acquired from the time series DB meet the predetermined conditions.SELECTED DRAWING: Figure 1

Description

The present invention relates to a remote operation system, a time stamp correction method, and a time stamp correction program.

The practical application of network virtualization and SDN (Software Defined Networking) has become widespread, and by utilizing these technologies, IT infrastructure that supports business operations can provide wide-area and detailed Items can be changed flexibly and quickly. On the other hand, IT infrastructure management items are becoming larger and more complex, and a large amount of management time is required not only for installation and initial settings, but also for continuous operation and operation. In recent years, there has been an increasing need to outsource tasks other than core operations, such as the management of IT infrastructure, and managed services that not only provide IT infrastructure environments to customers but also handle continuous operation and operation are attracting attention. ing.

Against this background, companies are also developing infrastructure for providing managed services. As a requirement for managed service providers who provide managed services, in order to centrally manage each customer's IT infrastructure, we must centrally manage data in various formats collected from different devices at each customer's IT infrastructure location. It is necessary to utilize it for operation. For this reason, the use of time-series databases is attracting attention because they use timestamps as the primary key, making it easier to confirm changes in the situation over time, and which can store data without worrying too much about the type of data other than timestamps.

Best practices for formatting data obtained from various sources and storing it in a time-series DB include Elasticsearch, which is a time-series DB, Logstash or Beats, which is a data collection tool, and Kibana, which visualizes data in a time-series DB. The ELK stack, which combines OSS (Open Source Software), is widely used and efficiently collects data from multiple locations by distributing data collection tools and time series databases. Additionally, the timestamp, which is the primary key of the data stored in the time series DB, is added when the data collection tool formats the data.

Japanese Patent Application Publication No. 2018-190216

When using a time series database, the reliability of the timestamps added to the data is important. The prior art describes a method of correcting time stamps by utilizing NTP (Network Time Protocol) time correction logs in order to increase the reliability of time stamps of data in a time series DB built into a control device.

However, in a managed service like this case, when a variety of data is collected from multiple customers' IT infrastructure bases and centrally managed using a time-series database, the time system of the managed service operation base and the customer's IT infrastructure base is different. This is not always the case, and even in the case of managed services, it is often impossible to match the time system of all devices at the customer's IT infrastructure base with the operation base as it would be a large-scale change. Additionally, IT infrastructure equipment whose time is not synchronized may be subject to operation. Assuming that the timestamp is assigned a data collection tool and that the data collection tool is operated at the customer's IT infrastructure site, the timestamp of the time series DB may contain the time systems of multiple customers' IT infrastructure sites. Become. When operating IT infrastructure, it is necessary not only to adjust the timestamp to the correct time, but also to adjust it according to the time system of the target when comparing alert times.

Accordingly, one aspect of the present invention aims to provide a technique that allows the time series of data in a time series DB to which time stamps of a plurality of time series are attached to be corrected according to requirements.

A remote operation system according to one aspect of the present invention is a remote operation system that uses a computer to manage data obtained via a network from an infrastructure base that operates one or more infrastructure devices, the system managing data obtained from the infrastructure device. a time-series DB that accumulates and holds operational information in which a time stamp of the infrastructure base or the infrastructure equipment is attached to the data obtained, a time stamp acquired from the infrastructure base or the infrastructure equipment, and the remote operation system. A time difference detection unit that calculates the difference between the time stamp and the time stamp of the time synchronization server of the operation base, and data received from the application that includes the specification of the time system and data acquisition range that the data of the infrastructure equipment used in the application follows. If the timestamp of the data in the acquisition range acquired from the time series DB and the difference satisfy a predetermined condition in accordance with the acquisition request, the timestamp of the data in the acquisition range is corrected using the difference. The system is configured as a remote operation system characterized by having a correction section.

According to one aspect of the present invention, it is possible to modify the time series of data in a time series DB to which time stamps of a plurality of time series are attached according to requirements.

system configuration diagram Sequence diagram of time difference recording Time difference retention table Sequence diagram of timestamp correction when acquiring time series DB data Flowchart of timestamp correction when acquiring time series DB data Sequence diagram of timestamp correction of individual acquired data Flowchart for correcting timestamps of individually acquired data Sequence diagram of time stamp correction information and data storage in time series DB Flowchart of timestamp correction when acquiring time-series DB data when the time-series DB has timestamp correction information System configuration diagram for creating time series DB sub-datasets Sequence diagram for creating subdataset of time series DB Sequence diagram for creating subdataset of time series DB System configuration diagram for setting requirements for each application GUI example for setting requirements for each application computer schematic diagram

Embodiments of the present invention will be described below with reference to the drawings. The following description and drawings are examples for explaining the present invention, and are omitted and simplified as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Unless specifically limited, each component may be singular or plural.

The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

In the following description, various information may be described using expressions such as "database," "table," and "list," but various information may be expressed using data structures other than these. "XX table", "XX list", etc. are sometimes referred to as "XX information" to indicate that they do not depend on the data structure. When describing identification information, when expressions such as "identification information", "identifier", "name", "ID", and "number" are used, they can be replaced with each other.

When there are multiple components having the same or similar functions, the same reference numerals may be given different suffixes for explanation. However, if there is no need to distinguish between these multiple components, the subscripts may be omitted in the description.

In addition, although the following explanation may explain processing performed by executing a program, a program is executed by a processor (for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit)), The processor may be the main body of the processing in order to perform the processing using appropriate storage resources (for example, memory) and/or interface devices (for example, communication ports). Similarly, the subject of processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The main body of processing performed by executing a program may be an arithmetic unit, and may include a dedicated circuit (for example, FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs specific processing. .

A program may be installed on a device, such as a computer, from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server includes a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Furthermore, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

In addition, the operational appliance, time adjustment appliance, operational application group, NTP server, etc. described in each of the following embodiments include, for example, a CPU 1601, a memory 1602, and an HDD (Hard Drive) as shown in FIG. 14 (computer schematic diagram). A reading device 1607 that reads and writes information to and from a portable storage medium 1608 such as a CD (Compact Disk) or USB memory, and an input device 1606 such as a scanner, keyboard, and mouse. , an output device 1605 such as a display, a communication device 1604 such as a NIC (Network Interface Card) for connecting to a communication network, and an internal communication line (referred to as a system bus) 1609 such as a system bus that connects these devices. It can be realized or stored in a general computer 1600.

Various data (for example, time series DB 111 of operation appliance 110, time difference recording unit 122 of time adjustment appliance 120, etc.) stored in the systems and devices shown in the following embodiments or used for processing is stored in memory by CPU 1601. This can be achieved by reading out and using the data from 1602 or external storage device 1603. In addition, each functional unit included in each system or device (for example, the base/device time difference detection unit 121 of the time adjustment appliance 120, the time stamp correction unit 123, the operation information acquisition unit 141 of the operation agent 140, the time difference detection unit 142, etc.) ) can be realized by the CPU 1601 loading a predetermined program stored in the external storage device 1603 into the memory 1602 and executing it.

The above-mentioned predetermined program is stored (downloaded) in the external storage device 1603 from the storage medium 1608 via the reading device 1607 or from the network via the communication device 1604, and then loaded onto the memory 1602. It may also be executed by the CPU 1601. Alternatively, the program may be directly loaded onto the memory 1602 from the storage medium 1608 via the reading device 1607 or from a network via the communication device 1604, and executed by the CPU 1601.

In the following, we will exemplify a case where the appliances, agents, etc. that make up this system are configured on one computer, but all or part of these functions may be distributed over one or more computers such as in the cloud. Similar functions may be realized by being provided with two devices and communicating with each other via a network.

In this example, the operation base collects information from each infrastructure device at a remote infrastructure base and stores it in a time series DB, and also acquires and records the time difference between the operation base and each infrastructure equipment at the infrastructure base. Then, when retrieving data from the time series DB, modify the timestamp according to the data usage requirements.

FIG. 1 is a diagram showing a configuration diagram of the first embodiment.

Embodiment 1 has one operation base 101, one or more infrastructure bases 102, and a management network 103 connecting them. As the management network 103, a network that safely connects locations, such as a VPN (Virtual Private Network) or a dedicated line, may be used.

In the operation base 101, an operation appliance 110, a time adjustment appliance 120, an operation application group 130, and an NTP server 124 are operating. Appliances are devices that virtually operate functions similar to HW devices on HW (Hardware) devices or server devices. In this way, a remote operation system including the operation appliance 110 and the time adjustment appliance 120 is connected to the infrastructure base 102 via the management network 103.

The operational appliance 110 has a time series DB 111, a message hub 112, and an operational dashboard 113.

The time adjustment appliance 120 includes a base/device time difference detection section 121, a time difference recording section 122, and a time stamp correction section 123.

The operational application group 130 includes one or more operational applications. In this embodiment, an NW (Network) usage fee measurement application 131, an alert information collection application 132, and a troubleshooting application 133 are shown as examples.

In the infrastructure base 102, an IT infrastructure 150, an operation agent 140, and an NTP server 143 are operating. As the IT infrastructure 150, a plurality of infrastructure devices 150 are operating.

The operation agent 140 includes an operation information acquisition section 141 and a time difference detection section 142.

First, the acquisition of operational information in this example will be described. At the infrastructure base 102, the operation information acquisition unit 141 of the operation agent 140 acquires operation information from the infrastructure devices 150-1, 150-2, etc. of the IT infrastructure 150, formats the data, and then sends it to the management network 103. The formatted data is sent to the message hub 112 via. The operation information acquisition unit 141 uses a data collection tool such as Logstash to acquire event and alert information necessary for operation from the infrastructure equipment 150 using protocols such as SNMP (Simple Network Management Protocol), syslog, and telnet. Then, the operational information acquisition unit 141 adds a timestamp according to the NTP server 143 of the infrastructure base 102, formats the acquired information into a type such as JSON (JavaScript Object Notification) that can be inserted into the time series DB 111, and sends it to the REST , AMQP, Kafka, and other message hubs support protocols. Message hub 112 receives the data and stores it in time series DB 111. The operation dashboard 113 displays operation information based on the contents of the time series DB 111. In this way, the operational information includes the above-mentioned event and alert information, and the time stamps associated with them. Furthermore, time stamps of a plurality of time systems (for example, the time system of the infrastructure base 102-1 and the time system of the infrastructure base 102-2) are assigned to the time series DB 111.

Next, acquisition of time difference information in this example will be described. At the infrastructure base 102, the time difference detection unit 142 of the operation agent 140 collects the device setting time from the infrastructure devices 150-1, 150-2, etc. of the IT infrastructure 150 and the base time from the NTP server 143, Via the management network 103, time information including the device setting time and the time at the base is sent to the base/apparatus time difference detection unit 121. The base/device time difference detection unit 121 receives the time information and acquires the time information of the operational base from the NTP server 124. The base/device time difference detection unit 121 calculates the time difference between the two and stores it in the time difference recording unit 122 as time difference information.

Finally, referring to information in the time series DB 111 from the operational application group 130 in this example will be described. In this example, the operational application group 130 includes a NW usage measurement application 131, an alert information collection application 132, and a troubleshooting application 133. All of these obtain operational information stored in the time-series DB 111 in order to report operational information or investigate the cause when a failure occurs. The timestamp correction unit 123 receives the request for information reference from the operational application group 130, refers to the information in the time difference recording unit 122, corrects the timestamp according to the requirements of the application, and assigns the corrected timestamp. It responds to the above request by, for example, transmitting the data.

FIG. 2 is a sequence diagram showing an example of acquiring and recording time difference information.

First, the time difference detection unit 142 of the infrastructure base 102 triggers the start of a time difference detection sequence. As a trigger, various examples can be considered, such as every fixed time like NTP time correction, etc., when the start time of a report for application requirements is reached, or immediately before maintenance when many operational events are expected to occur. (201)

Next, the time difference detection unit 142 obtains the device setting time from each infrastructure device 150-1, 150-2, . . . of the IT infrastructure 150 (202).

Next, the time difference detection unit 142 obtains the time of the infrastructure base 102 from the NTP server 143 (203).

Next, the time difference detection unit 142 sends the equipment setting time acquired in step 202 and the time of the infrastructure base 102 acquired in step 203 to the base/device time difference detection unit 121 of the operation base 101. Send as time information (204).

Next, the base/device time difference detection unit 121 obtains the time of the operational base 101 from the NTP server 124 as the time information of the operational base (205).

Finally, the base/device time difference detection unit 121 calculates the time difference 306 between the operation base 101, the infrastructure base 102, and each infrastructure device 150 from the time information acquired in steps 202, 203, and 205, and It is stored as information in the time difference recording unit 122 (206).

FIG. 3 is an example of recording time differences.

The data recorded in the time difference recording unit 122 is managed in a table format, and holds columns of operation base time 301, infrastructure base 302, device ID 303, device setting time 304, infrastructure base time 305, and time difference 306.

In this example, the base/device time difference detection unit 121 calculates and records the difference between the operational base time 301 and the infrastructure base time 305 as the time difference 306, but if the infrastructure base time 305 cannot be obtained due to lack of NTP, etc. calculates the time difference 306 using the device setting time 304 instead.

Each line 311-314... shows the acquisition information of the time difference from each infrastructure device 150 of each infrastructure base 102. Lines 311 and 312 show an example in which the infrastructure equipment 150 is synchronized with the NTP server 143, and the time is roughly synchronized. For example, in line 311, the time difference between "2021/08/31 09:00:00.111" which is the operation base time 301 and "2021/08/31 09:00:01.500" which is the infrastructure base time 305 306 is "+0.1389", indicating that both times are approximately synchronized.

Furthermore, rows 313 and 314 show an example in which the infrastructure base 102 does not have the NTP server 143 and the device setting time 304 of the infrastructure device 150 is shifted by a minute. For example, in line 313, the time difference between "2021/08/31 09:30:00.122" which is the operation base time 301 and "2021/08/31 09:40:00.222" which is the device setting time 304 306 is "+10:00.100", indicating that the two times are not synchronized.

Note that even if it is time difference information with the same infrastructure equipment 150, it is assumed that the time difference changes depending on the calculation timing, so old information is not deleted immediately but is continuously retained.

FIG. 4 is a sequence diagram showing an example of correcting timestamps when acquiring time-series DB data.

First, the operational application group 130 issues a data acquisition query to the time stamp correction unit 123 (401).

Next, the timestamp correction unit 123 acquires data including operational information from the time series DB 111 (402), acquires time difference information including the time difference 306 from the time difference recording unit 122 (403), and The stamp is corrected (404) and the data with the corrected timestamp is returned (405).

FIG. 5 is an example of a flowchart of the time stamp correction unit 123 (step 404) shown in the example of FIG.

First, the time stamp correction unit 123 receives a data acquisition query for the time series DB 111 from the operational application group 130. This example shows a retrieval query using REST, and the query specifies the infrastructure site with the URL path, the device name and time with the "query" key, and the time system that the data follows with the "term" key (in this example, This indicates that the conditions are "monitoring_base" representing the operation base 101), the required accuracy ("0.1sec" in this example), and the correction method ("replace" that replaces the timestamp in this example) (501). Note that in step 501, "gt" represents "Greater than" and "lt" represents "Less than". Furthermore, "10d" and "9d" represent "10days" and "9days", respectively, and in this example, indicate that the query is to obtain data for one day from 10 days ago to the present.

Next, the timestamp correction unit 123 acquires data from the time series DB 111 according to the contents of the "query" key of the query received in step 501 (502). For example, the timestamp correction unit 123 may write information such as {“timestamp”:“2021/09/10 10:10:10.001”} indicating a timestamp included in the operational information stored in the time-series DB 111, an event at that time, etc. Get “info”:{......}} indicating alert information. Such data is acquired for one day from 10 days ago to the present. It is assumed that the data in this example includes, for example, "infrabase_1_equipment_1" representing the infrastructure equipment 150-1 of the infrastructure base 102-1 as a time system to which the data follows.

Next, the timestamp correction unit 123 determines whether the query received in step 501 is not a query that responds by collecting data for a certain period of time, or whether the period of data collection is shorter than the precision required by the query (503 ). This is because the time series DB 111 is not necessarily used to respond with individual data one by one. For example, for visualization purposes, calculate a summary such as the number of data, average value, and median value for data including multiple events and alert information acquired every hour, and then use the results as an answer to a query. There are cases. In such a case, if the data is to be responded to in a batch and if the summary period is longer than the required accuracy, it can be determined that there is no need to correct the timestamp.

That is, in step 503, if the query received in step 501 requests that the operational appliance 110 respond with data from the time series DB 111 for a certain period of time (if condition A is satisfied), or if the operational appliance 110 compiles the data of the time series DB 111, and if the period is not shorter than the precision requested by the above query (if condition B is satisfied), the timestamp correction unit 123 needs to correct the timestamp. It is determined that there is not, and the process proceeds to step 506 (503; YES).

On the other hand, if the query received in step 501 does not satisfy the above condition A or does not satisfy the above condition B, the timestamp correction unit 123 determines that it is necessary to correct the timestamp, and proceeds to step 504. (503;NO). The above conditions A and B are specified within the query as in steps 501 and 502.

Next, the timestamp correction unit 123 acquires, from the time difference recording unit 122, time difference information including the time difference 306 around the time of the timestamp that satisfies the conditions specified in the query, from among the data acquired in step 502. Do (504). In this example, according to the query received in step 501, the time difference 306 between the operation base 101 and the infrastructure base 102 is acquired. Here, it is shown that the time difference information “{“2021/09/10AM”:{“equipment_1”:”+1.1000s”}}” has been acquired. If multiple time differences are recorded around the relevant time, the average value or intermediate value is calculated to calculate the most probable time difference. Also, in this example, the time difference is obtained in JSON format, but the data type of the response is not limited to that.

Next, the timestamp correction unit 123 determines whether the time series of the timestamp included in the data acquired in step 502 (in this example, the infrastructure device 150-1 of the infrastructure base 102-1) is presented in the query in step 501. Check whether the timestamp included in the data obtained in step 502 has been corrected by determining whether the time difference is greater than the required accuracy. Do (505).

For example, if the operation agent 140 follows the NTP server 124 of the operation base 101 via the management network 103, the timestamp correction unit 123 may have assigned a time stamp based on the time of the operation base 101 from the beginning. There is sex. For example, the timestamp correction unit 123 reads information such as information "infrabase_1" (identification information of the infrastructure base 102) related to the time system to be followed, which is recorded in the data acquired in step 502. The timestamp correction unit 123 determines whether the read information regarding the time system to follow differs from the information regarding the time system to follow specified in the query received in step 501 (for example, "monitoring_base" representing the operation base 101). If it is determined that the two are different, the difference between the time stamp of the data obtained in step 502 above and the time of the NTP server 124 of the operation base 101, that is, the time of the operation base 101 and the infrastructure base 102, is determined. Verify that the difference 306 is greater than the requested accuracy specified in the query received in step 501. Note that in the above example, since the two do not match, the process proceeds to step 507.

That is, in step 505, the timestamp correction unit 123 uses ), and if the condition C is satisfied, and if the condition that the time difference 306 between the operation base 101 and the infrastructure base 102 is greater than the required accuracy specified in the query received in step 501 (condition D is satisfied) ), proceed to step 507 (505; YES). On the other hand, in step 505, if neither the above condition C nor the above condition D is satisfied, the time stamp correction unit 123 determines that there is no need to perform time stamp correction, and proceeds to step 506 (505; NO).

Subsequently, if the timestamp modification unit 123 determines that the timestamp needs to be modified in step 505, it modifies the timestamp according to the modification method specified in the query received in step 501, and updates the modified timestamp. The assigned data is returned to the operational application group 130 (507).

In this example, since the modification method specified in the query received in step 501 is "replace", the timestamp modification unit 123, for example, indicates the timestamp of the data acquired in step 502 {"timestamp":" 2021/09/10 10:10:10.001”} shows the time difference 306 between the operation base 101 and infrastructure base 102 obtained in step 504 {“2021/09/10AM”:{ “equipment_1”:”+1.1000 Calculate the corrected timestamp {“timestamp” : “2021/09/10 10:10:11.101” } with “s”}}” added. Then, the time stamp correction unit 123 transmits the data having the corrected time stamp obtained by the above calculation to the operational application group 130.

In this example, the timestamp is replaced, but other modifications can be made such as writing the timestamp before and after the correction using different key names, or adding an offset using a different key. Methods are also envisaged.

If the time stamp correction unit 123 determines that there is no need to correct the time stamp, it returns the data obtained in step 502 as is to the operational application group 130 (506).

In this embodiment, not only the data in the time series DB 111, but also the time stamps of information such as logs individually acquired by the operational application group 130 from the infrastructure equipment 150 of each infrastructure base 102 are corrected to a different time system.

FIG. 6 is a sequence diagram of an example of correcting time stamps of individually acquired data.

First, the operational application group 130 individually obtains information such as time-stamped logs from the infrastructure equipment 150 (601). In this example, the operational application group 130 obtains "2021/09/11 20:20:10.002 "info..." from the infrastructure device 150, for example, as information such as the above log.

The reason why the operational application group 130 directly acquires information such as logs from the infrastructure device 150 is as follows. That is, the information stored in the time series DB 111 is acquired by the operation information acquisition unit 141 of the operation agent 140. The operation information acquisition unit 141 does not send all information in consideration of the load on the infrastructure equipment 150 and the capacity of the time series DB 111, but basically only sends information that has a high priority in operation. However, since other detailed information is also required when dealing with failures or maintenance, the operation information acquisition unit 141 acquires information individually depending on the case.

Next, the operational application group 130 sends a time stamp modification request to the time stamp modification unit 123 (602). The time stamp of the information acquired in step 601 is given at the device setting time of the infrastructure device 150. However, for example, when comparing log information obtained from other infrastructure devices 150-n or verifying the order relationship with nearby events at the operation base 101, it is necessary to correct the time system. Therefore, the operating application group 130 transmits the above modification request to the time stamp modification unit 123.

Next, the time stamp correction unit 123 acquires time difference information from the time difference recording unit 122 (603), corrects the time stamp (604), and transmits the data with the corrected time stamp attached. and replies with the corrected timestamp (605).

FIG. 7 is an example of a flowchart of the time stamp correction unit 123 (step 602) shown in the example of FIG.

First, the timestamp modification unit 123 receives a timestamp modification request from the operating application group 130 (701). This example shows a modification request using REST, where the URL path is the timestamp modification request, the "term" key is the original time system (the time system of the information obtained in step 601; in this example, "equipment_1_1"), It shows the time system to follow after correction (in this example, “monitoring_base” representing the operation base 101) and the required accuracy (in this example, “0.1sec”). Also, specify the timestamp to be modified using the "timestamp" key. In this example, the timestamp modification unit 123 issues the timestamp modification request, including "2021/09/11 20:20:10.002" indicating the timestamp included in the information such as the log acquired in step 601, for example. receive.

Next, similarly to step 504, the time stamp correction unit 123 acquires time difference information including the time difference 306 around the time of the time stamp for which the correction request was received in step 701 from the time difference recording unit 122 (702 ). In this example, in accordance with the time stamp correction request received in step 701, the time difference 306 corresponding to a time within a predetermined range (for example, 5 minutes) including the time indicated by the time stamp included in the information such as the log is calculated. , obtained from the time difference recording unit 122. This example shows that the time stamp correction unit 123 has acquired “{“2021/09/11PM”:{“equipment_1”:”+2.1000s”}}” as the time difference 306.

Next, the timestamp correction unit 123 determines whether or not the time stamp needs to be corrected by determining whether or not the time difference obtained in step 702 is greater than the requested accuracy of the correction request received in step 701. Judgment (703). In other words, if the time stamp correction unit 123 determines that the time difference obtained in step 702 is larger than the required accuracy of the correction request received in step 701, the required accuracy is not met and correction is necessary. It is determined that this is the case, and the process proceeds to step 704 (703; YES). On the other hand, if the time stamp correction unit 123 determines that the time difference obtained in step 702 is not larger than the required accuracy of the correction request received in step 701, the required accuracy is satisfied and no correction is necessary. It is determined that there is, and the process proceeds to step 705 (703; NO).

Next, if the timestamp correction unit 123 determines that the timestamp needs to be corrected, the timestamp correction unit 123 corrects the timestamp so as to satisfy the correction request received in step 701, and the data to which the corrected timestamp has been added is is replied to the operational application group 130 (704).

In this example, the timestamp correction unit 123 applies the time difference obtained in step 702 to the timestamp "2021/09/11 20:20:10.002" included in the correction request received in step 701, for example. Add “{“2021/09/11PM”:{ “equipment_1”:”+2.1000s”}}” to calculate the corrected timestamp ““2021/09/11 20:20:12.102””. Then, the time stamp correction unit 123 transmits the data having the corrected time stamp obtained by the above calculation to the operational application group 130. Note that in this example, only the corrected timestamp is returned, but it is also possible to write the timestamps before and after the correction, or to add information such as the number of rows to make the process easier to handle.

On the other hand, if the timestamp correction unit 123 determines that the timestamp does not need to be corrected, it replies to the operation application group 130 to that effect (705).

In this embodiment, when the operation information acquisition unit 141 creates the operation information data to be stored in the time series DB 111, it also writes the timestamp of the operation base so that the time difference can be traced later, and stores it in the time series DB 111. Give an example. This example assumes that the data acquisition tool of the operational information acquisition unit 141 can be modified. In addition, all data stored in the time series DB 111 is accompanied by the timestamp of the operation base, and if there is no large blank time exceeding a predetermined threshold for the data, the data stored in the time series DB 111 is It is also possible to modify the time stamps shown in the first and second embodiments. However, accessing the time series DB 111 does not necessarily result in acquiring all data one by one. In addition, access to retrieve data summarized in the time direction is mainstream, and having to retrieve many data items one by one in parallel every time the timestamp is corrected increases the access load to the time series DB111. is likely to double. Therefore, when correcting the time stamp, it is determined whether to use the time difference recording unit 122 or the data in the time series DB 111 depending on the requirements.

FIG. 8 is a sequence diagram showing an example in which when the operation information acquisition unit 141 stores data in the time series DB 111, the time stamp of the operation base is also written and saved.

First, the operational information acquisition unit 141 collects operational information from the infrastructure equipment 150 (801). This information acquisition method is the same as in the first embodiment.

Next, the operation information acquisition unit 141 acquires time information of the operation base 101 via the time difference detection unit 142 (802).

Next, the operation information acquisition unit 141 formats the data in the same manner as in the first embodiment, and also records the time information of the operation base 101 acquired in step 802 (803), and sends the data in chronological order via the message hub 112. Send data to DB111 (804). Here, the operation information acquisition unit 141 acquires “{“timestamp” : “2021/09/20 15:01:10.001”,“info”:{…” included in the operation information acquired from the infrastructure equipment 150 of the infrastructure base 102. …}}” is added with the im-stamp ““monitorzone_timestamp”: “2021/09/20 15:01:09.501”” of the operation base 101 included in the time information obtained from the NTP server 124 of the operation base 101. 804a, “{“timestamp”:“2021/09/20 15:11:11.111”“info”:{......}” included in the time information obtained from the NTP server 124 of the operation base 101 It shows that data 804b with the im-stamp “monitorzone_timestamp” : “2021/09/20 15:01:10.611”} of operation base 101 added is being sent. In this example, the infrastructure equipment 150 of the infrastructure base 102 includes time stamps for multiple infrastructure bases and infrastructure equipment, including the infrastructure equipment of the infrastructure base 102-1 and the infrastructure equipment of the infrastructure base 102-2. .

Note that "info":{...}" is event or alert information of the infrastructure base, as in the first embodiment. In this embodiment, since the time information of the operational base 101 is associated with each event and alert information of the infrastructure base, time differences can be grasped in units of events and alerts.

Figure 9 shows that when the data stored in the time-series DB 111 includes not only the timestamp of the infrastructure base 102 but also the timestamp of the operation base 101, the timestamp of the data in the time-series DB 111 is added to the application requirements. This is an example of a flowchart that is modified according to the following. This process is performed by the time stamp correction unit 123, but since many parts are the same as those in FIG. 5 of the first embodiment, the explanation will focus on the differences.

Steps 901 to 903 are partially similar to steps 501 to 503 in FIG.

That is, the time stamp correction unit 123 receives a data acquisition query for the time series DB 111 from the operational application group 130 (901). This example shows a REST acquisition query, where the URL path specifies the infrastructure site, and the "query" key specifies the device name and time (in this example, it indicates the infrastructure device at infrastructure site 102-1). infrabase_1_equipment_1” and the time from the current moment to 10 days ago {“gt”:”now-10d”,“lt”:”now”}, the time system that the data follows with the “term” key (in this example, the time system for infrastructure base 102-2) This indicates that the conditions are the infrastructure equipment "infrabase_2_equipment_2"), the required accuracy (in this example, "0.001sec"), and the modification method (in this example, "replace", which indicates replacing the timestamp).In other words, the step The query received at 901 is a query requesting to replace the timestamp of the infrastructure equipment of infrastructure base 102-1 from now until 10 days ago with the timestamp of the infrastructure equipment of infrastructure base 102-2 with an accuracy of 0.001 seconds. It shows that there is.

Next, the timestamp correction unit 123 acquires data from the time series DB 111 according to the contents of the "query" key of the query received in step 901 (902). For example, the timestamp correction unit 123 corrects the timestamp “2021/09/20 15:01:09.501” of the operation base 101 included in the operation information sent in step 804 of FIG. 8 and stored in the time series DB 111. Timestamp “timestamp” of infrastructure base 102-1 “infrabase_1_equipment_1”: “2021/09/20 15:01:10.001” and “info” showing event and alert information at that time: {......}} get.

Then, the timestamp correction unit 123 receives the data acquisition query of the time series DB 111, and as in the case of the first embodiment, the query received in step 901 causes the operation appliance 110 to aggregate the data of the time series DB 111 for a certain period of time. If the content requests a response (condition A is satisfied), or if the operational appliance 110 is compiling data from the time series DB 111, and the period is not shorter than the precision requested by the above query. (If condition B is satisfied), the time stamp modification unit 123 determines that there is no need to modify the time stamp, and proceeds to step 909 (903; YES). On the other hand, if the query received in step 901 does not satisfy the above condition A or does not satisfy the above condition B, the timestamp correction unit 123 determines that it is necessary to correct the timestamp, and proceeds to step 904. (903;NO).

Next, the timestamp modification unit 123 updates the timestamp of the infrastructure equipment of the infrastructure base 102-2, which is the time system specified for modification (for example, “infrabase_2_equipment_2”, “timestamp”: “2021/09/20 14:30:05.000 ”) and the time-based timestamp of the operation base (for example, “monitorzone_timestamp”: “2021/09/20 14:30:07.001”), which is somewhat close to the timestamp of the data obtained in step 902. Obtain time event data from the time series DB 111 (904).

Further, the time stamp correction unit 123 determines whether the time stamp of the data acquired in step 902 and the data acquired in step 904 are separated by a certain amount or more (905). In this example, the timestamp correction unit 123 uses the timestamp of the infrastructure equipment “infrabase_1_equipment_1” of the infrastructure base 102-1 acquired in step 902 and the timestamp of the infrastructure equipment “infrabase_2_equipment_2” of the infrastructure base 102-2 acquired in step 904. It is determined whether there is a gap of a certain amount of time or more.

If the time stamp correction unit 123 determines that the time stamp of the data obtained in step 902 and the data obtained in step 904 are not separated by a certain amount or more (905; YES), the time stamp correction unit 123 corrects Determine that it is possible to modify the timestamp. Then, in accordance with the query request received in step 901, the timestamp correction unit 123 updates the timestamp of the infrastructure equipment of the infrastructure base 102-1 acquired in step 902 with the infrastructure equipment of the infrastructure base 102-2 acquired in step 904. It responds to the above request by correcting the timestamp and sending data with the corrected timestamp (906).

On the other hand, if the time stamp correction unit 123 determines that the time stamp of the data acquired in step 902 and the data acquired in step 904 are separated by a certain amount or more (905; NO), the time stamp correction unit 123 It is determined that it is not possible to modify the timestamp. Then, the time stamp correction unit 123 uses the time stamp of the infrastructure equipment infrabase_2_equipment_2 of the infrastructure base 102-2, which is the time series specified to be corrected in the query received in step 901, from the time difference recording unit 122, and the time stamp of the infrastructure equipment infrabase_2_equipment_2 of the infrastructure base 102-2, Obtain the time difference around the time of the time-based timestamp of the obtained operation base. For example, the time stamp correction unit 123 obtains {“2021/09/20 PM”:{“equipment_1”:”-2.000s”}} calculated by the time difference recording unit 122 (907).

Then, the timestamp correction unit 123 adds the difference obtained in step 907 to the timestamp of the infrastructure equipment of the infrastructure base 102-1 obtained in step 902, and adds the time stamp to the timestamp of the infrastructure equipment of the infrastructure base 102-2. It responds to the above request by, for example, transmitting data with the deemed timestamp (908).

Note that if the timestamp correction unit 123 determines that there is no need to correct the timestamp (903; YES), it returns the data acquired in step 902 as is to the operational application group 130, as in the first embodiment ( 909).

With this sequence, the reference data is not retrieved from the time series DB 111 every time the timestamp is modified, but the reference data is retrieved only when necessary, reducing the access load to the time series DB 111 while modifying the timestamp. becomes possible.

In Examples 1 to 3, timestamps were corrected when acquiring data from the time series DB 111. However, in terms of data management, rather than always accessing a DB that centrally manages all data, it is necessary to create sub-datasets by selecting frequently accessed data and making necessary modifications in advance. Effective for dispersion. An ETL (Extract, Transfer, Load) tool is often used as a tool to create a sub-dataset, and in this example, it is assumed that necessary timestamp changes will be made when converting to a sub-dataset. In addition, in data management, a component that centrally manages all data, such as a time series DB111, is called a "data lake," and a formatted component that is set aside for easy reference, such as a sub-dataset, is called a "data warehouse" or "data warehouse." Sometimes called ``mart''.

FIG. 10 is a system configuration diagram when creating a sub data set from the time series DB 111. The difference from the system configuration diagram of the first embodiment shown in FIG. 1 is that the operational appliance additionally includes a sub-data time series DB 1001 and a sub-data set forming unit 1002. The time adjustment appliance 120 may be provided with a base/device time difference detection unit 121.

11A and 11B are sequence diagrams of an example of creating a sub data set from the time series DB 111.

First, in FIG. 11A, the sub-data set forming unit 1002 applies a trigger to start adding sub-data sets (1101). Various conditions can be assumed as the trigger, such as every certain time or after a certain number of data are added to the time series DB 111.

Next, the sub-data set forming unit 1002 acquires original data for the sub-data set from the time series DB 111 (1102). This acquisition method is similar to, for example, the procedure of step 502 in FIG. 5 in the first embodiment.

Next, the sub-data set forming unit 1002 obtains time difference information around the time stamp of the sub-data set to be added from the time difference recording unit 122 in order to correct the time stamp (1103). This acquisition method is, for example, similar to the procedure of step 504 in FIG. 5 in the first embodiment.

Next, the sub-data set forming unit 1002 formats the sub-data set (1104). This formatting is similar to, for example, the formatting method in step 507 of FIG. 5 in the first embodiment, and data is added or replaced depending on the assumed application requirements. Thereafter, the sub-data set forming unit 1002 adds the sub-data set to the sub-data time series DB 1101. In this example, the data is edited in such a way that the time stamp of the operation base is also written as the sub-data set (1105).

In FIG. 11A, a case is illustrated in which data is stored in the time series DB 111 without the time stamp of the operation base as in the case of Example 1 and Example 2, but Example 3 shown in FIG. 11B The same can be considered in the case where data with a time stamp of the operation base is stored in the time series DB 111, as in the case of .

First, in FIG. 11B, the sub-data set forming unit 1002 applies a trigger to start adding sub-data sets (1101). As with the case of FIG. 11A, various conditions are assumed as the trigger, such as every certain time or after a certain number of data are added to the time series DB 111.

Next, the sub-data set forming unit 1002 acquires original data for the sub-data set from the time series DB 111 (1102b). This acquisition method is similar to, for example, the procedure of step 902 in FIG. 9 in the third embodiment. In FIG. 11B, unlike in FIG. 11A, in step 1102b, for example, the timestamp “2021/09/20 15:01:09.501” of the operation base 101 included in the operation information stored in the time series DB 111 and the infrastructure base 102 -1 The timestamp “timestamp”: “2021/09/20 15:01:10.001” of “infrabase_1_equipment_1” and “info”:{......}} indicating event and alert information at that time are obtained. ing.

Next, the sub-data set forming unit 1002 obtains time difference information around the time stamp of the sub-data set to be added from the time difference recording unit 122 in order to correct the time stamp (1103b). This acquisition method is, for example, similar to the procedure of step 907 in FIG. 9 in the third embodiment.

Next, the sub-data set forming unit 1002 formats the sub-data set (1104b). This formatting is similar to, for example, the formatting method in step 908 of FIG. 9 in the third embodiment, and data is added or replaced depending on the assumed application requirements. Thereafter, the sub-data set forming unit 1002 adds the sub-data set to the sub-data time series DB 1101. In this example, in addition to the timestamp of the operation base, the data is edited to include the timestamp of the infrastructure base 102-2 as a sub-data set (1105b).

Create a subdataset as described above. Of course, there is not just one sub-dataset, and individual sub-datasets may be created according to the requirements of the application. In addition, it is possible to create a dataset that compiles necessary parts of data from multiple infrastructure devices 150 and multiple infrastructure locations 102, unifies time stamps, and visualizes the main chronological order in a unified manner, depending on the purpose. It is expected that the way data is used will also change.

In Examples 1 to 4, the time adjustment appliance 120 operated as a black box function, but the time adjustment appliance 120 may be separated from the operation appliance 110 so that it can operate in combination with the operation appliance 110 and the operation application group 130. is assumed. In this embodiment, the time stamp adjustment requirements for each application are set in advance using the setting GUI of the time adjustment appliance 120 for this purpose, thereby enabling flexible cooperation with the applications.

FIG. 12 is a system configuration diagram when setting requirements for time stamp adjustment for each application in the time adjustment appliance. As a difference from the first embodiment, the time adjustment appliance 120 includes a per-application requirement setting section 1202 and a per-application requirement recording section 1203. Furthermore, it includes a setting GUI 1201 for setting the requirements setting section 1202 for each application.

FIG. 13 is an example of a GUI for setting requirements for time stamp adjustment for each application in the time adjustment appliance.

For example, the per-application requirements setting unit 1202 holds these data in a table format that includes rows of application name 1301, application specifications 1302, time to match 1303, required accuracy 1304, correction method 1305, and other items 1306. . For example, the per-app requirement setting unit 1202 receives an operation from the user via the input device 1606 and sets items in each line, and then receives a press of the enter button 1321 to reflect the settings of each item, The information is displayed on output device 1605. The per-application requirement setting unit 1202 records the set items as they are in the per-application requirement recording unit 1203 (table such as a database). As explained in step 501, step 901, etc., when the time stamp correction unit 123 receives a data acquisition query for the time series DB 111 from the operational application group 130, the time stamp correction unit 123 converts the application name 1301 and application specifications included in the query. An application is selected with reference to 1302, and time stamp correction requirements similar to those in the first embodiment are generated with reference to the time system to be matched 1303, required accuracy 1304, and correction method 1305.

As explained above, according to this system, for example, an IT infrastructure remote operation system that connects and operates remote IT infrastructure via a management network such as VPN, and operation information that utilizes a time-series DB (Database) are available. When managing multiple time systems, record the time difference between each infrastructure site or device and the operation site, and correct it using the recorded time difference information when outputting data. In a time-series DB that contains a mixture of timestamps, data can be referenced smoothly according to the purpose of data use.

For example, as explained in Example 1, in this system, one or more infrastructure devices (e.g., infrastructure devices 150-1, 150-2) are operated by a computer. In a remote operation system that manages data obtained from an infrastructure base (for example, infrastructure base 102) via a network, the data (for example, event or alert information) acquired from the infrastructure equipment is A time-series DB that accumulates and retains operational information with device timestamps (for example, a DB that retains data in the format described in step 502 in Figure 5), and a a time difference detection unit (for example, base/device time difference detection unit 121) that calculates the difference between a time stamp and a time stamp of a time synchronization server (for example, NTP server 124) of an operation base of the remote operation system; The time system (for example, the time system specified in step 501 of FIG. "monitoring_base") and data acquisition range (for example, "timestamp":{"gt":"now-10d", "lt":"now"} specified in step 501 of Figure 5). In accordance with a data acquisition request (for example, the data acquisition query in step 501 above), the timestamp and the difference of the data in the acquisition range acquired from the time series DB meet a predetermined condition (for example, the data acquisition query in step 505 in FIG. 5). If conditions C and D) are satisfied, the time stamp correction unit (for example, the time stamp correction unit 123) corrects the time stamp of the data in the acquisition range using the difference. Therefore, it is possible to modify the time series of data in a time series DB to which time stamps of multiple time series have been added according to requirements requested by an application or the like.

Further, as described in the second embodiment, the infrastructure equipment outputs the data with a time stamp (for example, the log information shown in step 601 of FIG. 6), and the time stamp correction unit outputs the data with a time stamp attached. The data with the time stamp attached thereto is acquired from the infrastructure equipment, and the time stamp included in the acquired data is corrected using the difference. Therefore, without using time-series DB data, the operation application group 130 can modify the timestamp to a different time system using information such as logs individually obtained from the infrastructure devices 150 of each infrastructure base 102. .

Further, as explained in the third embodiment, the timestamp correction unit has a standard for correcting the timestamp of the infrastructure equipment used in the application (for example, the timestamp of "infrabase_1_equipment_1" shown in step 901 of FIG. 9). If the above data acquisition request including the infrastructure equipment that outputs a timestamp (for example, the timestamp of "infrabase_2_equipment_2" shown in step 901 of FIG. 9) is received, and the above predetermined conditions are met, from the above time series DB, If data including the timestamp of the infrastructure device that outputs the reference timestamp and the timestamp of the time synchronization server is obtained, and there is no difference of more than a certain amount of time between the two timestamps (for example, step If YES in step 905), as explained in step 906 of FIG. 9, the time stamp of the infrastructure equipment used in the application is corrected to the reference time stamp. Therefore, it is possible to correct time stamps between infrastructure sites and between infrastructure devices while maintaining a certain level of accuracy.

Furthermore, if there is a gap between the two time stamps by a certain amount of time or more (for example, if NO in step 905 of FIG. 9), the time stamp correction unit changes the time stamp of the infrastructure equipment used in the application to the time stamp of the infrastructure equipment used in the application. The correction is made using the difference between the reference time stamp and the time stamp of the time synchronization server of the operation base (for example, the time difference calculated in step 907). Therefore, even if it is not possible to correct timestamps between infrastructure sites or between infrastructure devices, timestamps can be corrected using the time synchronization server of the operational site while maintaining a certain level of accuracy.

The infrastructure base also stores data that associates the timestamp of the infrastructure equipment used in the application with the timestamp of the time synchronization server (for example, data 804a in step 804 shown in FIG. 8) and the standards. Operational information that writes data (for example, data 804b in step 804 shown in FIG. 8) that associates the timestamp of the infrastructure device that outputs the timestamp with the timestamp of the time synchronization server to the time series DB. It has an acquisition unit (eg, operational information acquisition unit 141). Therefore, it becomes possible to understand time differences in units of events and alerts.

The present invention is not limited to the above-described embodiments as they are, and in the implementation stage, the components may be modified and embodied without departing from the gist thereof, or multiple components disclosed in the above-described embodiments may be embodied. These can be implemented in appropriate combinations.

101 Operation base
102 Infrastructure base
103 Management Network
110 Operational Appliance
111 Time series DB
112 Message Hub
113 Operations Dashboard
120 Time Adjustment Appliance
121 Base/device time difference detection unit
122 Time difference recording section
123 Timestamp correction section
124 NTP server
130 Operational applications
131 NW usage fee measurement app
132 Alert information collection app
133 Troubleshooting app
140 Operation Agent
141 Operational Information Acquisition Department
142 Time difference detection section
143 NTP server
150 IT infrastructure
150-1, 150-2 Infrastructure equipment

Claims (11)

A remote operation system that uses a computer to manage data obtained via a network from an infrastructure base that operates one or more infrastructure devices,
a time-series DB that accumulates and holds operational information in which a time stamp of the infrastructure base or the infrastructure device is added to the data acquired from the infrastructure device;
a time difference detection unit that calculates a difference between a time stamp acquired from the infrastructure base or the infrastructure device and a time stamp of a time synchronization server of the operation base of the remote operation system;
In accordance with a data acquisition request received from an application that includes the time series and data acquisition range specified by the data of the infrastructure equipment used in the application, the timestamp and the difference of the data in the acquisition range acquired from the time series DB. a timestamp modification unit that modifies the timestamp of the data in the acquisition range using the difference if the data satisfies a predetermined condition;
A remote operation system characterized by having. The remote operation system according to claim 1,
the infrastructure equipment outputs the data with a time stamp;
The time stamp correction unit obtains the data with the time stamp attached from the infrastructure equipment, and corrects the time stamp included in the obtained data using the difference.
A remote operation system characterized by: The remote operation system according to claim 1,
The time stamp correction unit receives the data acquisition request including the infrastructure equipment that outputs a time stamp that is a reference for correcting the time stamp of the infrastructure equipment used in the application, and if the predetermined condition is met, the time stamp correction unit Obtain data including the timestamp of the infrastructure device that outputs the reference timestamp and the timestamp of the time synchronization server from the DB, and if the two timestamps do not differ by more than a certain amount of time, the application correcting the timestamp of the infrastructure equipment to be used to the reference timestamp;
A remote operation system characterized by: The remote operation system according to claim 3,
If there is a difference between the two timestamps by a certain amount of time or more, the timestamp correction unit converts the timestamp of the infrastructure equipment used in the application into the reference timestamp and the time of the time synchronization server of the operation base. Correct using the difference with the stamp,
A remote operation system characterized by: The remote operation system according to claim 3,
The infrastructure base includes data that associates a time stamp of the infrastructure device used in the application with a time stamp of the time synchronization server, and a time stamp of the infrastructure device that outputs the reference time stamp and the time synchronization server. an operational information acquisition unit that writes data associated with a timestamp to the time series DB;
A remote operation system characterized by having. A timestamp correction method performed in a remote operation system that manages data obtained via a network from an infrastructure base that operates one or more infrastructure devices using a computer, the method comprising:
a time difference detection unit calculates a difference between a time stamp acquired from the infrastructure base or the infrastructure device and a time stamp of a time synchronization server of the operation base owned by the remote operation system;
The timestamp modification unit adds the infrastructure base to the data acquired from the infrastructure device in accordance with the data acquisition request received from the application and including the time series and data acquisition range that the data of the infrastructure device used in the application follows. Or, if the time stamp of the data in the acquisition range acquired from a time-series DB that accumulates and holds operational information with time stamps of the infrastructure equipment and the difference satisfies a predetermined condition, the data in the acquisition range correcting the timestamp of using the difference,
A timestamp correction method characterized by: 7. The time stamp correction method according to claim 6,
the infrastructure equipment outputs the time-stamped data;
the time stamp correction unit obtains the data with the time stamp attached from the infrastructure equipment, and corrects the time stamp included in the obtained data using the difference;
A timestamp correction method characterized by: 7. The time stamp correction method according to claim 6,
The time stamp correction unit receives the data acquisition request including the infrastructure equipment that outputs a time stamp that is a reference for correcting the time stamp of the infrastructure equipment used in the application, and if the predetermined condition is satisfied, the time series Obtain data including the timestamp of the infrastructure device that outputs the reference timestamp and the timestamp of the time synchronization server from the DB, and if the two timestamps do not differ by more than a certain amount of time, the application correcting the timestamp of the infrastructure equipment to be used to the reference timestamp;
A timestamp correction method characterized by: The time stamp correction method according to claim 8, comprising:
If the time stamps between the two timestamps differ by a certain amount of time or more, the timestamp correction unit changes the timestamp of the infrastructure equipment used in the application to the reference timestamp and the time of the time synchronization server of the operation base. Correct using the difference with the stamp,
A timestamp correction method characterized by: The time stamp correction method according to claim 8, comprising:
The operation information acquisition unit of the infrastructure base generates data that associates the timestamp of the infrastructure equipment used in the application with the timestamp of the time synchronization server, and the timestamp of the infrastructure equipment that outputs the reference timestamp. writing data in which the data is associated with the timestamp of the time synchronization server to the time series DB;
A timestamp correction method characterized by: to the computer,
An infrastructure base that operates one or more infrastructure devices or a time stamp obtained from the infrastructure equipment, and a remote operation system that manages data obtained via a network from the infrastructure base that operates one or more infrastructure devices has Processing to calculate the difference with the timestamp of the time synchronization server of the operation base,
In accordance with a data acquisition request received from an application that includes the time system that the data of the infrastructure equipment used in the application follows and the specification of the data acquisition range, the time of the infrastructure base or the infrastructure equipment is added to the data acquired from the infrastructure equipment. If the timestamp of the data in the acquisition range acquired from a time-series DB that accumulates and holds stamped operational information and the difference satisfy a predetermined condition, the timestamp of the data in the acquisition range is A process of correcting using differences,
A timestamp correction program that runs the following.

Images