Make CircuitBreakerUrl class more informative about when it fails

User Story

As a Java backend developer, I want to add a property to the CircuitBreakerUrl class to act as a flag to throw (or not) an exception when the gotten response status from the HTTP client is not in the 2xx range. The default value for this property will be true to avoid breaking any existing functionality. When it's false, then it should not throw any exception and let the caller deal with the non-2xx HTTP status. Additionally, I want to leverage this user story to add some debugging information on the time elapsed when making requests to the CubeJS server.

Acceptance Criteria

Create a property in the CircuitBreakerUrl class to control exception throwing for non-2xx HTTP responses.
Set the default value of this property to true.
Update the AnalyticsAPI, EventLogRunnable, and CubeJSClient components to set the flag to false where needed.
Add logging for the time elapsed when making requests to the CubeJS server.
Ensure that the code changes are well-documented and unit tested.

dotCMS Version

master

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links

Link to Slack Conversations Link to Support Tickets Link to Figma Designs

Assumptions & Initiation Needs

Assumption 1: The existing codebase follows Java best practices.
Assumption 2: The CubeJS server is used for data retrieval.
Initiation Need 1: Access to the code repository.
Initiation Need 2: Development and testing environment.

Quality Assurance Notes & Workarounds

QA Note 1: Test cases should cover various scenarios, including different HTTP response codes.
QA Note 2: Verify that the logging of time elapsed is accurate and informative.
Workaround 1: In case of issues, revert the changes and investigate the root cause.

Sub-Tasks & Estimates

Create the property in CircuitBreakerUrl class - Estimated time: 2 hours
Update AnalyticsAPI, EventLogRunnable, and CubeJSClient - Estimated time: 4 hours
Add logging for time elapsed - Estimated time: 3 hours
Documentation and testing - Estimated time: 5 hours

dotCMS / core