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

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hacker News: Front Page
P
Palo Alto Networks Blog
T
ThreatConnect
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
T
True Tiger Recordings
P
Privacy & Cybersecurity Law Blog
B
Blog
IT之家
IT之家
Last Week in AI
Last Week in AI
F
Full Disclosure
Hacker News: Ask HN
Hacker News: Ask HN
C
Comments on: Blog
Microsoft Azure Blog
Microsoft Azure Blog
C
Cybersecurity and Infrastructure Security Agency CISA
Microsoft Security Blog
Microsoft Security Blog
博客园 - 【当耐特】
N
News and Events Feed by Topic
NISL@THU
NISL@THU
腾讯CDC
雷峰网
雷峰网
Security Latest
Security Latest
李成银的技术随笔
M
Microsoft Research Blog - Microsoft Research
L
LangChain Blog
L
Lohrmann on Cybersecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Check Point Blog
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
博客园 - Franky
N
News | PayPal Newsroom
V
V2EX
A
About on SuperTechFans
The Register - Security
The Register - Security
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Google Online Security Blog
Google Online Security Blog
MyScale Blog
MyScale Blog
Cisco Talos Blog
Cisco Talos Blog
Vercel News
Vercel News
WordPress大学
WordPress大学
C
Cyber Attacks, Cyber Crime and Cyber Security
The Hacker News
The Hacker News
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
爱范儿
爱范儿
A
Arctic Wolf
L
LINUX DO - 最新话题
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Datadog | The Monitor blog

Reduce CVE noise with OpenVEX assessments in Datadog How we made a SQL query optimization agent 59% more accurate using autoresearch and LLM Observability How to audit and clean up monitors effectively Diagnose slow PostgreSQL queries faster with explain plan correlation Explore Datadog metrics with Natural Language Queries Attribute AI costs across providers with Datadog Cloud Cost Management Simplify micro-frontend observability with Datadog RUM Toto 2.0: Time series forecasting enters the scaling era Diagnose and resolve database performance issues faster with Database Investigator Datadog for Government achieves FedRAMP® High certification Analyze cloud costs with flexible spreadsheets in Datadog Sheets Inside Datadog’s AI Research Lab: Meet two PhD candidates behind Toto Connect triage and investigation in a single workflow with Datadog Cloud SIEM This Month in Datadog - April 2026 Monitor and optimize Supabase query performance with Datadog Database Monitoring Add dynamically updating context to logs with Reference Tables and Observability Pipelines Introducing ARFBench: A time series question-answering benchmark based on real incidents Test network paths with TCP, UDP, and ICMP in Datadog The product signal latency gap slowing your growth How to investigate cloud credential compromise with Bits AI Security Analyst Evaluate, optimize, and secure your Google Cloud AI stack with Datadog Turn developer feedback into operational insight with Datadog Forms and Sheets Identify and fix code issues faster with Datadog’s Azure DevOps Source Code integration Steganography at scale: Embedding share URLs in Datadog widget screenshots Bringing observability data hosting to the UK on AWS Centralize observability management with Datadog Governance Console Every team should be A/B testing Manage service tracing across hosts with Single Step Instrumentation rules Route OTel data from AI apps to ClickHouse and Datadog using Observability Pipelines Spotting CI/CD misconfigurations before the bots do: Securing GitHub Actions with Datadog IaC Security Detect runtime threats in Python Lambda functions with Datadog AAP Offline evaluation for AI agents: Best practices 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 How we built a real-world evaluation platform for autonomous SRE agents at scale 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 When upserts don't update but still write: Debugging Postgres performance at scale 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 Closing the verification loop: Observability-driven harnesses for building with agents Closing the verification loop, Part 2: Fully autonomous optimization When an AI agent came knocking: Catching malicious contributions in Datadog’s open source repos 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 Designing MCP tools for agents: Lessons from building Datadog's MCP server 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 Fine-tune Toto for turbocharged forecasts 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 How we reduced the size of our Agent Go binaries by up to 77% 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
Monitor Lustre with Datadog
2026-02-06 · via Datadog | The Monitor blog
Michael Cronk

Michael Cronk

Mahip Deora

Mahip Deora

High-performance computing (HPC) clusters rely on fast, reliable shared storage so that expensive CPU cores and GPUs aren’t left idle waiting for data. When bandwidth or I/O bottlenecks emerge, your workloads can slow down as your cluster spends more time on blocked reads, metadata lookups, and sync operations than actually computing. Parallel file systems like Lustre can deliver the aggregate bandwidth these workloads need, so keeping Lustre performing consistently is critical to getting full value from your HPC infrastructure.

Datadog’s Lustre integration gives you detailed visibility into your parallel file system under real workloads. Lustre telemetry data enables you to track file system and metadata operations (such as creates, renames, directory scans, and attribute updates), I/O throughput, and file system health. By monitoring metadata servers (MDSes), metadata targets (MDTs), object storage servers (OSSs), object storage targets (OSTs), and clients, HPC teams can detect bottlenecks, troubleshoot job slowdowns, and optimize storage performance across large-scale environments.

In this post, we’ll walk through how the integration helps you:

Many HPC workloads are metadata-heavy, which means metadata servers and targets often become the bottleneck for I/O performance. MDSes and MDTs create and traverse large directory trees, touch many small files, and frequently update file attributes. When MDSes are stressed, users can experience slow I/O even though CPU, GPU, and network metrics look healthy. In this section, you’ll see how the Datadog Lustre integration helps you monitor your cluster’s metadata activity and metadata pressure so you can detect bottlenecks before they affect users.

Analyze metadata usage

The integration collects core metadata metrics that describe activity in your Lustre file systems, including life cycle operations and attribute changes, as well as reads, seeks, and lookups. You can visualize these metrics by using an out-of-the-box (OOTB) Lustre dashboard, grouping by file system or metadata target to see where in your HPC cluster these activities are concentrated.

Datadog Lustre overview dashboard showing system health tiles and job statistics, including Lustre device health, network health, percent of total storage used, average write throughput, and time series charts of job write and read activity with a list of top jobs by write count.

In the following screenshot, the dashboard graphs the lustre.filesystem.read_bytes.sum and lustre.filesystem.write_bytes.sum metrics, which show a series of spikes in Lustre file system read and write activity. This pattern is common at the start of HPC workflows, when jobs scan directories and initialize input data. Sustained high read activity on a single file system can indicate concentrated access, helping explain slow directory listings and longer runtimes for jobs that traverse large directory trees.

Datadog metrics explorer view querying Lustre filesystem read and write bytes, displaying a multi-series line chart of read/write throughput over time grouped by Lustre device UUID, with a table of per-device metrics beneath the graph.

By monitoring these and other metrics, such as lustre.filesystem.mkdir.count and lustre.filesystem.openclosetime.count, storage teams can track activity and detect bottlenecks before they lead to job overruns, errors, or latency.

Track per-job metadata pressure

Metadata pressure is the strain placed on metadata servers by high-frequency file operations. When your workloads slow down due to metadata pressure, Datadog enables you to troubleshoot efficiently by correlating Lustre metrics with job scheduler data, host metrics, and telemetry data from other parts of your HPC stack.

For example, if users report that a research workflow hangs during certain stages, you may see a correlated increase in directory operations and metadata latency on a particular file system. You can filter to home in on specific jobs, then view their scheduler metrics to identify the root of the problem. If a single job creates a large number of files, you may see rising scheduler latency (such as in your Slurm integration metrics) even if your resource utilization metrics are flat.

Correlating metadata pressure with individual jobs can inform your mitigation and tuning efforts. For example, it can show you when to change directory layouts, adjust striping patterns and file-per-process patterns, or update scheduler policies so fewer metadata-heavy jobs run at the same time.

Troubleshoot job slowdowns

Your cluster’s I/O throughput is a major factor in the performance of your workloads. When Lustre can’t deliver data fast enough, jobs can spend more time waiting on reads and writes than they do computing. Bottlenecks like this can be caused by limited bandwidth, uneven I/O across a few hot OSTs, or high latency.

Datadog’s Lustre integration surfaces cluster-wide and per-file system throughput metrics to help you spot bottlenecks and saturation. Tracking read and write throughput, operation counts, and latency helps you identify file systems or OSTs that are overloaded. This can also help you spot periods when the cluster isn’t using available bandwidth effectively. The OOTB Lustre dashboard makes it easy to see which file systems or OSTs are approaching saturation and whether utilization is balanced or skewed toward specific targets or clients.

Job Statistics data on the Datadog Lustre overview dashboard with timeseries graphs for job write activity and job read activity, alongside a bar chart ranking top jobs by write count, illustrating how individual jobs contribute to overall Lustre I/O.

Lustre job statistics metrics (lustre.job_stats.*) give you a per-job view of file system behavior. For each job, you can see:

  • Read and write operation counts and latency
  • Bytes read and written over the life of the job
  • Other I/O operations such as creating and renaming files and directories

This visibility into Lustre job stats helps you efficiently troubleshoot job slowdowns. For example, a training job that seems CPU-bound may actually be issuing many small random reads to a narrow set of OSTs, or a noisy neighbor job may be driving most of the I/O on a busy file system. With Datadog, you can identify the specific cause of the problem by its unique job ID so you can target your mitigations based on data instead of guesses.

By enabling you to correlate your Lustre job stats with host, GPU, network, and scheduler metrics, Datadog helps you see whether job slowdowns are caused by storage issues or, for example, resource starvation. This helps you better understand how workloads use Lustre so you can optimize storage performance by tuning striping patterns, rebalancing data, or revising applications to improve their I/O patterns.

Monitor storage and network health at scale

To keep a large Lustre deployment healthy, you need more than metadata and throughput metrics—you also need to know whether your file system components, capacity, and network are performing as expected. Datadog’s Lustre integration tracks total and available capacity per file system and health status of OSTs and MDTs. This lets teams plan for growth before they hit capacity limits, avoid overfilling specific pools, and balance workloads across available storage. It also helps you detect uneven capacity usage, when some file systems are nearly full while others have plenty of space available.

Datadog also collects metrics that show what’s happening on your storage servers and network. When users report slow I/O or jobs running longer than expected, OSS metrics help you quickly spot issues with queue depth or buffer availability. LNET metrics let you track interface throughput and correlate spikes in errors or retransmissions with drops in throughput to understand whether storage or the network is limiting performance. Because Datadog provides visibility across your environment, you can correlate Lustre health with host metrics, GPU monitoring, and network performance to see whether a problem originates in storage, compute, or the network and respond accordingly.

Monitor changelog events

In multi-tenant environments, understanding how data changes can be as important as tracking capacity. The Lustre integration can consume changelog events as structured logs, capturing operations such as file creates, deletes, and renames. Combined with metrics, Lustre changelog events help you identify high-churn directories and spot patterns that may lead to capacity issues. It also gives you crucial context when you need to investigate unexpected data movement or deletion.

Datadog Log Explorer filtered to Lustre logs, showing a stacked bar chart of log volume over time and a table of individual log events with timestamps, hosts, services, and message text, used to analyze Lustre changelog activity.

Gain end-to-end observability for Lustre in your HPC stack

Lustre plays a critical role in keeping HPC clusters productive. Datadog’s Lustre integration gives you visibility into file system and metadata operations, throughput, and file system health so you can detect bottlenecks, troubleshoot job slowdowns, and reduce storage-related job delays.

Because Lustre telemetry data sits alongside Slurm metrics, host and GPU monitoring, and network observability in Datadog, teams across storage, HPC operations, and applications can rely on a shared, consistent view of how their workloads are using the cluster. See the Lustre integration documentation for more information. If you’re not yet using Datadog, start today with a 14-day free trial.