> ## Documentation Index
> Fetch the complete documentation index at: https://gcore.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Monitoring for load balancers
export const Caution = ({children}) => {
return ;
};
Gcore collects and stores metrics and logs from various cloud resources, including load balancers. This guide explains the different monitoring features and how to configure them for an existing load balancer.
## Prometheus listener
Load balancers use listeners to associate a port with a pool of instances. In addition to the regular balancing listeners, you can create one that exposes an endpoint with the balancer's metrics. This enables you to scrape them with Prometheus and view them with Grafana.
Tip: Import [this pre-made Grafana dashboard](https://grafana.com/grafana/dashboards/15828-openstack-octavia-amphora-load-balancer/) to display your metrics.
### Enable Prometheus listener
You can enable the Prometheus listener from the Customer Portal by following these steps:
To enable the metrics endpoint, open the **Gcore Customer Portal**, navigate to **Cloud** > **Networking** > **Load Balancers**, and click the name of a load balancer in the list.
This will take you to the **Load Balancer Details** page.
Select the **Listeners** tab, scroll down until you see the **Add Listener** button, and click it.
This will open the **Add Listener** dialog.
Enter a **Name** for your listener, set a **Port** and a **Connection limit**, and for the **Protocol** select **Prometheus**.
Just like with regular listeners, you have the following options to secure your Prometheus listener:
* Define an allowed IP range with CIDRs.
* Define a list of users who get access through Basic Auth.
* Enable SSL/TLS by [adding certificates](/cloud/networking/load-balancers/add-certificates-to-load-balancer).
* Enable mTLS [via the Gcore Cloud API](/cloud/networking/load-balancers/configure-mtls-authentication).
Click the **Create Listener** button and wait until the Prometheus listener appears in the list.
You can now add the listener as a target to a Prometheus instance by adding the following lines to its prometheus.yml under the scrape\_configs section:
```yaml theme={null}
- job_name:
metrics_path: /metrics
static_configs:
- targets:
- :
```
### Disable Prometheus listener
Before you delete a Prometheus listener, you should delete the corresponding job from all *prometheus.yml* files.
You can disable the Prometheus listener in the **Customer Portal** by following these steps:
Open the **Gcore Customer Portal**, navigate to **Cloud** > **Networking** > **Load Balancers**, and click a load balancer's name in the list.
Select the **Listeners** tab, scroll down until you see the Prometheus listener, click on its corresponding action menu on the right, and click **Delete**.
## Logging as a service
Gcore offers Managed Logging, also known as logging as a service (LaaS) for all cloud resources.
When you enable logging on a load balancer, LaaS will store the logs in the same region as the load balancer.
### Enable logging
You can enable logging via the **Customer Portal** by following these steps:
To enable the logging, open the **Gcore Customer Portal**, navigate to **Cloud** > **Networking** > **Load Balancers**, and click the name of a load balancer in the list.
Select the **Logging** tab, and activate the **Enable Logging** toggle.
You can either use an existing log **Topic** or create a new one, allowing you to define a **Retention** period.
Click the **Save changes** button, and Gcore’s LaaS will set up the logging for the load balancer.
### View the logs
You can now view your logs in the **Customer Portal** or [your own Grafana instance](/cloud/logging-as-a-service/view-opensearch-logs-in-Grafana). To view the logs in the **Customer Portal**, follow these steps:
Open the **Gcore Customer Portal** and navigate to **Cloud** > **Managed Logging**.
Select a log topic from the list and click the corresponding **View Logs** link.
### Disable logging
You can disable logging via the **Customer Portal** by following these steps:
Open the **Gcore Customer Portal**, navigate to **Cloud** > **Networking** > **Load Balancers**, and click a load balancer's name in the list.
Select the **Logging** tab, deactivate the **Enable Logging** toggle, and click the **Save changes** button.
## Cloud API endpoints
You can request status, metrics, and general statistics for your load balancers via the Gcore Cloud API.
### Load balancer status
The status endpoints provide details about a load balancer's operating and provisioning status, its listeners, and their pools.
You can find more information about the endpoints on the following documentation pages.
* [Status of one specific load balancer](/api-reference/cloud/LoadBalancerStatusInstanceViewSet.get)
* [Status of all load balancers](/api-reference/cloud/LoadBalancerStatusViewSet.get)
### Load balancer metrics
The metrics endpoint provides information about CPU, memory, and network utilization.
You can find more information about the endpoints on the following documentation pages.
* [Metrics of one specific load balancer](/api-reference/cloud/LoadbalancerMetricsHandler.post)
### Load balancer and listener statistics
The get endpoints for load balancers and listeners provide data about connections, traffic, and errors when called with `?show_stats=true`.
You can find more information about the endpoints on the following documentation pages.
* [Get one specific load balancer](/api-reference/cloud/LoadBalancerInstanceViewSet.get)
* [Get one listener](/api-reference/cloud/LoadBalancerListenerInstanceViewSet.get)
* [Get all listeners](/api-reference/cloud/LoadBalancerListenerViewSet.get)