Opster Team
Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.
This guide will help you check for common problems that cause the log ” data_stream matching ” + request.name + ” not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, indices and request.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.
Log Context
Log “data_stream matching [” + request.name + “] not found”classname is GetDataStreamAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} } } else if (dataStreams.containsKey(request.name)) { results.add(dataStreams.get(request.name)); } else { throw new ResourceNotFoundException("data_stream matching [" + request.name + "] not found"); } results.sort(Comparator.comparing(DataStream::getName)); return results; }
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Try FreeConnect in under 3 minutes
Arpit Ghiya
Senior Lead SRE at Coupa