Pattern did not match non-truncated example – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.13-8.9

Briefly, this error occurs when the pattern defined in Elasticsearch does not match the non-truncated example. This could be due to incorrect pattern syntax or a mismatch between the pattern and the data. To resolve this issue, you can: 1) Review and correct the pattern syntax, ensuring it aligns with Elasticsearch’s regular expression syntax. 2) Check the data you’re trying to match, ensuring it aligns with the pattern. 3) If the data is dynamic, consider using a more flexible pattern. 4) If the pattern is complex, break it down into simpler patterns for easier debugging.

This guide will help you check for common problems that cause the log ” [{}] Pattern [{}] did not match non-truncated example [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] Pattern [{}] did not match non-truncated example [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                // case we will have appended an ellipsis to indicate truncation.
                assert example.endsWith("...") : exampleProcessor.pattern() + " did not match non-truncated example " + example;
                if (example.endsWith("...")) {
                    logger.trace(() -> format("[%s] Pattern [%s] did not match truncated example"; jobId; exampleProcessor.pattern()));
                } else {
                    logger.warn("[{}] Pattern [{}] did not match non-truncated example [{}]"; jobId; exampleProcessor.pattern(); example);

        Map fieldNameCountStore = new HashMap();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?