Skip to main content

Search

Ad Hoc Searching: Global Pages​

Ad hoc searches run from pages in the navigation rail that reach across all collected data rather than one case or entity: Datalake Search, a faceted search of the events in a data lake index, and KQL Search, which runs KQL queries against the data lake's indexes, including those with typed columns of their own such as AzureSigninLogs (v1: Data Lake → Search and Data Lake → KQL Query Builder).

Events and Flows​

There are two main databases that messages (logs) are stored in:

  • Event Database: Contains the incoming message and how it got there (its metadata)
  • Flow Database: Contains merged messages that shares a common tuple along with enhanced data

Both databases are useful and serve different purposes. Stored events are searched on a single search page.

In the navigation rail, open Datalake Search (/v2/events), subtitled Faceted search across all collected events in the data lake.

Datalake Search page before a search: the index selector, search box and time-range buttons across the top, the event histogram, the Filters panel with the Default facet's empty field groups, and the result table prompting to choose a time range and press Search

Pick an index and a time range, optionally type a search, and press Search; then review the matching events with a histogram of the event count and a configurable breakdown by field. The page is laid out top to bottom as a search bar (Data lake index selector, search box, time-range buttons, Search), a toolbar (the record count, then Save Facet, the sort order, JSON line, Columns, and Export JSON), the histogram, the Filters panel down the left, and the result table with its paging footer. See Events Search for the page in detail.

In this section​

  • Events Search: the search page in detail: indexes, the query bar, facets and the event count timeline.
  • Defining the Query: building a query, and the search and where command reference.
  • Lucene Queries: the free-text syntax the search bar accepts.
  • Facets: configuring the breakdown panel down the left of the results.
  • KQL: the tabular query language used on KQL Search (v1: Data Lake → KQL Query Builder).
  • Data Storage: the indexes and schemas a search runs against.
  • Investigate: searching as part of working a ticket.