Google Cloud Network Load Balancer Monitoring Integration
Get the best out of your Google Cloud Network Load Balancer service by integrating Site24x7 monitoring. Know how much traffic your load balancers handle, monitor packet counts, latency metrics, and connection statistics to optimize your cloud infrastructure.
Setup and configuration
- Adding Google Cloud Network Load Balancer while configuring a new Google Cloud monitor
If you have not configured a Google Cloud monitor yet, add one by following the steps below:
- Log in to your Site24x7 account.
- Go to Cloud > GCP > Add GCP Monitor or Admin > Cloud Monitoring > Google Cloud Platform(GCP).
- Provide a unique display name for identification purposes.
- Upload a service account JSON file to authenticate Site24x7 for performing resource discovery.
- Select Network Load Balancer from the Select the Resources for Monitoring list.
- Select existing Notification Profiles, User Alerts Groups, Tags, and IT Automation Templates or add new ones. You can also integrate Site24x7's alarms with your preferred third-party service.
- Click Start GCP Monitoring.
- Adding Google Cloud Network Load Balancer to an existing Google Cloud monitor
If you already have a Google Cloud monitor configured for the service account, you can add Google Cloud Network Load Balancer by following the steps below:
- Log in to your Site24x7 account.
- Go to Cloud > GCP and select your GCP monitor.
- Click the hamburger
icon next to Service View and select Edit, which brings you to the Edit GCP Monitor page.
- On the Edit GCP Monitor page, select Network Load Balancer from the Select the Resources for Monitoring list and click Save.
- After successful configuration, go to Cloud > GCP > Network Load Balancer. Now you can view the discovered Google Cloud Network Load Balancer resources.
It will take approximately five minutes to discover new GCP resources.
Polling frequency
Site24x7's Google Cloud Network Load Balancer monitor collects minute-wise metric data, and the statuses of your Google Cloud Network Load Balancer are reported every five minutes.
Supported metrics
The metrics are organized by load balancer type (L3, L4 proxy, and TCP/SSL proxy) for better readability.
L3 Load Balancer Metrics
Metric name |
Description |
Statistic |
Unit |
Egress bytes count |
The number of bytes sent from the external network load balancer to the client. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Egress packets count |
The number of data packets sent from the external network load balancer to the client. |
Average |
Count |
Ingress bytes count |
The number of bytes sent from the client to the external network load balancer. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Ingress packets count |
The number of data packets sent from the client to the external network load balancer. |
Average |
Count |
RTT latencies |
The average round trip time (RTT) latency measure across TCP connections. |
Average |
Milliseconds |
Egress bytes per internal TCP/UDP load balancer |
The number of bytes sent from the internal TCP/UDP load balancer to the client. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Egress packets per internal TCP/UDP load balancer |
The number of data packets sent from the internal network load balancer to the client. |
Average |
Count |
Ingress bytes per internal TCP/UDP load balancer |
The number of bytes sent from the client to the internal TCP/UDP load balancer. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Ingress packets per internal TCP/UDP load balancer |
The number of data packets sent from the client to the internal network load balancer. |
Average |
Count |
RTT latencies per internal TCP/UDP load balancer |
The average round trip time (RTT) latency across all TCP connections for internal TCP/UDP load balancer flows. |
Average |
Milliseconds |
Proxy-only addresses |
The number of proxy-only addresses segregated by state, active at the time of data collection. |
Average |
Count |
L4 Proxy Load Balancer Metrics
Metric name |
Description |
Statistic |
Unit |
Egress bytes count |
The number of bytes sent from the external network load balancer to the client. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Ingress bytes count |
The number of bytes sent from the client to the external network load balancer. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Closed connections |
The total number of connections that were terminated over TCP/SSL proxy load balancer. |
Total |
Count |
New connections |
The total number of connections that were created over TCP/SSL proxy load balancer. |
Total |
Count |
Proxy-only addresses |
The number of proxy-only addresses segregated by state, active at the time of data collection. |
Average |
Count |
TCP/SSL Proxy Load Balancer Metrics
Metric name |
Description |
Statistic |
Unit |
Egress bytes count |
The number of bytes sent from the external network load balancer to the client. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Ingress bytes count |
The number of bytes sent from the client to the external network load balancer. In case of TCP flow, this metric shows the number of bytes on the application stream. |
Average |
Count |
Closed connections |
The total number of connections that were terminated over TCP/SSL proxy load balancer. |
Total |
Count |
New connections |
The total number of connections that were created over TCP/SSL proxy load balancer. |
Total |
Count |
Proxy-only addresses |
The number of proxy-only addresses segregated by state, active at the time of data collection. |
Average |
Count |
Frontend RTT |
The average round trip time (RTT) latency measured by the proxy's TCP stack. |
Average |
Milliseconds |
Open connections |
The number of outstanding connections through the TCP/SSL proxy load balancer |
Total |
Count |
Threshold configuration
- Global configuration
- In the Site24x7 web client, go to the Admin section on the left navigation pane.
- Select Configuration Profiles from the left pane and select Threshold and Availability from the drop-down menu.
- Click Add Threshold Profile in the top-right corner.
- For Monitor Type, select Network Load Balancer.
- Now you can set the threshold values for the metrics listed above.
- Monitor-level configuration
- In the Site24x7 web client, go to Cloud > GCP > Network Load Balancer.
- Select a resource you would like to set a threshold for, then click the hamburger
icon.
- Select Edit, which directs you to the Edit Network Load Balancer Monitor page.
- You can set the threshold values for the metrics with the Threshold and Availability option.
- You can also configure IT Automation at the attribute level.
IT Automation
Site24x7 offers a set of exclusive IT Automation tools that automatically resolve performance degradation issues. These tools react to events proactively rather than waiting for manual intervention. The IT Automation tools automate repetitive tasks and automatically remediate threshold breaches. The alarm engine continually evaluates system events for which thresholds are set and executes the mapped automation when there is a breach.
How to configure IT Automation for a monitor
Configuration Rules
Editing multiple monitors to associate different monitor groups or add a different tag can be a tedious process. With Site24x7's Configuration Rules, you can automate the configuration settings of your monitoring resources. Also, Site24x7 allows you to create custom rules to track configuration changes continuously and achieve the ideal configuration settings.
How to add Configuration Rules
Summary
The Summary tab will give you the performance data organized by time for the metrics listed above. To view the summary:
- Go to Cloud > GCP > Network Load Balancer.
- Select a resource.
- Click the Summary tab.
Configuration Details
The Configuration Details tab provides details on the configurations of application instances. To get the configuration details:
- Go to Cloud > GCP > Network Load Balancer.
- Select a resource.
- Click the Configuration Details tab.
Reports
Gain in-depth data about the various parameters of your monitored resources and accentuate your service performance using our insightful reports.
To view reports for a Google Cloud Network Load Balancer resource:
- Go to the Reports section on the left navigation pane.
- Select Network Load Balancer from the menu on the left.
- You can find the Availability Summary Report, Performance Report, and Inventory Report for one selected monitor. Or you can get the Summary Report, Availability Summary Report, Health Trend Report, and Performance Report for all the Google Cloud Network Load Balancer monitors.
You can also get reports from the Summary tab of the Google Cloud Network Load Balancer monitor:
- Click the Summary tab.
- Get the Availability Summary Report of the monitor by clicking Availability.
- You can also find the Performance Report of the monitor by clicking any chart title.
Related content
- Monitoring Google Cloud Platform
- List of Google Cloud services supported for monitoring
- Possible reasons why GCP resources are not added for monitoring in Site24x7
- What permissions should I have in my Google account to enable Site24x7's Google Cloud Platform (GCP) monitoring?
- How to create a service account JSON file to authenticate Site24x7 for the discovery of GCP resources
- How to create a service account in the GCP console