The query scheduler executes queries by scanning each segment in portions of a particular byte size (\The query scheduler executes queries by scanning each segment in portions of a particular byte size (\ If a chunk takes too long, the scheduler might decide to stop execution part way through, and defer the rest of the work for later. This allows the scheduler to context switch to other queries, even if some very slow query is present where chunks take a long time. This metric counts how many times that kind of deferment happens, which is an indicator of the presence of one or more very slow queries.

Metric Namequery-segment-chunk-deferred
Metric TypeMeter
Introduced Version1.239
Standard Fields for this Metric  
@hostVHost ID 
@idA unique identifier for the event. Can be used to refer to and re-find specific events. 
@ingesttimestampThe timestamp of when the event was ingested. The value is milliseconds-since-epoch. 
@timestampTimestamp in milliseconds since the epoch (1st Jan 1970, 00:00) of the event, e.g. 2022-11-22 09:50:20.100 if the event has an identifiable timestamp. 
@timestamp.nanosExtended precision of timestamp below millisecond. E.g. 295000 
@timezoneThe timezone the event originated in, if known. 
countCounter of the number of events since LogScale was started. 
m11 minute moving average 
m1515 minute moving average 
m55 minute moving average 
mean_rateMoving mean rate since the application started. 
nameName of metric 
rate_unitRate per unit for metric event 
typeMetric type 

Example Metric Record:

json
{
   "#repo" : "humio-metrics",
   "#type" : "metrics",
   "@host" : "200",
   "@id" : "GEXJkLoqicpCSdSkW6cutQu6_2738_493_1781427803",
   "@ingesttimestamp" : "1781427803457",
   "@timestamp" : 1781427803411,
   "@timestamp.nanos" : "0",
   "@timezone" : "UTC",
   "count" : "0",
   "m1" : "0",
   "m15" : "0",
   "m5" : "0",
   "mean_rate" : "0",
   "name" : "query-segment-chunk-deferred",
   "rate_unit" : "events/second",
   "type" : "METER"
}