Using Search in Azure Application Insights | Microsoft Docs
Search and filter raw telemetry sent by your web app.
Using Search in Application Insights
Search is a feature of Application Insights that you use to find and explore individual telemetry items, such as page views, exceptions, or web requests. And you can view log traces and events that you have coded.
(For more complex queries over your data, use Analytics.)
Where do you see Search?
In the Azure portal
You can open diagnostic search from the Application Insights Overview tab of your application (located at in the top bar) or under investigate on the left.
Go to the Event types' drop-down menu to see a list of telemetry items- server requests, page views, custom events that you have coded, and so on. At the top of the results' list, is a summary chart showing counts of events over time.
Click out of the drop-down menu or Refresh to get new events.
In Visual Studio
In Visual Studio, there's also an Application Insights Search window. It's most useful for displaying telemetry events generated by the application that you're debugging. But it can also show the events collected from your published app at the Azure portal.
Open the Search window in Visual Studio:
The Search window has features similar to the web portal:
The Track Operation tab is available when you open a request or a page view. An 'operation' is a sequence of events that is associated with to a single request or page view. For example, dependency calls, exceptions, trace logs, and custom events might be part of a single operation. The Track Operation tab shows graphically the timing and duration of these events in relation to the request or page view.
Inspect individual items
Select any telemetry item to see key fields and related items.
This will launch the end-to-end transaction details view.
Filter event types
Open the Event types' drop-down menu and choose the event types you want to see. (If, later, you want to restore the filters, click Reset.)
The event types are:
- Trace - Diagnostic logs including TrackTrace, log4Net, NLog, and System.Diagnostic.Trace calls.
- Request - HTTP requests received by your server application, including pages, scripts, images, style files, and data. These events are used to create the request and response overview charts.
- Page View - Telemetry sent by the web client, used to create page view reports.
- Custom Event - If you inserted calls to TrackEvent() in order to monitor usage, you can search them here.
- Exception - Uncaught exceptions in the server, and those that you log by using TrackException().
- Dependency - Calls from your server application to other services such as REST APIs or databases, and AJAX calls from your client code.
- Availability - Results of availability tests.
Filter on property values
Choosing no values of a particular property has the same effect as choosing all values. It switches off filtering on that property.
Notice that the counts to the right of the filter values show how many occurrences there are in the current filtered set.
Find events with the same property
To find all the items with the same property value, either type it into the search bar or click the checkbox when looking through properties in the filter tab.
Search the data
[!NOTE] To write more complex queries, open Logs (Analytics) from the top of the Search blade.
You can search for terms in any of the property values. This is useful if you have written custom events with property values.
You might want to set a time range, as searches over a shorter range are faster.
Search for complete words, not substrings. Use quotation marks to enclose special characters.
Here are the search expressions you can use:
||Find all events in the time range whose fields include the word "apple"|
||Find events that contain both words. Use capital "AND", not "and".
||Find events that contain either word. Use "OR", not "or".|
||Find events that contain one word but not the other.|
If your app generates a large amount of telemetry (and you are using the ASP.NET SDK version 2.0.0-beta3 or later), the adaptive sampling module automatically reduces the volume that is sent to the portal by sending only a representative fraction of events. However, events that are related to the same request are selected or deselected as a group, so that you can navigate between related events.
Create work item
You can create a bug in GitHub or Azure DevOps with the details from any telemetry item.
Go to the end-to-end transaction detail view by clicking on any telemetry item then select Create work item.
The first time you do this, you are asked to configure a link to your Azure DevOps organization and project.
(You can also configure the link on the Work Items tab.)
Send more telemetry to Application Insights
In addition to the out-of-the-box telemetry sent by Application Insights SDK, you can:
- Capture log traces from your favorite logging framework in .NET or Java. This means you can search through your log traces and correlate them with page views, exceptions, and other events.
- Write code to send custom events, page views, and exceptions.
See the Limits summary.
How can I see POST data in my server requests?
We don't log the POST data automatically, but you can use TrackTrace or log calls. Put the POST data in the message parameter. You can't filter on the message in the same way you can filter on properties, but the size limit is longer.