|
Is there a way to enforce case-sensitivity on a field by field basis? Example: myid="0ZP0YFS5Rl7pACDD1K002" and myid="0ZP0YFS5Rl7pACDD1k002" where the lower-case k at the far right of the value makes these two field values different. |
|
You can use the
1
You should instead code the above as: sourcetype=whatever myid="0ZP0YFS5Rl7pACDD1K002" | where myid="0ZP0YFS5Rl7pACDD1K002". If you do not do so, the search will likely be much less efficient, as it will need to bring back everything from the sourcetype without taking advantage of the index, then filter it with
(08 Sep '10, 17:40)
gkanapathy ♦
|
|
values do not have case-sensitivity. operations on values may have sensitivity to the case of the values. there is no global way to make every possible operation and function in Splunk case-insensitive, and besides "search", most are case-sensitive. You can of course always normalize most values using the "upper()" or "lower()" eval functions, but (for example) this can't be applied to match values in lookup tables. |
|
Another options is to use the
Matching part of a raw event:
A partial-field matching example:
1
Please ensure that you include enough of the text search string in the base query to ensure that the search is efficiently using the index, e.g.,
(08 Sep '10, 17:41)
gkanapathy ♦
|
