If your clients are device apps

If your application is serving clients such as phones or other devices, add the appropriate SDK to your device app.

If you configure the client SDK with the same instrumentation key as the server SDK, the two streams will be integrated so that you can see them together.

Usage tracking

When you've delivered a new user story, you'd like to know how much your customers are using it, and whether they are achieving their goals or having difficulties. Get a detailed picture of user activity by inserting TrackEvent() and other calls in your code, both at the client and server.

Diagnostic logs

Capture log traces from your favorite logging framework to help diagnose any problems. Your log entries will appear in diagnostic search along with the Application Insights telemetry events.

Publish your app

If you haven't yet published your app (since you added Application Insights), do that now. Watch the data grow in the charts as people use your app.

Keep separate resources for dev, test and release

For a major application, it's advisable to send telemetry data from debugging, testing and production into separate resources.

Add dependency tracking

Dependency metrics can be invaluable to help you diagnose performance issues. They measure calls from your app to databases, REST APIs, and other external components.

In Diagnostic Search, select a request that failed or has a long duration. In the details blade, look under Calls to Remote Dependencies to see if the problem is in a call your app made to an external component.

If you don't see anything listed, you need to follow some steps to set up dependency tracking.