Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article addresses some of the most frequently asked questions around Azure Application Insights for AppSource apps.
How do I enable Application Insights telemetry for my submissions?
To enable Application Insights signals for your submissions, you must specify the applicationInsightsConnectionString property in the manifest (app.json) of your extension. Learn more about this property in JSON files.
I don't see any signals in the resource specified for my extension, what do I do next?
Here's a list of steps that you can follow to troubleshoot this issue:
- Validate that the Application Insights resource queried is the same one as specified in the manifest (app.json) of your extension.
- Validate that the time range when running the query covers the time of the submission.
- If you're using the
applicationInsightsKeyproperty in the manifest (app.json) of your extension, you should use theapplicationInsightsConnectionStringproperty instead because it's more reliable. Make sure to use the full connection string from your Azure Application Resource. - If you're using the
applicationInsightsConnectionStringproperty in the manifest (app.json) of your extension, make sure that you're using the full connection string and that it contains, at least, the following key-value pairs:InstrumentationKey=<some-key>,IngestionEndpoint=<some-url>, andLiveEndpoint=<some-url>. Learn more in Connection strings - Validate the data sampling and daily cap set for the Azure Application Insights resource. Navigate to the resource in Azure and go to 'Configure > Usage and estimated costs'. Validate that your Application Insights retains all data (data sampling is set to 100%) and that you haven't reached your daily cap. Learn more in Sampling in Application Insights.
I can see some signals in Application Insights, but I can't find why my submission failed, what do I do next?
Much information is provided in the custom dimensions of the signals. The validation errors can generally be found for the signals with eventId LC0034. Learn more about the signals emitted during the technical validation of AppSource submission in Analyzing AppSource submission validation trace telemetry.
Note
Instead of writing your own queries, we recommend using the executable Azure Data Studio Troubleshooting Guide (TSG). This guide contains queries that process the signals for your submission and extract the important information.
Related information
Technical validation checklist
Analyzing AppSource submission validation trace telemetry