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

推荐订阅源

酷 壳 – 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 Toto 2.0: Time series forecasting enters the scaling era Simplify micro-frontend observability with Datadog RUM Attribute AI costs across providers with Datadog Cloud Cost Management 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 The product signal latency gap slowing your growth Test network paths with TCP, UDP, and ICMP in Datadog Turn developer feedback into operational insight with Datadog Forms and Sheets How to investigate cloud credential compromise with Bits AI Security Analyst Evaluate, optimize, and secure your Google Cloud AI stack with Datadog Bringing observability data hosting to the UK on AWS Identify and fix code issues faster with Datadog’s Azure DevOps Source Code integration Steganography at scale: Embedding share URLs in Datadog widget screenshots Every team should be A/B testing Centralize observability management with Datadog Governance Console Spotting CI/CD misconfigurations before the bots do: Securing GitHub Actions with Datadog IaC Security Route OTel data from AI apps to ClickHouse and Datadog using Observability Pipelines Manage service tracing across hosts with Single Step Instrumentation rules Offline evaluation for AI agents: Best practices Detect runtime threats in Python Lambda functions with Datadog AAP 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 When an AI agent came knocking: Catching malicious contributions in Datadog’s open source repos Closing the verification loop, Part 2: Fully autonomous optimization 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
From performance to impact: Bridging frontend teams through shared context
2025-12-15 · via Datadog | The Monitor blog

Connecting day-to-day development work to real user outcomes can be challenging. As a result, engineers and product teams often struggle to effectively prioritize projects together. While the goal of improving user experience (UX) is the same, each team relies heavily on different—and often siloed—forms of monitoring to understand their app, creating a disconnect in metrics and visualizations that can be hard to communicate.

To gain a full picture of their app’s UX, both teams need a deep understanding of how users are responding to version changes, errors, or performance issues. Achieving this means translating each team’s key goals, concerns, and findings into a common language.

In this post, we’ll explore strategies for combining real user monitoring (RUM) and product analytics to:

How frontend teams define success

Engineering and product teams often envision the optimal state of their app differently, which is reflected in the tools and metrics they use.

For frontend engineering teams, success is defined in terms of system performance. Their main goal is to identify and remediate issues before they cause significant user impact. They consider performance issues to be the main cause of a negative experience and look to metrics like Core Web Vitals, error rates, and frustration signals to assess UX. As a result, they are most interested in tools that use these metrics to help them detect technical problems, pinpoint where they occur, and evaluate user impact, including:

On the other hand, product teams are primarily concerned with user engagement and discoverability. Their main goal is to determine which aspects of their app are driving or reducing user activity. They spend much of their time deciding which projects to prioritize, particularly when predicting how design changes or performance optimizations might impact engagement.

To quantify success in concrete data, product teams look at overall conversion and retention rates for a big-picture view. They may also look at more granular indicators of user engagement, such as how long users stay on a page, how much they spend per session, and how often they interact with key elements like checkout buttons. The tools these teams use tend to depict trends in user activity, including:

  • Funnels that depict dropoff at each step of the user journey
  • Pathway diagrams that show the most popular journeys within an app
  • Experiments that measure the viability of projects in terms of business goals such as revenue

Ultimately, the disconnect between product and engineering teams tends to stem from a lack of a shared context. Siloed metrics and disparate tools prevent them from connecting their perspectives for more informed goal setting and troubleshooting. For example, frontend engineering teams may view a feature that results in faster loading times as a clear success. However, product teams may see the same project as a failure if it doesn’t improve conversion rates. By combining data, teams can more easily collaborate on and prioritize projects that lead to success from both perspectives—that is, ones that improve performance in areas with the greatest impact on user engagement.

Combining RUM and product analytics for complete visibility

For engineering and product teams to make decisions together, they need a unified understanding of what users are doing and seeing within their app. Bringing together RUM and product analytics tools enables these teams to connect performance troubleshooting and optimization to end-user outcomes. By drawing from the same source of truth, they can more easily collaborate on decision making and effectively prioritize projects based on their impact on user experience.

To do this, they need to first establish a shared vocabulary for key user actions. Without consistent definitions, teams often end up interpreting the same behavior differently, slowing down investigations and making it hard to align on priorities. To help your organization develop a single, universal dataset, Datadog automatically captures user actions, labels them, and populates them across both Datadog Product Analytics and Datadog RUM. This means that every team uses the same common reference points and can more effectively communicate with each other. Product Analytics also comes with a no-code Action Management interface—currently in Preview—that enables teams to create reusable action names, allowing product managers to directly customize this dataset and reducing engineering overhead.

A user labelling an action by selecting it within their app's interface.

From here, sharing analytics through monitoring tools helps both teams evaluate the effectiveness of their projects from multiple perspectives. Let’s say that you belong to a product team that has recently released a redesign of your website. Soon after rollout, you receive an alert about a sharp increase in frustration signals. You pivot to a funnel within Datadog Product Analytics, enter the steps for your most common user flow, and quickly spot that your enrollment page now has a higher than expected drop-off rate. By clicking into the funnel step for this page, you can view a list of dropped-off sessions that contain frustration clicks.

The funnel analysis window for a step with significant dropoff, with a list of relevant sessions displayed.

You view a session replay for this page and identify an unresponsive enroll button that caused users to abandon their sessions. You send this replay to your engineering teams, who can pivot directly from the replay to performance diagnostic data within Datadog RUM.

A replay for a session that involved frustration clicks.
A replay for a session that involved frustration clicks.
A replay for a session that involved frustration clicks.

Alternatively, engineering teams can easily view the impact of their changes through unified data. If you’re an engineer who’s recently completed performance optimizations for your app, you can view user engagement trends within Product Analytics to determine the impact of these changes. For example, you may want to determine whether there’s been an increase in checkout completion events following your optimizations. If you do see a marked improvement, you can send these results to your product teams to communicate that this is a critical project worth investing in further.

Start connecting user experience to product outcomes

When teams share visibility into software performance and user engagement, engineers see the real impact of their work and product teams gain empathy for technical challenges. By bridging their data, frontend teams can easily assess how every release shapes the user journey.

You can learn more about using Datadog RUM and Product Analytics together in our recent case study with Ibnsina Pharma. You can also read our documentation to start monitoring performance with RUM and user engagement with Product Analytics. Or, if you’re new to Datadog, you can sign up for a 14-day free trial.