Using CQL Reports to debug Scorecards

Please note, these reports utilize API calls, so we recommend running the report for a single entity during testing.

Some queries in Scorecards provide a hover which identifies the value Cortex is returning (example below, where there is only one dashboard for the service).

Where this is not available, CQL reports can be utilized to provide more granular information on the value of a rule when passing, or an associated error when failing.  Until published, CQL reports are private to the individual user.

In this example, we have a Scorecard looking to confirm that the entity's readme.md file is populated, (git.fileContents("readme.md") != null) which some entities are failing:

To investigate further, in CQL reports, create a CQL report, starting from scratch.

Add required information, including a name.  Apply filters or groupings to specific services to narrow down the scope to a failing example.
In Define Columns, add a new column.  This is where you'll add the CQL expression without the quantifier.  Save, and the report will generate.  

In this example, we can see that the rule is returning the contents of the ReadMe for entity Cortex Support. We can also see that My First Service is failing the rule due to the returned error, which identifies the service has not been registered with the Git integration.