Dynatrace Blog

IT modernization planning for Federal agencies spans multi-year cycles: platform decisions made at a point in time must sustain through implementation timelines and evolving technologies. A vendor may be certified today, but will their technology still meet an agency’s requirements when a program reaches full operating capability tomorrow? Federal agencies are modernizing through hybrid cloud transformation and AI adoption while threat actors are using AI to accelerate attack velocity.

If you want to see them in action, head over to our Release Radar launchpad on the Dynatrace Playground. Smartscape gets a unified topology view and ad-hoc filters In a significant Smartscape® update, a new All topology view shows every relationship for a given node in a single graph: the infrastructure stack, communication flows, and relationships such as monitoring, load balancing, routing, and API dependencies.

Here’s the uncomfortable truth: organizations are spending billions on cloud migrations, yet many fail to deliver the promised ROI. Why? Because moving workloads to the cloud without addressing operational visibility, runaway costs, and fragmented tooling multiplies the problem.

I think a lot of developers are quietly afraid right now. Not because AI is going to replace them any time soon. Most experienced developers don’t actually believe that. The fear is more subtle than that. They’re afraid of getting left behind, learning the wrong tools or building the wrong way. Afraid that younger developers are adapting faster or that others understand all of this better. I feel that pressure too. I use Claude® Code CLI constantly. Every day.

Enterprise AI is rapidly evolving from standalone models to agentic AI systems, where multiple AI agents collaborate to gather information, reason across data sources, and generate complex outputs. These systems unlock powerful new capabilities, but they also introduce significant operational challenges. Organizations must be able to observe, govern, and optimize AI agents, models, and infrastructure in real time.

Kubernetes Security Posture Management (KSPM) is a specialized subset of Security Posture Management (SPM) that focuses on container orchestration platforms. Its main purpose is to identify misconfigurations and compliance gaps across clusters. Here are the latest enhancements: KSPM is turned on by default during Kubernetes cluster onboarding Security findings are surfaced directly in the Kubernetes app Node Configuration Collector (NCC) occurs automatically via the Dynatrace Operator.

Dynatrace extends HIPAA compliance to Google Cloud Platform Dynatrace has long supported HIPAA‑compliant deployments on Amazon Web Services (AWS) and Microsoft Azure. With the extension of HIPAA compliance to Google Cloud Platform (GCP), healthcare organizations in the United States can now standardize observability and security controls across all three major hyperscalers.

This is the second post in our series on LLM evaluations. In the companion post, Evaluate LLM and agent quality in Dynatrace AI Observability with dt-evals, we showed you how to run online evaluations against real GenAI prompt traces and bring quality scores into Dynatrace AI Observability alongside latency, cost, and errors. This post steps back to the fundamentals: what evaluations are, how they work, and the methods teams use to measure AI quality.

AI is stretching the boundaries of traditional log management. More data without context slows insight, increases risk, and stalls AI progress. Teams need to rethink how they capture, process, and use telemetry from ingest to analysis. This action plan outlines how to unify telemetry, optimize pipelines, and turn data into real‑time, trusted intelligence teams can use to scale AI operations with confidence.

At Dynatrace, we believe the future of observability and cloud-native operations is open. Not “open” as a slide-deck buzzword, but open as in showing up every day to write code, review PRs, chair working groups, and build tools the community can use, extend, and make their own. We’re proud to be an active contributor to the cloud-native ecosystem. We build in the open because we’ve seen firsthand that open collaboration produces better software for our customers, the community, and the industry.