You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No results in wildcard searches when missing first letter #2648
We encountered a problem when using the raw filter with wildcard
It seems like there needs to be at least the first letter of the wanted string to get results with the substring.:
Additional info:
There was an error in the Exceptionless-Web-Log providing the problem with the query
"allow_leading_wildcard" is set to false in the post request to elasticsearch
without that, going against elasticsearch itself, the results are correct
Thanks for the update and for tracking down the Elasticsearch setting. We’ve historically disabled leading wildcard searches, which can be expensive and affect overall system performance. We’ll discuss this further with the team before making any changes.
It's insanely expensive, Any reason you couldn't do this search without the leading wildcard? Like use a custom property? We might be willing to accept a pr for this as long as it defaults to off. Just want to make sure we lead anyone turning this on down the right path.
In our case its about searching through the error-log messages of a scheduler with several steps where the suspect of the job (a tablename with underscores) was only mentioned in the message
With log messages custom properties would be no problem, but with error messages its a lot more complicated for us
I searched through the exceptionless repo but did not find the spot where the wildcard option was turned off, so I can't really provide a pr as I guess the option is set somewhere in the foundatio dependencies of exceptionless.
Activity
niklastha commentedon Oct 8, 2026
Additional info:
There was an error in the Exceptionless-Web-Log providing the problem with the query
"allow_leading_wildcard" is set to false in the post request to elasticsearch
without that, going against elasticsearch itself, the results are correct
niemyjski commentedon Oct 8, 2026
Thanks for the update and for tracking down the Elasticsearch setting. We’ve historically disabled leading wildcard searches, which can be expensive and affect overall system performance. We’ll discuss this further with the team before making any changes.
niklastha commentedon Oct 9, 2026
I understand. Maybe a setting to enable for self hosters would be nice, if performance is the only concern
niemyjski commentedon Oct 13, 2026
It's insanely expensive, Any reason you couldn't do this search without the leading wildcard? Like use a custom property? We might be willing to accept a pr for this as long as it defaults to off. Just want to make sure we lead anyone turning this on down the right path.
niklastha commentedon Oct 13, 2026
In our case its about searching through the error-log messages of a scheduler with several steps where the suspect of the job (a tablename with underscores) was only mentioned in the message
With log messages custom properties would be no problem, but with error messages its a lot more complicated for us
I searched through the exceptionless repo but did not find the spot where the wildcard option was turned off, so I can't really provide a pr as I guess the option is set somewhere in the foundatio dependencies of exceptionless.