Logging

Logging for Load Balancers #

VNETWORK Logging collects and stores logs from various Cloud resources, including Load Balancers. This guide outlines configuring Logging for an existing Load Balancer and highlights the guaranteed throughput between different Load Balancer regions and Logging regions.

To create a new Load Balancer, refer to our product documentation.

Step 1. Open Load Balancers settings #

In the Cloud menu, select Networking and then Load Balancers. Click the Load Balancer name for which you want to configure Logging.

Create Load Balancer

Step 2. Enable Logging #

Go to the Logs tab and turn on the Enable Logging toggle.

Enable Logging

Step 3. Configure Logging settings #

1. Create a namespace for your topics.

This setting is available if you have not activated Logging for your project in the selected destination region.

Previously, when activating Logging, you could see a non-human-readable string, e.g., cbc25c71af8d4f7ca6cbbcdc5a4d68fe.your-topic as a namespace that is used as prefixed for topics. To make this process more user-friendly, we created the possibility of making human-readable namespaces, e.g., namespace123.your-topic.

You can only create a namespace for a new project where the default value is not set up.

To create a namespace, input the namespace name according to the following restrictions:

  • Lowercase Latin letters and digits can be used
  • Underscore and spaces are prohibited
  • Length is between 2–32
  • The name should be unique for the destination region. If it’s already used, the system will suggest inputting another name.

Click Create.

Configure logging

2. Add a topic. Select an existing one from the list or create a new one. For a new topic, specify the name and the retention period.

3. Click Save changes.

Your Load Balancer will start sending logs to the topic.

Throughput test results #

Below are the test results that demonstrate the throughput for various region pairs (measured in K RPS,) where “source” is the region of a load balancer and “destination” is the location of the Managed Logging servers.

SourceDestinationMeasured log delivery throughput, K RPS
AmsterdamLuxembourg9.6
Amsterdam-2Luxembourg14.4
DarmstadtLuxembourg16.8
FrankfurtLuxembourg8
TokyoLuxembourg1.6
IstanbulLuxembourg8.8
LondonLuxembourg17.6
Luxembourg-2Luxembourg12
WarsawLuxembourg11.2
Paris-2Luxembourg14.4
DubaiLuxembourg17.6
AlmatyLuxembourg16
JohannesburgLuxembourg11.2
NewportLuxembourg16.8
DubaiSingapore16.8
AlmatySingapore12.8
TokyoSingapore9.6
SingaporeSingapore14.4
JohannesburgSingapore11.2
SydneySingapore10.4
MumbaiSingapore17.6
Hong KongSingapore10.4
ChicagoManassas8
ManassasManassas15.2
Santa ClaraManassas7.2
Sao PauloManassas14.4
Sao Paulo-2Manassas16.8