Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Enhance report performance with new Elasticsearch features (8.2)

Updated on May 3, 2021

New Elasticsearch enhancements improve reporting performance and the reporting and searching experience.

  • Filtering in reports is now case-insensitive. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing affects performance.
  • Reports that use string comparison operators in filters can now run queries against Elasticsearch instead of querying the database. The following operators are supported for Elasticsearch queries:
    • Starts with, Ends with, Does not start with, and Does not end with
    • Contains and Does not contain
    • Greater than, Less than, Greater than or equal, and Less than or equal

    In cases where a query cannot be run against Elasticsearch, the query is run against the database, for example, if the query includes a join. To determine if a query was run against Elasticsearch, use the Tracer tool and enable the Query resolution event type.

The following image shows the filters on the Report Definition.


Report Definition filters

For more information about report filtering, see Editing filter conditions

For more information about tracing events, see Tracer event types to trace.

  • Previous topic Increase search indexing performance using a queue processor (8.2)
  • Next topic Improve reporting performance by configuring Elasticsearch indexing

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us