GitHubContribute in GitHub: Edit online

hassuffix_cs operator

Filters a record set for data with a case-sensitive ending string. has searches for indexed terms, where a term is three or more characters. If your term is fewer than three characters, the query scans the values in the column, which is slower than looking up the term in the term index.

The following table provides a comparison of the hassuffix operators:

Operator Description Case-Sensitive Example (yields true)
hassuffix RHS is a term suffix in LHS No "microsoftWindowsSource5" hassuffix "CE5"
!hassuffix RHS isn't a term suffix in LHS No "microsoftWindowsSource5" !hassuffix "micro"
hassuffix_cs RHS is a term suffix in LHS Yes "microsoftWindowsSource5" hassuffix_cs "ce5"
!hassuffix_cs RHS isn't a term suffix in LHS Yes "microsoftWindowsSource5" !hassuffix_cs "CE5"

  • RHS = right hand side of the expression
  • LHS = left hand side of the expression

For further information about other operators and to determine which operator is most appropriate for your query, see datatype string operators.

Performance tips

Performance depends on the type of search and the structure of the data.

For faster results, use the case-sensitive version of an operator, for example, hassuffix_cs, not hassuffix.


T | where col hassuffix_cs (expression)


  • T - The tabular input whose records are to be filtered.
  • col - The column to filter.
  • expression - Scalar or literal expression.


Rows in T for which the predicate is true.


In this example the query looks for log sources that end with the value In a case sensitive manner.

    | project original_time, data_source_name, name
    //--- has suffix    
    | where original_time > now(-5m)
    | where data_source_name hassuffix_cs "Source5"
    //--- USER Criteria Here
    | take 2


original_time data_source_name name
2023-04-11T14:52:33.755Z microsoftWindowsSource5 Application Information event
2023-04-11T12:27:01.489Z microsoftWindowsSource5 Winlogon Notification Subscriber Unavailable