Dev/test workflow for tracer engineers working on the Datadog .NET tracer — build a local Datadog.AzureFunctions NuGet package, deploy it to a test Azure Function App, trigger it, and analyze traces/logs to verify instrumentation behavior. Use this skill whenever the user is working on Azure Functions instrumentation: building or testing the Datadog.AzureFunctions NuGet package, deploying to a test Function App, analyzing instrumentation logs or spans from an Azure Functions app, or configuring Datadog environment variables on Azure — even if they don't explicitly invoke /azure-functions.
Update/bump the libdatadog native library version in dd-trace-dotnet. Use when the user asks to bump, update, or upgrade libdatadog, or mentions a new libdatadog release version.
Analyze Azure DevOps CI build failures in dd-trace-dotnet pipeline. This skill should be used when the user mentions a failing CI build, PR checks failing, Azure DevOps pipeline failures, test failures in CI, or when they share a build ID or PR number and want to understand what went wrong. Analyzes build failures, categorizes them (infrastructure/flaky/real), and provides actionable recommendations.
Stack Trace Crash Analysis for dd-trace-dotnet
Perform a review on a GitHub PR, leaving comments on the PR
| name | analyze-error |
| description | Error Stack Trace Analysis for dd-trace-dotnet |
| argument-hint | <paste-error-stack-trace> <ctrl+enter any other context> |
| disable-model-invocation | true |
Analyze a redacted exception that was encountered within an application running dd-trace-dotnet. The exception was caught by dd-trace-dotnet, redacted, and then sent to Datadog's log intake. The goal is to: understand the error, determine if it is caused by dd-trace-dotnet, determine how to reproduce, determine how to prevent it (not catch it).
User provided the basic error message along with the redacted stack trace. First line will be the Error Message - this is a constant message template that dd-trace-dotnet will log and send to Datadog Following lines will be the stack trace.
The user may have entered additional context info afterwards such as descriptions, PR links, versions the error was seen on.
If it appears that duck typing is involved, prior to doing deep analysis go over the source code within dd-trace-dotnet\tracer\src\Datadog.Trace\DuckTyping\ as it is vital to have a clear understanding of this for proper error reconstruction.
When necessary refer to the official source of known third party libraries that are within the stack to provide better error reconstruction.
Use Markdown Do not use tables
Stack Trace, Component / CODEOWNER team, Actionability
2 to 3 sentences that can be used to explain what is happening.
Detailed analysis outlining the code flow that leads to the error. Format as follows:
Before / after code comparison, format this as a git diff
Provide an overview of how to reproduce this error.