github/awesome-copilot / skills/appinsights-instrumentation
appinsights-instrumentation
VerifiedInstrument a webapp to send useful telemetry data to Azure App Insights
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 1.1 KB |
| SKILL.md | skill md | 2.4 KB |
| examples/appinsights.bicep | other | 759 B |
| references/ASPNETCORE.md | markdown | 1.7 KB |
| references/AUTO.md | markdown | 891 B |
| references/NODEJS.md | markdown | 1.8 KB |
| references/PYTHON.md | markdown | 1.8 KB |
| scripts/appinsights.ps1 | script | 1.2 KB |
references/ASPNETCORE.md
View on GitHub## Modify code
Make these necessary changes to the app.
- Install client library
```
dotnet add package Azure.Monitor.OpenTelemetry.AspNetCore
```
- Configure the app to use Azure Monitor
An ASP.NET Core app typically has a Program.cs file that "builds" the app. Find this file and apply these changes.
- Add `using Azure.Monitor.OpenTelemetry.AspNetCore;` at the top
- Before calling `builder.Build()`, add this line `builder.Services.AddOpenTelemetry().UseAzureMonitor();`.
> Note: since we modified the code of the app, the app needs to be deployed to take effect.
## Configure App Insights connection string
The App Insights resource has a connection string. Add the connection string as an environment variable of the running app. You can use Azure CLI to query the connection string of the App Insights resource. See [scripts/appinsights.ps1](../scripts/appinsights.ps1) for what Azure CLI command to execute for querying the connection string.
After getting the connection string, set this environment variable with its value.
```
"APPLICATIONINSIGHTS_CONNECTION_STRING={your_application_insights_connection_string}"
```
If the app has IaC template such as Bicep or terraform files representing its cloud instance, this environment variable should be added to the IaC template to be applied in each deployment. Otherwise, use Azure CLI to manually apply the environment variable to the cloud instance of the app. See [scripts/appinsights.ps1](../scripts/appinsights.ps1) for what Azure CLI command to execute for setting this environment variable.
> Important: Don't modify appsettings.json. It was a deprecated way to configure App Insights. The environment variable is the new recommended way.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |