EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

How to View Environment Load Balancer Details


Umar Ghazi

Software Engineer, Senior • MicroStrategy


The Load Balancer information is now available in the Environment details section of each environment. In addition to viewing information about your instances, you can now also view metrics about your load balancers and register/deregister instances from the load balancers.

This guide will show you how to manage the load balancers on your environment. It covers the following topics:

Using the Load Balancers
How Load Balancers Affect Your Environment
Load Balancer Metrics
 

Using the Load Balancers

The following steps will show you how to register/deregister your Server Instance and other ports from the Application Load Balancer:

  • Click the blue plus button to expand the environment details
     
ka044000000kQtMAAU_0EM44000000R0VA.png
  • Under the Server tab, click Application Load Balancer. If you have an environment with multiple instances, they will be divided among 3 categories. Server instances will be under the Server tab, Developer instances will be under the Developer tab, and Metadata instances will be in the Metadata tab. By default, the Server tab will be expanded and other tabs can be expanded to reveal their respective instances and load balancers.
     
ka044000000kQtMAAU_0EM44000000R0VP.png
ka044000000kQtMAAU_0EM44000000R0VU.png
  • Under Connected Instances, click on Ports: 8443 to view the Server Instance
ka044000000kQtMAAU_0EM44000000R0VZ.png
  • Click the 3 dots to the right and click Deregister. The instance will soon be deregistered from the Application Load Balancer.
     
ka044000000kQtMAAU_0EM44000000R0Vo.png
  • When an instance is deregistered from the Application Load Balancer, it will show as ‘unhealthy.’ When it is deregistered from the Elastic Load Balancer, it will show as ‘OutOfService.’ Both of these states will be indicated by a yellow triangle with an exclamation mark, as seen in the screenshot below.
ka044000000kQtMAAU_0EM44000000R0Vy.png
  • Clicking on Other Ports reveals 3 other ports. Follow the same process as step 4 to register or deregister them as needed. You can also click on the 3 dots next to the group names to register/deregister everything in that group.
ka044000000kQtMAAU_0EM44000000R0W8.png
  • The same steps above can be followed to register or deregister other instances from both the Application Load Balancer and the Elastic Load Balancer.
ka044000000kQtMAAU_0EM44000000R0WD.png


 

How Load Balancers Affect Your Environment

Disconnecting ports or instances from your load balancers on your environment will cause loss of access to certain services. The below tables highlight which parts of your environment you will lose access to if you disconnect the corresponding port or instance:
Application Load Balancer

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

Elastic Load Balancer

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

Load Balancer Metrics

There are several metrics about your load balancers that can be viewed in the Environment Details section of your environment. They show specific details about the health and status of your load balancers. Metrics are derived directly from AWS and are updated every 5 minutes. All metrics are shown as averages over the 5 minute period. Refer to the below table for descriptions of each metric, taken directly from AWS.
Application Load Balancer

52.4 MB 
Port 8443Controls Web, Landing Page, and LibraryPort 1443Controls Usher Network ManagerPort 2443Controls Usher 1 Way IDMPort 3000Controls Usher ServicesServer InstanceControls Usher 2 Way IDM & Usher GatewayDeveloper InstanceControls RDP access to Developer BoxRequest Count

The number of requests processed over IPv4 and IPv6. This count includes only the requests with a response generated by a target of the load balancer.
Processed Bytes

The number of requests processed over IPv4 and IPv6. This count includes only the requests with a response generated by a target of the load balancer.
Processed Bytes

The total number of bytes processed by the load balancer over IPv4 and IPv6.
Active Connection Count

The total number of bytes processed by the load balancer over IPv4 and IPv6.
Active Connection Count

The total number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.
Target Response Time

The total number of concurrent TCP connections active from clients to the load balancer and from the load balancer to targets.
Target Response Time

The time elapsed, in seconds, after the request leaves the load balancer until a response from the target is received.
New Connection Count

The time elapsed, in seconds, after the request leaves the load balancer until a response from the target is received.
New Connection Count

The total number of new TCP connections established from clients to the load balancer and from the load balancer to targets.
Consumed Load Balancer Capacity Units

The total number of new TCP connections established from clients to the load balancer and from the load balancer to targets.
Consumed Load Balancer Capacity Units

The number of load balancer capacity units (LCU) used by your load balancer. You pay for the number of LCUs that you use per hour.
Request Count                         

Elastic Load Balancer

The number of load balancer capacity units (LCU) used by your load balancer. You pay for the number of LCUs that you use per hour.
Request Count                         

The number of requests processed over IPv4 and IPv6. This count includes only the requests with a response generated by a target of the load balancer.
Latency[TCP listener] The total time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.Healthy Host Count

The number of requests processed over IPv4 and IPv6. This count includes only the requests with a response generated by a target of the load balancer.
Latency[TCP listener] The total time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.Healthy Host Count

The number of requests processed over IPv4 and IPv6. This count includes only the requests with a response generated by a target of the load balancer.
Latency[TCP listener] The total time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.Healthy Host Count

The number of requests processed over IPv4 and IPv6. This count includes only the requests with a response generated by a target of the load balancer.
Latency[TCP listener] The total time elapsed, in seconds, for the load balancer to successfully establish a connection to a registered instance.Healthy Host Count

The number of targets that are considered healthy.

To learn more about load balancer metrics, refer to the following AWS documentation:
Application Load Balancer Metrics: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html
Elastic Load Balancer Metrics: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/elb-metricscollected.html


Comment

0 comments

Details

Blog Post

Published:

October 11, 2018

Last Updated:

November 2, 2018