Integrating relational and non-relational databases

Patent metadata

Field	Value
Publication number	US-2018307735-A1
Application number	US-201715491300-A
Country	US
Kind code	A1
Filing date	Apr 19, 2017
Priority date	Apr 19, 2017
Publication date	Oct 25, 2018
Grant date	—

Abstract

Provided is a process including: receiving a request for a user interface depicting data specified, at least in part, by the request; accessing data in a first type of database, the data in the first type of database including references to entries in a second type of database different from the first type of database, wherein the two types of databases include a relational database and a non-relational database; forming instructions to present a user interface depicting accessed data in the first type of database with inputs to effectuate access to data in the second type of database.

First claim

What is claimed is:

1 . A method of forming user interfaces based on data that spans relational and non-relational databases, the method comprising:
receiving, with one or more processors, a request for a user interface depicting data specified, at least in part, by the request; in response to receiving the request, accessing, with one or more processors, data in a first type of database, the data in the first type of database including references to entries in a second type of database different from the first type of database, wherein the two types of databases include a relational database and a non-relational database; forming, with one or more processors, instructions to present a user interface depicting accessed data in the first type of database specified, at least in part, by the request, wherein:
the user interface includes a user-selectable visual element associated with an event handler and a first reference from the first type of database to one or more entries in the second type of database,
the user-selectable visual element depicts at least some of the accessed data in the first type of database that is associated in the first type of database with the first reference to one or more entries in the second type of database, and
user selection of the visual element causes the event handler to send an indication that the visual element was selected and the first reference from the first type of database to one or more entries in the second type of database;
receiving, with one or more processors, the indication that the visual element was selected and the first reference from the first type of database to one or more entries in the second type of database; and in response to receiving the indication, accessing, with one or more processors, the one or more entries in the second type of database based on the first reference and causing the accessed one or more entries in the second type of database to be presented in the user interface.

2 . The method of claim 1 , wherein:
the first type of database is a non-relational database; the second type of database is a relational database; the method comprises:
storing first monitoring data from a first monitoring application in the non-relational database, the first monitoring data being indicative of performance of a distributed application executing on a plurality of computing devices;
storing second monitoring data from a second monitoring application different from the first monitoring application in the relational database, the second monitoring data being indicative of performance of the distributed application executing on the plurality of computing devices, the first monitoring data including different metrics or events from metrics or event in the second monitoring data, at least some of the first monitoring data indicating a cause of a metric or event in the second monitoring data or vice versa; and
forming instructions to present the user interface comprises forming instructions to present a monitoring-data dashboard with a plurality of graphs, wherein a plurality of visual elements of the monitoring-data dashboard are user selectable to navigate from a selected visual element depicting data in the non-relational database to another visual element depicting data in the relational database, or vice versa.

3 . The method of claim 1 , wherein:
the user interface comprises a data visualization formed by a data visualization application that is not configured to form visualizations of data in a relational database; and the user-selectable visual element is added to the data visualization by the data visualization application.

4 . The method of claim 3 , comprising:
receiving a data access request sent by the data visualization application; determining that the data access request includes the first reference; in response to the determination:
translating the data access request from a first query language to a second query language different from the first query language; and
selecting a database among the first type of database and the second type of databases corresponding to the second query language.

5 . The method of claim 4 , wherein translating the data access request comprises:
parsing a data access request formatted as a hierarchical arrangement of dictionaries and lists to form an abstract syntax tree; traversing the abstract syntax tree to identify a table identifier and value of a field in a table corresponding to the table identifier; and forming a structured query language query selecting entries having the value of the field from the identified table and requesting the return of responsive data in the form of a hierarchical arrangement of dictionaries and lists.

6 . The method of claim 3 , comprising:
receiving a data access request sent by the data visualization application; determining that the data access request does not include a reference to data in a relational database among the first type of databases and the second type database; and in response to the determination, sending the data access request without translating the other data access request into another query language.

7 . The method of claim 1 , wherein:
the first reference is a query in a query language of the second type of database.

8 . The method of claim 7 , wherein:
the query language of the first type of database is not a version of a structured query language; and the query language of the second type of database is a version of a structured query language.

9 . The method of claim 1 , comprising:
entries in the second type of database include references to entries in the first type of database; and the references to entries in the first type of database correspond to filters configured to filter entries in a non-relational document database.

10 . The method of claim 1 , comprising:
receiving a request to delete a given record stored in the second type of database; in response to the request to delete the given record, accessing the first type of database to identify references to the given record; causing the first type of database to delete the accessed references to the given record; and causing the second type of database to delete the given record.

11 . The method of claim 10 , comprising:
before causing the first type of database to delete the accessed references to the given record, determining that the deleted references to the given record do not reference other records in the second type of database.

12 . The method of claim 1 , comprising:
receiving monitoring data from a plurality of infrastructure monitoring agents executing on a plurality of computing devices executing a distributed application; writing the infrastructure monitoring data to the second type of database; and adding references to the infrastructure monitoring data to records in the first type of database describing performance of the distributed application, wherein adding references to the infrastructure monitoring data to records in the first type of database comprises:
obtaining host identifiers or computing device identifiers of hosts or computing devices monitored by the respective infrastructure monitoring agents;
selecting different subsets of the data in the first type of database based on the different subsets corresponding to different ones of the host identifiers or computing device identifiers; and
adding different references to the different subsets corresponding to different monitoring data of the different hosts or computing devices.

13 . The method of claim 12 , wherein:
the records in the first type of database describ

Assignees

• Ca Inc

Inventors

• Thayer Nicholas D
• Perkins James
• Mishra Rajat Kumar
• Diwakar Kiran Prakash

Classifications

• G06F16/211

  Schema design and management · CPC title

• G06F16/248

  Presentation of query results · CPC title

• G06F16/284

  Relational databases · CPC title

• G06F16/25 Primary

  Integrating or interfacing systems involving database management systems · CPC title

• G06F17/30554

  Physics · mapped topic