mirror of
https://github.com/github/awesome-copilot.git
synced 2026-08-16 06:06:54 +00:00
Stephen Benjamin
4214189287
While implementing the Agent Plugin v1 spec in https://github.com/stbenjam/skillsaw/pull/483, I used this repository as a canonical real-world source for tests. Along the way its checks surfaced genuine correctness issues worth fixing regardless of tooling: - Internal links that do not resolve (22): wrong relative paths, links whose targets are runtime output paths rather than bundled files (now inline code), a schemeless external URL parsed as a relative path, and links to files that do not exist (removed). - Bundled skill files never referenced from their SKILL.md (14): each is now cited from the section where it is used, so nothing ships unreachable from the skill's instructions. - Unclosed or mis-nested code fences (11): markdown templates embedding code blocks now use four-backtick outer fences so inner fences nest instead of closing the template early and leaking example content as live markdown; also removed stray orphan fences and closed an unterminated block at end of file. - Invisible unicode (1): removed a zero-width space from a code example, a copy-paste artifact invisible to reviewers.
30 lines
1.7 KiB
Markdown
30 lines
1.7 KiB
Markdown
## 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.
|