Could not perform time series aggregation – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Could not perform time series aggregation ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Log Context

Log “Could not perform time series aggregation”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

&& context.aggregations().factories().context().isInSortOrderExecutionRequired()) {
 TimeSeriesIndexSearcher searcher = new TimeSeriesIndexSearcher(context.searcher(); getCancellationChecks(context));
 try {; bucketCollector);
 } catch (IOException e) {
 throw new AggregationExecutionException("Could not perform time series aggregation"; e);
 context.queryCollectors().put(AggregationPhase.class; BucketCollector.NO_OP_COLLECTOR);
 } else {
 Collector collector = context.getProfilers() == null
 ? bucketCollector


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content