The integrated platform for monitoring & security
Observability
End-to-end, simplified visibility into your stack’s health & performance
製品
Applications
ログ管理
Security
Detect, prioritize, and respond to threats in real-time
Cloud Security
Application Security
Cloud SIEM
Digital Experience
Optimize front-end performance and enhance user experiences
Related Products
Software Delivery
Build, test, secure and ship quality code faster
Service Management
Integrated, streamlined workflows for faster time-to-resolution
AIOps
AI
Monitor and improve model performance. Pinpoint root causes and detect anomalies.
AI Observability
Platform Capabilities
Built-in features & integrations that power the Datadog platform
Built-in Features
Workflows & Collaboration
Extensibility
Industry
Technology
Use-case
Looking for Datadog logos?
You can find the logo assets on our press page.
ID: javascript-best-practices/no-console
javascript-best-practices/no-console
Language: JavaScript
Severity: Warning
Category: Best Practices
Debugging with console is not considered a bad practice, but it’s easy to forget about console statements and leave them in production code. There is no need to pollute production builds with debugging statements.
console
console.log(foo) console.error(foo) console.info(foo) console.warn(foo)
Console.info(foo)
Seamless integrations. Try Datadog Code Analysis
1 2
rulesets: - javascript-best-practices # Rules to enforce JavaScript best practices.
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products
