IP Library Granted Patent US 11,853,294
Granted Patent B2
US 11,853,294 · App. 17/883,812 · Granted Dec 26, 2023

Key name synthesis

Inventors: Christian Friedrich Beedgen (Mountain View, CA); David M. Andrzejewski (San Francisco, CA); Benjamin Everette Newton (Belmont, CA); Kumar Avijit (Fremont, CA); Stefan Christoph Zier (San Jose, CA)
Assignee: Sumo Logic, Inc.
G06F16/2379G06F16/2228G06F16/24G06F16/258
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,853,294
App. No.
17/883,812
Granted
Dec 26, 2023
Kind
B2
Abstract

Key name synthesis is disclosed. A metrics data point is received. Based at least in part on a translation statement, at least a portion of the received metrics data point is associated with a key specified by the translation statement such that the specified key and the associated at least portion of the received metrics data point form a key-value pair. The key-value pair is associated with the received metrics data point.

Claims (60)

1. A computer-implemented method comprising:

creating a metadata catalog for indexing a plurality of time series that store information from log messages, each log message comprising a timestamp, a metric name, and a metric value corresponding to the metric name, each time series storing the metric values and corresponding timestamps for one metric name from a plurality of metric names, wherein a time-series table is created for each time series and the name of the time-series table is determined based on the metric name and identifying metadata extracted from the log messages, each row of the time-series table comprising the timestamp and the metric value associated with one element of the time series, wherein metric values for different metric names are stored in different time-series tables, wherein each time series is implemented as a time-series table and each time-series table is stored in a time-series database, the metadata catalog comprising a metric table for each metric name, the metric table comprising an entry for each metric name with information on time series associated with the metric name;

for each received log message:

identifying the entry in the metric table based on the metric name extracted from the log message and a key value pair metadata;

accessing the identified entry in the metric table to identify the time-series table for storing the log message based on the metric name extracted from the log message; and

adding to the identified time-series table a new entry with the metric value and timestamp in the received log message;

providing a user interface (UI) for presenting information on the plurality of time series associated with the metadata catalog;

receiving a selection on the UI of a first time series from the plurality of time series; and

presenting information on the first time series in the UI.

2. The method as recited in claim 1 , wherein providing the UI comprises:

presenting a list of the plurality of time series based on information of the metadata catalog.

3. The method as recited in claim 1 , wherein providing the UI comprises:

providing an option for entering a search value;

accessing the metric table of the metadata catalog to identify time series matching the search value; and

presenting the identified time series that match the search value.

4. The method as recited in claim 3 , wherein at least one time series from the plurality of time series comprises a host identifier, the method further comprising:

entering a host identifier as the search value; and

presenting the time series associated with a metric name equal to the host identifier.

5. The method as recited in claim 1 , wherein providing the UI comprises:

presenting a graphical preview of time series that match a metric value received in a query, the graphical preview comprising one line for each time series.

6. The method as recited in claim 1 , wherein the metric table includes a link to the time-series table where the time series is stored.

7. The method as recited in claim 1 , wherein providing the UI comprises:

providing an auto-complete feature for selecting a time series, the auto-complete feature being based on the metadata catalog.

8. A system comprising:

a memory comprising instructions; and

one or more computer processors, wherein the instructions, when executed by the one or more computer processors, cause the system to perform operations comprising:

creating a metadata catalog for indexing a plurality of time series that store information from log messages, each log message comprising a timestamp, a metric name, and a metric value corresponding to the metric name, each time series storing the metric values and corresponding timestamps for one metric name from a plurality of metric names, wherein a time-series table is created for each time series and the name of the time-series table is determined based on the metric name and identifying metadata extracted from the log messages, each row of the time-series table comprising the timestamp and the metric value associated with one element of the time series, wherein metric values for different metric names are stored in different time-series tables, wherein each time series is implemented as a time-series table and each time-series table is stored in a time-series database, the metadata catalog comprising a metric table for each metric name, the metric table comprising an entry for each metric name with information on time series associated with the metric name;

for each received log message:

identifying the entry in the metric table based on the metric name extracted from the log message and a key value pair metadata;

accessing the identified entry in the metric table to identify the time-series table for storing the log message based on the metric name extracted from the log message; and

adding to the identified time-series table a new entry with the metric value and timestamp in the received log message;

providing a user interface (UI) for presenting information on the plurality of time series associated with the metadata catalog;

receiving a selection on the UI of a first time series from the plurality of time series; and

presenting information on the first time series in the UI.

9. The system as recited in claim 8 , wherein providing the UI comprises:

presenting a list of the plurality of time series based on information of the metadata catalog.

10. The system as recited in claim 8 , wherein providing the UI comprises:

providing an option for entering a search value;

accessing the metric table of the metadata catalog to identify time series matching the search value; and

presenting the identified time series that match the search value.

11. The system as recited in claim 8 , wherein the metadata catalog stores metric values and timestamps for each metric name and a pointer to a table where the metric values and the timestamps for that metric name are stored.

12. The system as recited in claim 8 , wherein providing the UI comprises:

presenting a graphical preview of time series that match a metric value received in a query, the graphical preview comprising one line for each time series.

13. A non-transitory machine-readable storage medium including instructions that, when executed by a machine, cause the machine to perform operations comprising:

creating a metadata catalog for indexing a plurality of time series that store information from log messages, each log message comprising a timestamp, a metric name, and a metric value corresponding to the metric name, each time series storing the metric values and corresponding timestamps for one metric name from a plurality of metric names, wherein a time-series table is created for each time series and the name of the time-series table is determined based on the metric name and identifying metadata extracted from the log messages, each row of the time-series table comprising the timestamp and the metric value associated with one element of the time series, wherein metric values for different metric names are stored in different time-series tables, wherein each time series is implemented as a time-series table and each time-series table is stored in a time-series database, the metadata catalog comprising a metric table for each metric name, the metric table comprising an entry for each metric name with information on time series associated with the metric name;

for each received log message:

identifying the entry in the metric table based on the metric name extracted from the log message and a key value pair metadata;

accessing the identified entry in the metric table to identify the time-series table for storing the log message based on the metric name extracted from the log message; and

adding to the identified time-series table a new entry with the metric value and timestamp in the received log message;

providing a user interface (UI) for presenting information on the plurality of time series associated with the metadata catalog;

receiving a selection on the UI of a first time series from the plurality of time series; and

presenting information on the first time series in the UI.

14. The non-transitory machine-readable storage medium as recited in claim 13 , wherein providing the UI comprises:

presenting a list of the plurality of time series based on information of the metadata catalog.

15. The non-transitory machine-readable storage medium as recited in claim 13 , wherein providing the UI comprises:

providing an option for entering a search value;

accessing the metric table of the metadata catalog to identify time series matching the search value; and

presenting the identified time series that match the search value.

16. The non-transitory machine-readable storage medium as recited in claim 13 , wherein providing the UI comprises:

presenting a graphical preview of time series that match a metric value received in a query, the graphical preview comprising one line for each time series.

Assignments (2)
PATENT SECURITY AGREEMENT Recorded May 12, 2023
From: SUMO LOGIC, INC.
To: AB PRIVATE CREDIT INVESTORS LLC, AS COLLATERAL AGENT
Reel/Frame 063633/0648 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 17, 2022
From: BEEDGEN, CHRISTIAN FRIEDRICH; ANDRZEJEWSKI, DAVID M.; NEWTON, BENJAMIN EVERETTE; AVIJIT, KUMAR; ZIER, STEFAN CHRISTOPH
To: SUMO LOGIC, INC.
Reel/Frame 060832/0659 →
Continuity (4)
Continuation 16031738 · Jul 10, 2018
Provisional Application 62686587 · Jun 18, 2018
Provisional Application 62586754 · Nov 15, 2017
Related Publication 20220398243A1 · Dec 15, 2022
Cited By (2)
US 12,477,364 US 12,495,319