Introducing CQL reports
Reporting is essential when managing a microservice architecture. Without some kind of reporting tool, it’s significantly more difficult to gain insight into how services and resources are functioning. Software teams need this insight in order to make meaningful progress — without reporting, it’s hard to even know where progress needs to be made.
With the introduction of CQL reports, Cortex gives you more visibility than ever before. Up until now, CQL and reports have been relatively binary. Although CQL gives you the power to traverse your data with flexibility, it’s been constrained to true/false, yes/no answers.
CQL reports are highly responsive: your columns, which would normally be defined as scorecard rules, are based on custom CQL expressions instead. Let’s say, for example, you have sonarqube(“coverage”) >= 0.9 as a scorecard rule. In a standard report for that scorecard, your rule would be a column, and in each cell you’d see whether the service or resource has at least 90% code coverage. But what if you want to see what the actual code coverage for each service or resource is? Using CQL reports, you can now generate a report that returns the exact SonarQube metrics for each service.
CQL reports takes the power of Cortex’s Query Builder even further. Not only can you query all the raw data within Cortex, but with CQL reports, you can also build a custom report on top of all that data, unlocking greater visibility into your components’ performance.
To see what kind of insights CQL reports can generate for your organization, book a demo with us today.