Kentik announced general availability of Kentik Map for Azure and extensive support for Microsoft Azure infrastructure in Kentik Cloud.
With this release, Kentik provides comprehensive network observability across all multi-cloud deployments, and gives network, cloud, and infrastructure engineers the context to rapidly answer any question about their networks.
Enterprises use Kentik Cloud to optimize performance, resolve network incidents, reduce cloud costs, and maximize ROI of migrations to Azure, Google Cloud, and AWS. These latest Azure enhancements follow the recently announced release of Kentik Map for Google Cloud, underscoring Kentik's command of network observability for hybrid and multi-cloud environments.
Kentik Map for Azure visualizes Azure infrastructure in an interactive, data- and context-rich map that highlights how Azure resources nest within each other and connect to on-prem environments. Additionally, Kentik now collects, analyzes, and contextualizes traffic flow and performance data from Microsoft Azure along with data from on-prem, Google Cloud, and AWS services, enriching all network telemetry with deep application, business, and security context to provide actionable observability across all hybrid and multi-cloud environments. Organizations can now:
- Reference live visualizations of Azure infrastructure topology in Kentik Map for Azure, with both current and historical views of paths and detailed metadata
- Quickly understand path and performance details of traffic routes that connect Microsoft Azure workloads to data centers across Azure Express Routes
- Visualize and interrogate traffic across Azure Firewalls, Load Balancers, Application Gateways, and other network infrastructure
- Visualize and interrogate all branch, VPN, private cloud, and intra-cloud connectivity that is connected with Azure VWAN
- Drill into the impact of NSG (Network Security Group) configuration on security and productivity with live traffic data
- Use custom tags to add any custom context to Microsoft Azure data along with pre-built Azure-native attributes sourced from Azure APIs
- Create custom dashboards with configurable pre-built widgets to visualize important Azure cost and performance trends
"Legacy NPM and observability tools are simply not able to provide the visibility that enterprises need to understand the impact of traffic flows and performance on customer experiences," said Christoph Pfister, Chief Product Officer, Kentik. "By unifying all network telemetry, across all clouds and data centers, Kentik's latest advancements enable enterprises to make data-driven decisions, optimize resource utilization, and achieve peak performance and security for their hybrid and multi-cloud infrastructure."
The Latest
IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...