MAX_TIME_SERIES

Get the maximum value per time interval. This aggregation is useful for collecting time-series data for graphs. The size of the time intervals is configurable & dynamic; the time interval used will change depending on how many points you wish to hold per aggregation key ‌You can change the time interval and/or the number of points per interval to suit your graph.

Syntax

MAX_TIME_SERIES([MAX POINTS, INTERVALS, ]TIME, VALUE)

Arguments

MAX POINTS: The maximum amount of points to hold before reducing the resolution to the next interval size (Default Value: 300). INTERVALS: An array of integers representing the time interval buckets to return data for. If the aggregation has more than MAX POINTS values in the given window it will use the next interval from this array to reduce the amount of points to comply with MAX POINTS. Default: [60000, 300000, 600000, 1800000, 3600000, 10800000, 21600000, 43200000, 86400000] TIME: An expression returning the time value that the VALUE is to be associated with. VALUE: An expression returning the value to aggregate in the provided TIME bucket.

Returns

An array of key value pairs, the key is the time (in epoch ms) and the value is of type VALUE and contains the average of the values within that time frame.

Note:

Series are arrays, so MAX_TIME_SERIES will only appear in the Add Aggregate dialog when the source file is hierarchical. When uploading files, Upsolver's Infer Types checkbox is used to recognize epoch time as a time field. But it only recognizes epoch time in milliseconds.

When uploading files with INFER TYPES - only 13 digit fields are recognized as valid dates 1628894700 is converted to "data.time" 1,628,894,700. Use Add Calculated Field > TO_DATE to convert 1,628,894,700,000 to 2021-08-14 01:45:00.

AVAILABLE IN

Output Type Availablity Aggregated Outputs NO Explicit Lookup Table YES Inline Joins\Lookups NO

Example

Data

[
   {
      "serverIp":"10.0.0.1",
      "time":1628894700000,
      "cpuUsage":52.3
   },
   {
      "serverIp":"10.0.0.1",
      "time":1628894760000,
      "cpuUsage":2.4
   },
   {
      "serverIp":"10.0.0.1",
      "time":1628894820000,
      "cpuUsage":99.3
   },
   {
      "serverIp":"10.0.0.1",
      "time":1628894880000,
      "cpuUsage":99.6
   },
   {
      "serverIp":"10.0.0.1",
      "time":1628894940000,
      "cpuUsage":12.3
   },
   {
      "serverIp":"10.0.0.1",
      "time":1628895000000,
      "cpuUsage":55
   },
   {
      "serverIp":"10.0.0.2",
      "time":1628894700000,
      "cpuUsage":2.3
   },
   {
      "serverIp":"10.0.0.2",
      "time":1628894760000
   },
   {
      "serverIp":"10.0.0.2",
      "time":1628894820000,
      "cpuUsage":9.3
   },
   {
      "serverIp":"10.0.0.2",
      "time":1628894880000,
      "cpuUsage":9.6
   },
   {
      "serverIp":"10.0.0.2",
      "time":1628894940000,
      "cpuUsage":2.3
   }
]

Query

Collect from server metric events - max cpu over time - in order to display on a graph in a web page:

SELECT 
   data.serverIp AS serverip:STRING,
   MAX_TIME_SERIES(2, [60000, 300000], data.time, data.cpuUsage) AS max_cpu
FROM 
   TIME_SERIES_DATA_w_NULL
GROUP BY 
   data.serverIp

Results

{
   "serverip":"10.0.0.2",
   "max_cpu":[
      {
         "value":9.6,
         "key":1628894700000
      }
   ]
}{
   "serverip":"10.0.0.1",
   "max_cpu":[
      {
         "value":99.6,
         "key":1628894700000
      },
      {
         "value":55,
         "key":1628895000000
      }
   ]
}

Related Functions

MAX MAX_BY MAX_EACH

Dialog