惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

M
MIT News - Artificial intelligence
有赞技术团队
有赞技术团队
S
Schneier on Security
aimingoo的专栏
aimingoo的专栏
T
Troy Hunt's Blog
U
Unit 42
Hacker News - Newest:
Hacker News - Newest: "LLM"
V2EX - 技术
V2EX - 技术
T
The Blog of Author Tim Ferriss
V
Visual Studio Blog
H
Heimdal Security Blog
H
Hacker News: Front Page
Blog — PlanetScale
Blog — PlanetScale
博客园 - 司徒正美
Cloudbric
Cloudbric
Google DeepMind News
Google DeepMind News
C
Cisco Blogs
The Cloudflare Blog
C
Cybersecurity and Infrastructure Security Agency CISA
Microsoft Security Blog
Microsoft Security Blog
MyScale Blog
MyScale Blog
F
Fortinet All Blogs
N
News | PayPal Newsroom
Attack and Defense Labs
Attack and Defense Labs
D
DataBreaches.Net
N
News and Events Feed by Topic
Security Archives - TechRepublic
Security Archives - TechRepublic
Forbes - Security
Forbes - Security
Simon Willison's Weblog
Simon Willison's Weblog
F
Full Disclosure
The Register - Security
The Register - Security
L
LINUX DO - 热门话题
Webroot Blog
Webroot Blog
Google Online Security Blog
Google Online Security Blog
AI
AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
I
Intezer
S
Security Affairs
阮一峰的网络日志
阮一峰的网络日志
K
Kaspersky official blog
云风的 BLOG
云风的 BLOG
博客园 - 叶小钗
T
Threatpost
Spread Privacy
Spread Privacy
小众软件
小众软件
AWS News Blog
AWS News Blog
S
Secure Thoughts
S
Security @ Cisco Blogs
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
J
Java Code Geeks

Datadog | The Monitor blog

Introducing our open source AI-native SAST Instrument and monitor Boomi integration flows with OpenTelemetry and Datadog Not all index scans are equal: How we cut query latency by over 99% Platform engineering metrics: What to measure and what to ignore Integrate Recorded Future threat intelligence with Datadog Cloud SIEM CI/CD security: threat modeling using a MITRE-style threat matrix CI/CD security: How to secure your GitHub ecosystem Ingress NGINX is EOL: A practical guide for migrating to Kubernetes Gateway API Operating agentic AI with Amazon Bedrock AgentCore and Datadog LLM Observability: Lessons from NTT DATA Introducing the Datadog Code Security MCP Capture and analyze custom heatmaps in Session Replay Understand session replays faster with AI summaries and smart chapters Monitor ClickHouse query performance with Datadog Database Monitoring How we designed empathetic alert sounds for on-call engineers Search and act across Datadog to resolve issues faster with Bits Assistant Measure the business impact of every product change with Datadog Experiments Analyzing round trip query latency Configuring JavaScript caches for better performance Introducing Bits AI Dev Agent for Code Security Datadog achieves ISO 42001 certification for responsible AI Monitor Nutanix clusters, hosts, and VMs with Datadog Monitor Juniper Mist in Datadog A new Host Map for modern infrastructure Annotate traces to improve LLM quality with Datadog LLM Observability What’s new in Cloud SIEM: AI-powered investigations, enhanced threat intelligence, and scalable security operations Explore Kubernetes with native OpenTelemetry data Monitor Oracle Fusion Cloud Applications with Datadog Announcing the Datadog Terraform provider v4.0.0 Scaling Kubernetes workloads on custom metrics How to design cloud environments for AI-powered threat analysis Monitor Aruba Central in Datadog How we centralize and remediate risks with Datadog Case Management Accelerate incident response with Datadog and ServiceNow Monitor your application and network load balancer logs Understanding Karpenter architecture for Kubernetes autoscaling Tools for collecting metrics and logs from Karpenter Monitor Karpenter with Datadog What your product data is actually saying Key metrics for monitoring Karpenter Securing Datadog’s platform in the AI age: The role of observability data Four ways engineering teams use the Datadog MCP Server to power AI agents Approaching your observability migration with the right mindset Meet the new Bits AI SRE: Deeper reasoning, twice as fast Key learnings from the 2026 State of DevSecOps study Use plain English to query your multi-cloud infrastructure in Resource Catalog Simplifying troubleshooting across the user journey with Datadog Synthetic Monitoring Protect your OCI resources with Datadog Cloud Security This Month in Datadog - February 2026 Amazon EC2 security: How misconfigured and public AMIs expand your cloud attack surface Enable end-to-end visibility into your Java apps with a single command Measure and improve mobile app startup performance with Datadog RUM Evaluating our AI Guard application to improve quality and control cost Identify untested code across every level of your codebase Make use of guardrail metrics and stop babysitting your releases Monitor Versa Networks SD-WAN performance in Datadog Improve performance and reliability with APM Recommendations Remediate transitive vulnerabilities faster with Datadog Software Composition Analysis Generate audit-ready vulnerability and compliance reports with Datadog Sheets Monitor Fortinet FortiManager performance in Datadog Improve test coverage across codebases with Datadog Code Coverage Move fast, don’t break things: Consistent testing standards at scale Enrich logs with ServiceNow CMDB context before routing to any SIEM or logging tool Monitor Lustre with Datadog Make faster, better product decisions with Datadog Product Analytics Surface and remediate runtime posture issues with Workload Protection Findings Protect agentic AI applications with Datadog AI Guard How to optimize JavaScript code with CSS Trace Google Pub/Sub workloads in Cloud Run with Datadog Detect human names in logs with ML in Sensitive Data Scanner How we cut our NLQ agent debugging time from hours to minutes with LLM Observability Debug PostgreSQL query latency faster with EXPLAIN ANALYZE in Datadog Database Monitoring Datadog acquires Propolis Unify and correlate frontend and backend data with retention filters Scale compliance across global frameworks with Datadog Cloud Security Monitor Arista VeloCloud SD-WAN performance with Datadog Building reliable dashboard agents with Datadog LLM Observability Simplify log collection and aggregation for MSSPs with Datadog Observability Pipelines Mitigation for Node.js denial-of-service vulnerability affecting Datadog APM Automate flaky test fixes with the Bits AI Dev Agent and Test Optimization How we built an AI SRE agent that investigates like a team of engineers Datadog integrations 2025 recap: Observability for AI, security, and hybrid cloud Design effective executive dashboards with Datadog Implement dbt data quality checks with dbt-expectations Bring faster visibility into AWS Lambda functions with remote instrumentation Troubleshoot faster with the GitLab Source Code integration in Datadog How Cambia Health Solutions saved $30,000 monthly with Cloud Cost Management and the Datadog Resource Catalog Normalize any logs for Cloud SIEM with Datadog's OCSF processor Optimizing Datadog at scale: Cost-efficient observability at Zendesk Detect, diagnose, and resolve network issues easily with CNM Network Health Connect engineering errors to user impact in early-stage products Cilium configuration for Kubernetes operations at scale Designing feedback loops for progressive delivery Ship features faster and safer with Datadog Feature Flags Choosing the right OpenTelemetry Collector distribution Route your monitor alerts with Datadog monitor notification rules Automate Cloud SIEM investigations with Bits AI Security Analyst Cloud threat detection: How to identify risky activity across control and data planes Collecting Kafka performance metrics Monitoring Kafka with Datadog Monitoring Kafka performance metrics
Best practices for monitoring cloud costs with Datadog Scorecards
2024-10-31 · via Datadog | The Monitor blog

To ensure that your organization’s cloud spend is efficient, you need detailed and granular visibility to understand what comprises your costs, what causes them to change, and how the cloud services and resources you use are enabling your business goals. Extending your visibility and more closely monitoring your cloud costs can position you to successfully adopt FinOps, which provides a framework that can help you maximize the value you get from your cloud spend. As you evolve your cloud cost monitoring, you can mature your FinOps practice, empowering your teams to more actively manage their costs and identifying the trends that illustrate your organization’s cost-management improvements.

Datadog Scorecards evaluate your organization’s compliance against your observability, reliability, and documentation standards, and ensure visibility into each service’s ownership data. By adding custom rules to your scorecards, you can easily track your FinOps evolution and share data to report that progress to stakeholders throughout the organization.

In this post, we’ll describe several best practices that will help you initiate and mature your organization’s FinOps practice. We’ll show you how Scorecards and Workflow Automation can jump-start your organization’s adoption and compliance by helping you collect cloud cost data and showcase the effectiveness of your optimizations as your FinOps practice matures.

We’ll look at how you can:

Tag your resources for complete cost allocation

A key capability for a successful FinOps practice is cost allocation—attributing the component costs in your cloud bill to the specific business units or activities (such as teams, departments, or applications) that incurred those costs. Some cloud costs are shared—such as Kubernetes clusters that host services used by different teams—and can be difficult to allocate. But developing your organization’s cost allocation capability early in your FinOps journey is critical, because even partial allocation can reveal paths toward optimizing your spend. It’s important to allocate costs as much as you can based on the data you have and then aim to increase your cost allocation as your FinOps practice matures.

Adding a team tag to your cloud infrastructure components is a productive step in increasing your cost allocation. This tag allows you to isolate each team’s costs from the organization’s overall cloud spend, enabling cost ownership—a key principle in the FinOps framework. You can use Scorecards to help you track your organization’s use of the team tag, which can help you understand how well you’re able to allocate costs. In the screenshot below, a new custom rule is being added to the Cloud Costs scorecard to track usage of the team tag.

Configuring a custom rule in Datadog to allocate at least 80 percent of service costs by team tag.

If your organization is new to FinOps—in what the FinOps Maturity Model calls the “crawl” stage—you should aim to allocate at least 50 percent of your costs. As your FinOps practice matures, you should increase this target, aiming for at least 80 percent in the intermediate (“walk”) phase of the maturity model.

You can use Datadog Workflow Automation to automatically evaluate your services’ use of the team tag and determine your overall cost allocation capability. The Workflow blueprint titled “At least 80 percent of a service’s costs are allocated using the team tag” calculates the percentage of each service’s costs that are tagged appropriately. The workflow automatically updates the outcome for each service, assigning it a PASSING result if 80 percent or more of its costs are tagged, or a FAILING result if the percentage of costs is too low.

In the screenshot below, the Scorecards view shows that 57 percent of services have the team tag applied. Note that one of the services has an outcome of SKIPPED, which indicates that no cost data was available for that service. One of the services with a FAILING outcome is expanded to explain the outcome and show recommended remediation steps.

Datadog's cloud cost scorecard displaying service compliance with cost monitoring rules.

Datadog provides resources to help you improve your tagging and increase your cost allocation. The cost visibility enabled through team tags complements the scoped resource visibility provided by Datadog Teams, which can help teams understand their costs in context. And you can use Datadog Tag Pipelines to help standardize the tags on your cloud resources. You can also use tools from your cloud provider to help enforce tagging, such as an AWS tag policy or Service Control Policy (SCP).

Some resources may remain untaggable—for example, your cloud provider’s monitoring, logging, and support services. Although you may not reach 100 percent cost allocation, each increase you make improves your position to track and optimize your costs.

Maximize your use of commitment-based discounts

While using less of the cloud services and resources you rely on is one path to cost optimization, paying less for what you use—by adopting commitment-based discounts—is another path. Discount programs such as Amazon EC2 Reserved Instances allow you to reduce the cost of a service by committing to and prepaying for an amount of usage of that service. They can provide substantial savings, but require that you accurately project your future utilization of the service—if you overcommit, you’ll pay for service you don’t end up using.

You should take full advantage of these programs, but you need a deep understanding of your cloud costs to manage the risk of overpaying. The FinOps Maturity Model specifies a goal for organizations in the “crawl” phase to purchase enough discounts to cover just 60 percent of their eligible cloud spend. This can help new FinOps practitioners mitigate the risk of overcommitting until they have gained enough experience to safely purchase more discounts. As your FinOps practice matures into the “walk” phase, you’ll have greater cost allocation and visibility, and you should aim to increase your discount purchases enough to cover 70 percent of your eligible spend.

Scorecard view showing discount program compliance across services.

The Workflow blueprint titled “Discount program coverage is at least 70 percent for a service” queries the proportion of discounted costs to overall costs. You can create a workflow based on this blueprint, and then add a custom rule to your Scorecards to surface the amount of discount coverage for each service, as well as your overall score rolled up from coverage data across all services.

Alert on unexpected cost changes

The speed and flexibility of the cloud enables teams to innovate quickly and operate reliable, performant applications. But while the cloud’s elastic nature helps you ensure your applications’ performance—for example, by instantly triggering serverless functions and fluidly managing your autoscaling groups—it can also lead to unexpected increases in your cloud spending. To avoid the panic of receiving a monthly bill that’s higher than you expected, you should rely on real-time alerting to identify rising cloud costs while you still have time to mitigate them.

Cost Monitors for Datadog Cloud Cost Management allow you to alert on unexpected changes in your rate of cloud spend. Cost monitors proactively notify your engineering and FinOps teams, enabling them to investigate the cause of an increase and mitigate its impact on your monthly bill by optimizing the affected resource. You can alert on cost anomalies, as illustrated in the screenshot below. You can also alert on costs that rise above a threshold, forecasts that predict future costs above a limit you specify, or cost changes in comparison to the previous day, week, or month.

Setting up an anomaly cost monitor. The screenshot also shows daily cost view and anomalies view.

Scorecards can help you ensure that each of your services has at least one cost monitor to help you track its costs. Using a blueprint, you can easily build a workflow that automatically checks your services’ cost monitors and displays the outcome on a scorecard. In the screenshot below, a scorecard shows the rule’s outcome for each service and reports that only 25 percent of services have at least one associated cost monitor.

Tracking cloud cost compliance: Datadog Scorecard showing services with one or more cost monitors.

You can easily make your scorecards visible to stakeholders throughout your organization—for example, by sharing reports via Slack—to spotlight your teams’ compliance with this and other best practices and cultivate another key FinOps capability: reporting and analytics.

Adopt best practices for continual cost optimization

Even if your FinOps practice is well established, the best practices we’ve highlighted in this post can help you achieve continuous optimization by improving your cloud cost monitoring and management. Scorecards give you visibility into your cost optimization status and let you track your progress and share updates across the organization to highlight your evolving FinOps capabilities. If you’re not already using Datadog, you can start today with a free 14-day trial.