Current View
File name:

-

File size:

-

Title:

-

Author:

-

Subject:

-

Keywords:

-

Creation Date:

-

Modification Date:

-

Creator:

-

PDF Producer:

-

PDF Version:

-

Page Count:

-

Page Size:

-

Fast Web View:

-

Preparing document for printing…
0%
Troubleshoot Web Service Issues and Eliminate Visibility Gaps in Virtual Load Balancing Environments NetOps and application teams can learn how vSTREAM virtual appliances and nGeniusONE helped trace an HTTP 404 error to a virtual load balancer in a hybrid cloud environment. The use case shows how packet-level monitoring on both sides of a load balancer restored customer access to an e-commerce web portal. What problem did the company face? Customers could not log in to the company's web portal, so they could not order products, update profiles, or track shipments. The e-commerce application was split-hosted, with databases in a colocation facility and front-end and back-end services in Oracle Cloud, and the failure came during a seasonal surge in sales. Lost orders, customer churn, and reputational harm were the risks. How did IT add visibility? IT leadership expanded its nGenius Enterprise Performance Management investment with the following setup: • vSTREAM virtual appliances on both sides of the virtual load balancers in a VMware virtual machine within Oracle Cloud • An nGeniusONE server in a colocation data center using packet-based Smart Data from vSTREAM • Web Services Monitor views of traffic across the load balancer interfaces • Session Trace data showing hop-by-hop analysis on both sides of the load balancer How was the 404 error resolved? The Web Services Monitor showed application and timeout errors in Oracle Cloud, and Session Trace revealed a 404 PAGE NOT FOUND error. The team traced it to a third-party virtual load balancer that routed traffic improperly after an Oracle Cloud update. IT updated the load balancer's routing configuration, customers regained access, and the team kept monitoring in nGeniusONE to confirm the problem did not return. Frequently Asked Questions What does an HTTP 404 error mean in this use case? A 404 error means a web server could not find the requested resource or page. In load balancing environments, HTTP status codes such as 404, 500, and 502 are diagnostic details that can indicate network, server, or workload disruptions. What does Web Services Monitor show? It sorts and counts message IDs for requests and failures and measures average response time, so teams can monitor the health and performance of web services. Asset Type: Use Case

About this content