Converting uni-temporal data to cloud based multi-temporal data

Abstract

A method includes receiving configuration data that maps an agent of a source computing system to a node of a graph, maps the node to a table, and maps the agent to an agent topic; and receiving time series data at the agent topic as uni-temporal data from the agent mapped to the node. The method further includes generating a row key, from the configuration data and for the time series data, that includes a value identifier and an acquisition time value; and generating a column identifier, from the configuration data and for the time series data from the agent, that includes a version time value identifying when the time series data is received. The method further includes forming the table as a multi-temporal table by storing the time series data in the table with the row key and with the column identifier.

What is claimed is: 
     
       1. A method comprising:
 receiving configuration data that maps an agent of a source computing system to a node of a graph, maps the node to a table, and maps the agent to an agent topic; 
 receiving time series data at the agent topic as uni-temporal data from the agent mapped to the node; 
 generating a row key, from the configuration data and for the time series data, that includes a value identifier and an acquisition time value, the value identifier describing the time series data and the acquisition time value identifying when the time series data is acquired by the source computing system; 
 generating a column identifier, from the configuration data and for the time series data from the agent, that includes a version time value identifying when the time series data is received; 
 forming the table as a multi-temporal table with a row comprising the row key and a column comprising the column identifier by storing the time series data in the table using the acquisition time value of the row key and using the version time value of the column identifier, the table being mapped to the node that is mapped to the agent; and 
 presenting the row key and the column identifier in the multi-temporal table in a graphical user interface. 
 
     
     
       2. The method of  claim 1 , wherein the table is a first table and the node is a first node, further comprising:
 receiving the time series data from the agent at a data gateway with the agent topic; 
 receiving a message, which includes structure data, from the agent at a configuration gateway with a configuration topic specified in the configuration data; 
 updating the configuration data based on a structure data; and 
 forming a second table that is mapped to a second node based on the updated configuration data. 
 
     
     
       3. The method of  claim 1 , further comprising:
 receiving a time series request for previous time series data stored in the table with a previous column identifier; 
 locating the previous time series data in the table; and 
 transmitting the previous time series data in response to the time series request. 
 
     
     
       4. The method of  claim 1 , further comprising:
 storing the graph in an event based format that includes a set of events; 
 receiving a previous graph request for a previous graph; 
 locating the previous graph in the event based format and loading the previous graph from the set of events; and 
 transmitting the previous graph in response to the previous graph request. 
 
     
     
       5. The method of  claim 1 , wherein the version time value is an unsigned integer that represents an hour of a day with a starting date of eight thousand years before current era. 
     
     
       6. The method of  claim 1 , further comprising:
 sending a subscription request to the agent; and 
 receiving the time series data in response to the subscription request. 
 
     
     
       7. The method of  claim 1 , further comprising:
 scheduling a periodic request for the agent; 
 sending the periodic request to the agent; and 
 receiving the time series data in response to the periodic request. 
 
     
     
       8. A system comprising:
 a memory coupled to a processor; 
 an application that executes on the processor, uses the memory, and is configured for: 
 receiving, by a configuration service of the application, configuration data that maps an agent of a source computing system to a node of a graph, maps the node to a table, and maps the agent to an agent topic; 
 receiving time series data at the agent topic as uni-temporal data from the agent mapped to the node; 
 generating, by an ingestion service of the application, a row key, from the configuration data and for the time series data, that includes a value identifier and an acquisition time value, the value identifier describing the time series data and the acquisition time value identifying when the time series data is acquired by the source computing system; 
 generating a column identifier, from the configuration data and for the time series data from the agent, that includes a version time value identifying when the time series data is received; 
 forming the table as a multi-temporal table with a row comprising the row key and a column comprising the column identifier by storing the time series data in the table using the acquisition time value of the row key and using the version time value of the column identifier, the table being mapped to the node that is mapped to the agent; and 
 presenting the row key and the column identifier in the multi-temporal table in a graphical user interface. 
 
     
     
       9. The system of  claim 8 , wherein the table is a first table, wherein the node is a first node, and wherein the application is further configured for:
 receiving the time series data from the agent at a data gateway with the agent topic; 
 receiving a message, which includes structure data, from the agent at a configuration gateway with a configuration topic specified in the configuration data; 
 updating the configuration data based on a structure data; and 
 forming a second table that is mapped to a second node based on the updated configuration data. 
 
     
     
       10. The system of  claim 8 , wherein the application is further configured for:
 receiving a time series request for previous time series data stored in the table with a previous column identifier; 
 locating the previous time series data in the table; and 
 transmitting the previous time series data in response to the time series request. 
 
     
     
       11. The system of  claim 8 , wherein the application is further configured for:
 storing the graph in an event based format that includes a set of events; 
 receiving a previous graph request for a previous graph; 
 locating the previous graph in the event based format and loading the previous graph from the set of events; and 
 transmitting the previous graph in response to the previous graph request. 
 
     
     
       12. The system of  claim 8 , wherein the version time value is an unsigned integer that represents an hour of a day with a starting date of eight thousand years before current era. 
     
     
       13. The system of  claim 8 , wherein the application is further configured for:
 sending a subscription request to the agent; and 
 receiving the time series data in response to the subscription request. 
 
     
     
       14. The system of  claim 8 , wherein the application is further configured for:
 scheduling a periodic request for the agent; 
 sending the periodic request to the agent; and 
 receiving the time series data in response to the periodic request. 
 
     
     
       15. A non-transitory computer readable medium comprising computer readable program code for:
 receiving configuration data that maps an agent of a source computing system to a node of a graph, maps the node to a table, and maps the agent to an agent topic; 
 receiving time series data at the agent topic as uni-temporal data from the agent mapped to the node; 
 generating a row key, from the configuration data and for the time series data, that includes a value identifier and an acquisition time value, the value identifier describing the time series data and the acquisition time value identifying when the time series data is acquired by the source computing system; 
 generating a column identifier, from the configuration data and for the time series data from the agent, that includes a version time value identifying when the time series data is received; 
 forming the table as a multi-temporal table with a row comprising the row key and a column comprising the column identifier by storing the time series data in the table using the acquisition time value of the row key and using the version time value of the column identifier, the table being mapped to the node that is mapped to the agent; and 
 presenting the row key and the column identifier in the multi-temporal table in a graphical user interface. 
 
     
     
       16. The non-transitory computer readable medium of  claim 15 , wherein the table is a first table and the node is a first node, further comprising computer readable program code for:
 receiving the time series data from the agent at a data gateway with the agent topic; 
 receiving a message, which includes structure data, from the agent at a configuration gateway with a configuration topic specified in the configuration data; 
 updating the configuration data based on a structure data; and 
 forming a second table that is mapped to a second node based on the updated configuration data. 
 
     
     
       17. The non-transitory computer readable medium of  claim 15 , further comprising computer readable program code for:
 receiving a time series request for previous time series data stored in the table with a previous column identifier; 
 locating the previous time series data in the table; and 
 transmitting the previous time series data in response to the time series request. 
 
     
     
       18. The non-transitory computer readable medium of  claim 15 , further comprising computer readable program code for:
 storing the graph in an event based format that includes a set of events; 
 receiving a previous graph request for a previous graph; 
 locating the previous graph in the event based format and loading the previous graph from the set of events; and 
 transmitting the previous graph in response to the previous graph request. 
 
     
     
       19. The non-transitory computer readable medium of  claim 15 , wherein the version time value is an unsigned integer that represents an hour of a day with a starting date of eight thousand years before current era. 
     
     
       20. The non-transitory computer readable medium of  claim 15 , further comprising computer readable program code for:
 sending a subscription request to the agent; and 
 receiving the time series data in response to the subscription request.