RI-7632: rework statistics for api/v2 client

[ArtemHoruzhenko]

What

This PR implements the RDI statistics functionality for the API v2 client, adding support for fetching and transforming statistics data from RDI API v2 endpoints.

Key Changes

Backend (API)

• New Statistics Client Methods:

  • Added getStatistics() method to ApiV2RdiClient for fetching statistics from RDI API v2
  • Implemented proper error handling and response transformation
  • Integrated with existing RDI client architecture

• Statistics Transformers:

  • Created RdiStatisticsTransformer to convert API v2 responses to internal DTOs
  • Implemented transformation logic for:
    • Client connection statistics
    • Stream processing metrics
    • Performance data
    • Ingestion statistics
  • Added proper type mapping and data validation

• DTOs and Interfaces:

  • Defined API v2 statistics response interfaces
  • Created transformation mappings between API v2 format and internal format
  • Ensured type safety across the statistics pipeline

Testing

• Unit Tests:
  • Added comprehensive tests for ApiV2RdiClient.getStatistics()
  • Created tests for RdiStatisticsTransformer
  • Covered edge cases and error scenarios
  • Verified proper data transformation

Technical Decisions

1. Transformer Pattern: Used a dedicated transformer class to separate API response parsing from business logic, making the code more maintainable and testable

2. Type Safety: Defined strict TypeScript interfaces for API v2 responses to catch type mismatches early

3. Error Handling: Implemented robust error handling to gracefully handle API failures and malformed responses

4. Separation of Concerns: Kept the client focused on HTTP communication while delegating transformation logic to specialized transformers

Dependencies

This PR builds on top of:

• PR RI-7632: rework API for RDI statistics #5353 (RDI statistics API rework) - provides the DTOs and models used by the transformer

Integration

The statistics client integrates with:

• RdiClientProvider - uses this client to fetch statistics
• RDI statistics DTOs - transforms API responses into these models
• RDI statistics controller - serves transformed data to the frontend

Testing

Automation Tests

• Unit tests for ApiV2RdiClient.getStatistics() method
• Unit tests for RdiStatisticsTransformer
• Tests cover successful responses, error cases, and edge cases
• Integration tests with actual RDI API v2 endpoint

Manual Testing

• Verify statistics are correctly fetched from RDI API v2
• Test with different RDI configurations
• Verify error handling when RDI is unavailable or returns errors
• Check data transformation accuracy

Test Coverage

• New files have comprehensive unit test coverage
• All transformation logic is tested
• Error scenarios are covered

---

Note

Medium Risk
Adds a new v2 statistics fetch path and transformation logic, which could affect monitoring/UX if the v2 response shape differs or pipelines aren’t selected as expected. Also introduces typed handling of connection details (including password in the response interface), so reviewers should ensure no sensitive data is surfaced downstream.

Overview
Adds API v2 statistics support by introducing ApiV2RdiClient.getStatistics(), which fetches api/v2/pipelines/{name}/metric-collections and returns an RdiStatisticsResult with Success/Fail status handling.

Introduces v2 response typing (GetMetricsCollectionResponse) and a v2 transformer that reuses v1 statistics transformers while extending processing performance with transform_time_avg and write_time_avg, with accompanying unit tests to validate section ordering/types and edge cases.

^{Written by Cursor Bugbot for commit 33b3db6. This will update automatically on new commits. Configure here.}

[github-actions]

Code Coverage - Integration Tests

Status	Category	Percentage	Covered / Total
🟢	Statements	81.43%	16433/20179
🟡	Branches	64.49%	7487/11609
🟡	Functions	70.36%	2305/3276
🟢	Lines	81.06%	15457/19068

[github-actions]

Code Coverage - Backend unit tests

St.❔	Category	Percentage	Covered / Total
🟢	Statements	92.42%	14099/15256
🟡	Branches	74.88%	4391/5864
🟢	Functions	86.03%	2173/2526
🟢	Lines	92.23%	13476/14612

Test suite run success

3077 tests passing in 292 suites.

Report generated by 🧪jest coverage report action from 33b3db6

[github-actions]

Code Coverage - Frontend unit tests

St.❔	Category	Percentage	Covered / Total
🟢	Statements	82.88%	21196/25574
🟡	Branches	68.13%	8950/13136
🟡	Functions	78.06%	5801/7431
🟢	Lines	83.27%	20755/24924

Test suite run success

5556 tests passing in 704 suites.

Report generated by 🧪jest coverage report action from 33b3db6

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[valkirilov]

nit: Very very minor, but just for consistency - in most places we use capitalized enums, so better to stick to it.

[ArtemHoruzhenko]

had to remove it at all in the second commit. name is inconsistent so we can't rely on it.

[valkirilov]

I didn't compare the interfaces between v1 and v2, I just wonder whether we have matching parts or they're complete independant from each other?

Because, if we have matching sub-parts, maybe we don't have to redeclare them here again?

[ArtemHoruzhenko]

the root is different when statistics are almost the same but I would like to see complete picture in a single file. and moreover we might have some changes (e.g. additional fields will be added without breaking changes) which might require to modify response interface