Table: azure_lb - Query Azure Load Balancers using SQL
Azure Load Balancer is a high-performance, ultra low-latency Layer 4 load balancing service for all UDP and TCP protocols. It enables you to build highly scalable and highly available applications by providing automatic routing of network traffic to virtual machines. This service also provides health probes to detect the failure of an application on a virtual machine.
Table Usage Guide
The azure_lb
table provides insights into Load Balancers within Azure. As a Network Administrator, explore Load Balancer-specific details through this table, including configuration, location, and operational status. Utilize it to uncover information about Load Balancers, such as their health status, associated resources, and traffic routing rules.
Examples
Basic info
Explore which Azure Load Balancer resources are currently being provisioned in different regions. This is useful for managing and optimizing geographically distributed resources.
select id, name, type, provisioning_state, etag, regionfrom azure_lb;
select id, name, type, provisioning_state, etag, regionfrom azure_lb;
List failed load balancers
Determine the areas in which load balancers have failed within your Azure environment. This can aid in troubleshooting and improving the reliability of your network infrastructure.
select id, name, type, provisioning_statefrom azure_lbwhere provisioning_state = 'Failed';
select id, name, type, provisioning_statefrom azure_lbwhere provisioning_state = 'Failed';
Query examples
- compute_virtual_machine_scale_set_network_interfaces_for_network_load_balancer
- compute_virtual_machine_scale_set_vms_for_network_load_balancer
- compute_virtual_machines_for_network_load_balancer
- load_balancer_frontend_ip_configurations
- load_balancer_inbound_nat_rules
- load_balancer_load_balancing_rules
- load_balancer_outbound_rules
- load_balancer_probe
- network_load_balancer_backend_address_pools_for_network_load_balancer
- network_load_balancer_backend_pool_count
- network_load_balancer_backend_pools
- network_load_balancer_rules_count
- network_load_balancer_sku_name
- network_load_balancer_sku_tier
- network_load_balancer_tags
- network_load_balancers_for_compute_virtual_machine
- network_load_balancers_for_compute_virtual_machine_scale_set
- network_load_balancers_for_compute_virtual_machine_scale_set_vm
- network_load_balancers_for_network_public_ip
- network_load_balancers_for_network_virtual_network
- network_load_nat_rules_count
- network_load_probes_count
- network_network_interfaces_for_network_load_balancer
- network_public_ips_for_network_load_balancer
- network_virtual_networks_for_network_load_balancer
Control examples
Schema for azure_lb
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
akas | jsonb | Array of globally unique identifier strings (also known as) for the resource. | |
backend_address_pools | jsonb | Collection of backend address pools used by the load balancer. | |
cloud_environment | text | The Azure Cloud Environment. | |
diagnostic_settings | jsonb | A list of active diagnostic settings for the load balancer. | |
etag | text | A unique read-only string that changes whenever the resource is updated. | |
extended_location_name | text | The name of the extended location. | |
extended_location_type | text | The type of the extended location. Possible values include: 'ExtendedLocationTypesEdgeZone'. | |
frontend_ip_configurations | jsonb | Object representing the frontend IPs to be used for the load balancer. | |
id | text | The resource ID. | |
inbound_nat_pools | jsonb | Defines an external port range for inbound NAT to a single backend port on NICs associated with the load balancer. Inbound NAT rules are created automatically for each NIC associated with the Load Balancer using an external port from this range. Defining an Inbound NAT pool on the Load Balancer is mutually exclusive with defining inbound Nat rules. Inbound NAT pools are referenced from virtual machine scale sets. NICs that are associated with individual virtual machines cannot reference an inbound NAT pool. They have to reference individual inbound NAT rules. | |
inbound_nat_rules | jsonb | Collection of inbound NAT Rules used by the load balancer. Defining inbound NAT rules on the load balancer is mutually exclusive with defining an inbound NAT pool. Inbound NAT pools are referenced from virtual machine scale sets. NICs that are associated with individual virtual machines cannot reference an Inbound NAT pool. They have to reference individual inbound NAT rules. | |
load_balancing_rules | jsonb | Object collection representing the load balancing rules Gets the provisioning. | |
name | text | = | The resource name. |
outbound_rules | jsonb | The outbound rules. | |
probes | jsonb | Collection of probe objects used in the load balancer. | |
provisioning_state | text | The provisioning state of the load balancer resource. Possible values include: 'Succeeded', 'Updating', 'Deleting', 'Failed'. | |
region | text | The Azure region/location in which the resource is located. | |
resource_group | text | = | The resource group which holds this resource. |
resource_guid | text | The resource GUID property of the load balancer resource. | |
sku_name | text | Name of the load balancer SKU. Possible values include: 'Basic', 'Standard', 'Gateway'. | |
sku_tier | text | Tier of the load balancer SKU. Possible values include: 'Regional', 'Global'. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
subscription_id | text | =, !=, ~~, ~~*, !~~, !~~* | The Azure Subscription ID in which the resource is located. |
tags | jsonb | A map of tags for the resource. | |
title | text | Title of the resource. | |
type | text | The resource type. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- azure
You can pass the configuration to the command with the --config
argument:
steampipe_export_azure --config '<your_config>' azure_lb