- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
The extension includes these features:
Log Annotations: Gauge log volumes and search logs from your code.
Code Insights: Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
View in IDE: Jump directly from code references in Datadog to your source files.
Static Code Analysis: Detect and fix problems before you commit changes.
Exception Replay: Debug your production code.
Datadog account: Most features require a Datadog account.
myorg.datadoghq.com, you must indicate it using the datadog.connection.oauth.setup.domain setting.Git: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the git.enabled setting.
Use Log Annotations to gauge the volume of logs generated by a given log line in your code. The extension adds annotations above your code to detected logging patterns that match log records in Datadog. Click an annotation to open the Log Explorer in Datadog and view the matching logs.
You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select Datadog > Search Logs With Selected Text.
Code insights keep you informed with Datadog-generated insights that are relevant to your code base:
The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
The Code Insights view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you’re most interested in.
For specific insights about the file currently open in the active editor, check the File Insights view in the IDE’s file explorer. This view also lists issues discovered by Static Code Analysis within the file.
The View in VS Code or View in Cursor feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in Error Tracking):
You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
Static Code Analysis analyzes your code (locally) against predefined rules to detect and fix problems.
The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
Static Code Analysis supports scanning for many programming languages. For a complete list, see Static Code Analysis Rules. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
When you start editing a source file, the extension checks for static-analysis.datadog.yml at your source repository’s root. It prompts you to create it if necessary.
After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, search for the command Datadog: Configure Static Analysis Languages in the command palette (Shift + Cmd + P in macOS; Ctrl + Shift + P in Windows).
You can also run a batch analysis for individual folders and even the entire workspace. In the IDE’s file explorer view, right-click a folder and select Datadog Static Analysis > Analyze Folder or Analyze Workspace.
Exception Replay allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
To access this feature, you must enable Error Tracking Exception Replay on Datadog.
After the feature has been enabled, you can see an Exception Replay button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
Read the End-User License Agreement carefully before downloading or using the Datadog Visual Studio Code extension.
Datadog collects certain information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, what caused those errors, and user identifiers in accordance with the Datadog Privacy Policy and Datadog’s VS Code extension EULA. This data is used to help improve the extension’s performance and features, including transitions to and from the extension and the applicable Datadog login page for accessing the Services.
If you don’t wish to send this data to Datadog, you can disable this at any time in the extension’s settings: Datadog > Telemetry > Setup > Enable Telemetry and select disabled.
To share your feedback, email team-ide-integration@datadoghq.com or create an issue in the extension’s public repository.
Check out the issues section to discover known issues.
Do you use Cursor, or another fork of VS Code? Find the extension on the Open VSX Registry.
| |
