US 11,853,294 B2
Key name synthesis
Christian Friedrich Beedgen, Mountain View, CA (US); David M. Andrzejewski, San Francisco, CA (US); Benjamin Everette Newton, Belmont, CA (US); Kumar Avijit, Fremont, CA (US); and Stefan Christoph Zier, San Jose, CA (US)
Assigned to Sumo Logic, Inc., Redwood City, CA (US)
Filed by Sumo Logic, Inc., Redwood City, CA (US)
Filed on Aug. 9, 2022, as Appl. No. 17/883,812.
Application 17/883,812 is a continuation of application No. 16/031,738, filed on Jul. 10, 2018, granted, now 11,481,383.
Claims priority of provisional application 62/686,587, filed on Jun. 18, 2018.
Claims priority of provisional application 62/586,754, filed on Nov. 15, 2017.
Prior Publication US 2022/0398243 A1, Dec. 15, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/23 (2019.01); G06F 16/22 (2019.01); G06F 16/24 (2019.01); G06F 16/25 (2019.01)
CPC G06F 16/2379 (2019.01) [G06F 16/2228 (2019.01); G06F 16/24 (2019.01); G06F 16/258 (2019.01)] 16 Claims
OG exemplary drawing
 
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.