Service Graph

The service graph feature in NetScaler Console enables you to monitor all Kubernetes services in a graphical representation. This feature also enables you to view a detailed analysis and actionable metrics of the services. Navigate to Applications > Service Graph to view service graph for:

• Applications configured across all NetScaler instances

• Kubernetes applications

• 3-tier Web applications

Service graph for applications across all NetScaler instances

The global service graph feature enables you to get a holistic visualization of the clients to infrastructure to application view. From this single-pane service graph view, as an administrator, you can:

• Understand from which region the users are accessing the specific applications (3-tier Web apps and microservices app)
• Visualize the infrastructure (NetScaler instance) view that the client request is processed
• Understand if the issues are occurring from the client, infrastructure, or application
• Further drill down to troubleshoot the issue

Navigate to Applications > Service Graph and click the Global tab to view:

• End-to-end details of all applications connected from client to back-end servers

• All NetScaler instances that are connected to its respective data centers

  Note

  You can view data centers only if you have GSLB apps.

• The client metrics information

• The NetScaler metrics information

• All NetScaler instances that have discrete applications, custom applications, and discrete microservice applications

• The top 4 low-scored applications that belong to custom apps, discrete apps, and microservices apps

• The metrics information for the top 4 low-scored virtual servers

• The applications (discrete apps, custom apps, and microservices apps) status such as Critical, Review, Good, and Not Applicable.

For more information, see Holistic view of applications in service graph.

Service graph for Kubernetes applications

Navigate to Applications > Service Graph and click the Microservices tab to:

• Ensure end-to-end application overall performance

• Identify bottlenecks created by inter-dependency of different components of your applications

• Gather insights into the dependencies of different components of your applications

• Monitor services within the Kubernetes cluster

• Monitor which service has issues

• Check the factors contributing to performance issues

• View detailed visibility of service HTTP transactions

• Analyze the HTTP, TCP, and SSL metrics

• View client metrics and client transaction summary details

By visualizing these metrics in NetScaler Console, you can analyze the root cause of issues and take necessary troubleshooting actions faster. Service graph displays your applications into various component services. These services running inside the Kubernetes cluster can communicate with various components within and outside the application. To get started, see Setting up service graph.

Service graph for 3-tier Web applications

Navigate to Applications > Service Graph and click the Web Apps tab to view:

• Details on how the application is configured (with content switching virtual server and load balancing virtual server)

  For GSLB applications, you can view data center, NetScaler instance, CS, and LB virtual servers.

• End-to-end transactions from client to service

• The location from where the client is accessing the application

• The data center name where the client requests are processed and the associated data center NetScaler metrics (only for GSLB applications)

• Metrics details for client, service, and virtual servers

• If the errors are from the client or from the service

• The service status such as Critical, Review, and Good. NetScaler Console displays the service status based on service response time and error count.

  • Critical (red) - Indicates when average service response time > 200 ms AND error count > 0

  • Review (orange) - Indicates when average service response time > 200 ms OR error count > 0

  • Good (green) - Indicates no error and average service response time < 200 ms

• The client status such as Critical, Review, and Good. NetScaler Console displays the client status based on client network latency and error count.

  • Critical (red)- Indicates when average client network latency > 200 ms AND error count > 0

  • Review (orange) - Indicates when average client network latency > 200 ms OR error count > 0

  • Good (green) - Indicates no error and average client network latency < 200 ms

• The virtual server status such as Critical, Review, and Good. NetScaler Console displays the virtual server status based on the app score.

  • Critical (red) - Indicates when app score < 40

  • Review (orange) - Indicates when app score is between 40 and 75

  • Good (green) - Indicates when app score is > 75

Points to note:

• Only Load Balancing, Content Switching, GSLB virtual servers are displayed in service graph.

• If no virtual server is bound to a custom application, the details are not visible in service graph for the application.

• You can view metrics for clients and services in service graph only if active transactions occur between virtual servers and web application.

• If no active transactions available between virtual servers and web application, you can only view details in service graph based on the configuration data such as load balancing, content switching, GSLB virtual servers, and services.

• If any changes made in the application configuration, it may take 10 minutes to reflect in service graph.

For more information, see Service graph for applications.