Azure / Azure/azure-quickstart-templates

Should Instrumentation Key (instead of Connecting String) of an App Insight still be used in App service?

Open
#14,083 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

[Web App with App Insight sample](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.web/web-app-loganalytics/main.bicep#L57)

### Issue Details
I'm trying to look for a simple example to create a Web App with App Insights instrumentation. I found the above example, but I see that it is still using the _Instrumentation Key_. According to a [Doc](https://learn.microsoft.com/en-us/azure/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings), it sounds like Microsoft is recommending the move to _Connection Strings_. [Searching](https://github.com/search?q=repo%3AAzure%2Fazure-quickstart-templates%20APPINSIGHTS_INSTRUMENTATIONKEY&type=code) the full repo I see 44 files with the string `APPINSIGHTS_INSTRUMENTATIONKEY`. Just wondering I should go to the _Connection String_ or stay with the _Instrumentation Key_.
 

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the linked web-app-loganalytics/main.bicep example at line 57 and the Azure Monitor migration guidance on instrumentation keys versus connection strings. Compare the repository's 44 APPINSIGHTS_INSTRUMENTATIONKEY occurrences to determine the applicable recommendation; done means the issue has a clear answer and, if needed, identifies the affected examples for updating.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.