Access Logging
This section highlights the observability features of the Application Load Balancer (ALB) access logging. The ALB supports comprehensive logging that offer visibility into the application traffic. When enabled, all logs are transmitted to our observability system, where they can be queried and analyzed for valuable insights. Central logging must be enabled for this functionality, ensuring effective monitoring and troubleshooting of application traffic. This allows for proactive identification and resolution of potential issues, enhancing overall application performance and reliability.
Note: This feature is only available for newly created ALBS in non-US datacenters and requires central logging to be enabled as a prerequisite.
Access Logs
Once central logging is enabled, logs from your ALB will be sent to the logging service. You can access and analyze these logs using a dedicated Grafana instance.
Note: The Grafana URL where the logs will be available will follow the pattern as in this example: https://grafana.d6b7a2374abe.dev.logging.de-txl.ionos.com/
where d6b7a2374abe
is a hash of the contract number.
Enable Central Logging
Requirement: Enabling central logging is mandatory for the ALB to send logs.
Configuration: Send a
POST
request to the ALB endpoint to enable central logging. Here's an example using curl:
Note: Replace datacenterId
and TOKEN
with your actual data center ID and authorization token.
Note:
Enabling or disabling central logging is also possible via
PUT
requests.Enabling central logging incurs additional costs.
Last updated