Reading Time: 7 minutes

We are introducing the Dedicated Load Balancer (DLB) Logs Download API for CloudHub 1.0. This feature, now available across all commercial regions, provides visibility into the DLB for the first time. Previously, customers depended on customer support to access DLB logs. With this new API, they can retrieve logs and troubleshoot issues independently. This self-service capability reduces the need for support cases and improves issue resolution time.

What is the DLB Logs Download API?

The DLB Logs Download API offers Commercial Cloud customers a programmatic way to retrieve logs from their Dedicated Load Balancers. This feature facilitates integration and access to essential logs, providing the critical data needed for customers to resolve issues more quickly and with increased self-sufficiency.

Benefits

This new API delivers tangible benefits that directly impact your operational efficiency and overall satisfaction:

  • API access troubleshooting: Identify the reasons behind failed API access attempts routed through your DLB 
  • Improved customer satisfaction and self-service: Independently review DLB logs to efficiently troubleshoot connectivity issues or verify the status of your DLB’s SSL/TLS certificates 
  • Reduced support tickets: By enabling self-service troubleshooting, we anticipate a significant decrease in the number of high-severity support tickets and escalations related to DLB issues 
  • Enhanced Transparency and Control: Gain better visibility and control over your API infrastructure by having direct access to the logs that govern traffic flow 

Steps for how DBL Logs Download API works 

The CloudHub 1.0 Dedicated Load Balancer (DLB) Logs Download API allows users to retrieve log files for a specific DLB within a defined time period through a simple three-step process:

1. Initiate the log request

Define the exact log files needed by specifying the time range. The API supports two flexible methods for this:

Absolute time range: Pinpoint logs for specific incidents or periods of high activity by defining an exact start and end timestamp: 

curl --location -X POST 'https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/logs/download' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer myAccessToken' \
--data '{
    "resourceType": "DLB_LOGS",
    "resourceName": "myDlbName",
    "queryType": "ABSOLUTE",
    "startTime": "2025-12-25T10:00:00.000000Z",
    "endTime": "2026-01-01T10:00:00.000000Z"
}'

Relative time window: Quickly access recent data for diagnostics using relative definitions like “Last 1 Hour,” “Last 3 Hours,” or “Last 24 Hours,” eliminating the need for specific date/time calculations: 

curl --location -X POST 'https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/logs/download' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer myAccessToken' \
--data '{
    "resourceType": "DLB_LOGS",
    "resourceName": "myDlbName",
    "queryType": "RELATIVE",
    "timeRange": "LAST_3_HOURS",
    "maxRows": 500000,
    "validityMinutes": 60
}'

2. Check the download status 

Because log archives can be substantial, the API processes the file generation request asynchronously. After submitting the request, a dedicated status API endpoint must be queried repeatedly to monitor progress. The status API can return one of the following states:

  • Processing: Log files are being compiled and zipped 
  • Ready: The log file archive is complete and available for download 
  • Failed: An error occurred during compilation (such as an invalid time range or server error) 
curl --location -X GET 'https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/logs/download/status?executionName=myDlbExecutionName' \
--header 'Authorization: Bearer myAccessToken'

3. Secure log download

When the status is “Ready,” the API response returns a unique download token. This token is essential for data extraction. To ensure maximum security, the API generates a secure, time-sensitive download URL using this token. This URL is protected and expires after 60 minutes, ensuring that only authorized users can access the compressed .zip archive.

  • Security: The URL is protected and has a set expiration time (e.g. 60 minutes), ensuring confidentiality and access only by the authorized requestor 
  • Format: The downloaded file is a compressed .zip archive containing the individual log files for the requested time range 

After downloading the archive, you’ll find individual log files formatted as standardized JSON objects, offering granular insights into the traffic flowing through your load balancer, capturing essential metadata for every incoming and outgoing request. For a complete understanding of the log format and the attributes included in the JSON record, please refer to the product documentation.

Next steps and resources

We encourage all CloudHub 1.0 customers to explore this powerful new feature and leverage its capabilities to enhance your troubleshooting workflows.

For additional technical details and usage instructions, please consult the following resources: