steampipe plugin install azure

Table: azure_lb_probe - Query Azure Load Balancer Probes using SQL

Azure Load Balancer Probes are a feature of Azure Load Balancer that enables monitoring of the health and performance of the load balancer. Probes are used to detect the health of the backend resources and make decisions about sending network traffic. They provide essential information to ensure the efficient and reliable operation of the load balancer.

Table Usage Guide

The azure_lb_probe table provides insights into Azure Load Balancer Probes. Network administrators and DevOps engineers can use this table to monitor the health and performance of the load balancer, making it a valuable resource for maintaining optimal network performance. Furthermore, it can be utilized to detect anomalies and troubleshoot potential issues, ensuring the reliability and efficiency of the load balancer.

Examples

Basic info

Explore which Azure load balancer probes are currently in use to understand their configuration and state. This can help in managing network traffic and ensuring optimal performance.

select
id,
name,
type,
provisioning_state,
load_balancer_name,
port
from
azure_lb_probe;
select
id,
name,
type,
provisioning_state,
load_balancer_name,
port
from
azure_lb_probe;

List failed load balancer probes

Discover the segments that have failed load balancer probes in your Azure environment. This information can help you identify potential issues and improve your resource management.

select
id,
name,
type,
provisioning_state
from
azure_lb_probe
where
provisioning_state = 'Failed';
select
id,
name,
type,
provisioning_state
from
azure_lb_probe
where
provisioning_state = 'Failed';

List load balancer probes order by interval

Assess the elements within your Azure load balancer probes to prioritize them based on frequency of checks, allowing you to understand and manage the performance and availability of your services.

select
id,
name,
type,
interval_in_seconds
from
azure_lb_probe
order by
interval_in_seconds;
select
id,
name,
type,
interval_in_seconds
from
azure_lb_probe
order by
interval_in_seconds;

Schema for azure_lb_probe

NameTypeOperatorsDescription
_ctxjsonbSteampipe context in JSON form, e.g. connection_name.
akasjsonbArray of globally unique identifier strings (also known as) for the resource.
cloud_environmenttextThe Azure Cloud Environment.
etagtextA unique read-only string that changes whenever the resource is updated.
idtextThe resource ID.
interval_in_secondsbigintThe interval, in seconds, for how frequently to probe the endpoint for health status. Typically, the interval is slightly less than half the allocated timeout period (in seconds) which allows two full probes before taking the instance out of rotation. The default value is 15, the minimum value is 5.
load_balancer_nametext=The friendly name that identifies the load balancer.
load_balancing_rulesjsonbThe load balancer rules that use this probe.
nametext=The name of the resource that is unique within the set of probes used by the load balancer. This name can be used to access the resource.
number_of_probesbigintThe number of probes where if no response, will result in stopping further traffic from being delivered to the endpoint. This values allows endpoints to be taken out of rotation faster or slower than the typical times used in Azure.
portbigintThe port for communicating the probe. Possible values range from 1 to 65535, inclusive.
protocoltextThe protocol of the end point. If 'Tcp' is specified, a received ACK is required for the probe to be successful. If 'Http' or 'Https' is specified, a 200 OK response from the specifies URI is required for the probe to be successful. Possible values include: 'HTTP', 'TCP', 'HTTPS'.
provisioning_statetextThe provisioning state of the probe resource. Possible values include: 'Succeeded', 'Updating', 'Deleting', 'Failed'.
request_pathtextThe URI used for requesting health status from the VM. Path is required if a protocol is set to http. Otherwise, it is not allowed. There is no default value.
resource_grouptext=The resource group which holds this resource.
subscription_idtextThe Azure Subscription ID in which the resource is located.
titletextTitle of the resource.
typetextType of the resource.

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_probe