Data store query

• US 9,727,666 B2
• Filed: 04/30/2014
• Issued: 08/08/2017
• Est. Priority Date: 04/30/2014
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: entIT Software LLC (Open Text Corporation)
• Inventors: Hadzhiyski, Radi Dimitrov, Schimmelpfeng, Joern
• Primary Examiner(s): Beausoliel, Jr., Robert
• Assistant Examiner(s): HOANG, HAU HAI
• Application Number:
  US14/266,238
• Publication Number:
  US 20150317355A1
• Time in Patent Office: 1,196 Days
• CPC Class Codes: G06F 11/0727 in a storage system, e.g. in a DASD or network based storage system drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/243 Natural language query formulation
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/908 using metadata automatically derived from the content
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9538 Presentation of query results

Abstract

Querying a data store can include receiving a query defined by a number of phrases. Querying a data store can include identifying within the data store service component metrics, service component logs, and service component events associated with the query. Querying a data store can include displaying the identified service component metrics, service component logs, and service component events.

Claims

1. A system, comprising:

a receiving engine to receive a query defined by a phrase, wherein the query is in the form of a natural language query that does not include abbreviations or paths corresponding to data stored in a data store;

an identification engine to;

identify within the data store;

a service component metric associated with the phrase,

a service component log associated with the phrase, and

a service component event associated with the phrase;

identify the service component metric, the service component log, and the service component event do not match the phrase defining the natural language query;

determine a relationship between the service component metric, the service component log, and the service component event and a service specified in the phrase by referencing a configuration management database (CMDB) containing a topological mapping of relationships; and

determine the service component metric, the service component log, and the service component event are nonetheless associated with the phrase based on the relationship to the service specified in the phrase; and

a display engine to cause display of the identified service component metric, the identified service component log, and the identified service component event.

2. The system of claim 1, wherein the service component metric includes time series data related to the performance of an associated service component.

3. The system of claim 1, wherein the service component metric includes a tag describing a type of the service component metric.

4. The system of claim 3, wherein the service component metric includes a key attribute identifying an instance of the service component metric.

5. The system of claim 4, wherein the identification engine identifies the service component metric associated with the phrase based on the service component metric having at least one of a tags and a key attribute matching the phrase.

6. The system of claim 4, wherein the identification engine identifies the service component metric associated with the phrase based on having a key attribute matching a phrase following a key attribute indicating keyword in the query.

7. A non-transitory computer readable medium storing instructions executable by a processing resource to cause a computer to:

receive a natural language query defined by a plurality of phrases, wherein the natural language query does not include abbreviations or paths corresponding to data stored in a data store;

identify, in the data store, a service component metric, a service component log, and a service component event, each associated with at least one of the plurality phrases;

sort the identified service component metric, the identified service component log, and the identified service component event, including ordering the identified component metric, the identified service component log, or the identified service component event to appear earlier in a display responsive to the identified component metric, the identified service component log, or the identified service component event having meta information that matches one of the plurality of phrases that immediately follows a topology indicating keyword in the natural language query; and

display the identified service component metrics, the identified service component log, and the identified service component event according to the sort.

8. The non-transitory computer readable medium of claim 7, wherein to sort includes to order based on meta information corresponding to the identified service component metric, the identified service component log, and the identified service component event.

9. The non-transitory computer readable medium of claim 8, wherein an identified service component metric, an identified service component log, and an identified service component event including meta information matching a greater amount of the plurality of phrases appear earlier in the order.

10. A method, comprising:

receiving a natural language query defined by a phrase, wherein the natural language query does not include abbreviations or paths corresponding to data stored in a data store;

identifying, in the data store, a service component metric, a service component log, and a service component event, each associated with the phrase, including;

identifying the service component metric, the service component log, and the service component event do not match the phrase defining the natural language query;

determining a relationship between the service component metric, the service component log, and the service component event and a service specified in the phrase by referencing a configuration management database (CMDB) containing a topological mapping of relationships; and

determining the service component metric, the service component log, and the service component event are nonetheless associated with the phrase based on the relationship to the service specified in the phrase;

sorting the identified service component metric, the identified service component log, and the identified service component event based at least in part on associated meta information and the relationship to the service specified in the query; and

displaying the identified service component metric, the identified service component log, and the identified service component events based on the sorting.

11. The method of claim 10, wherein sorting the identified service component metric, the identified service component log, and the identified service component event includes ordering based on an association with a time frame of interest.

12. The method of claim 10, wherein sorting further comprises ordering a particular service component metric to appear earlier for display than other service component metrics responsive to the particular service component metric having meta information that matches a particular phrase in the natural language query the that immediately follows a topology indicating keyword in the natural language query.

13. The method of claim 10, wherein sorting further comprises ordering a particular service component log to appear earlier for display than other service component logs responsive to the particular service component log having meta information that matches a particular phrase in the natural language query the that immediately follows a topology indicating keyword in the natural language query.

14. The method of claim 10, wherein sorting further comprises ordering a particular service component event to appear earlier for display than other service component events responsive to the particular service component event having meta information that matches a particular phrase in the natural language query the that immediately follows a topology indicating keyword in the natural language query.

15. The method of claim 10, further comprising:

identifying a keyword attribute indicating keyword in the natural language query;

interpreting a particular phrase in the natural language query that immediately follows the keyword attribute indicating keyword as a key attribute that identifies a specific instance of a service component metric, service component log, or service component event associated with the service specified in the phrase of the natural language query.