The repository overview graph should show whether something is wrong 'somewhere in the repo'. The remark_counts_children in the JSON response should be used for this.
To not 'cry wolf' we should not include all the ASN1Issues and encodingIssues in these numbers, as those issues typically occur in all objects for a repo. One way to go at this, is to only show the count for the ERROR RemarkLevel in the graph (if it that count is > 0 ). Assuming errors are relatively rare, the combination of the number and the textual representation of errors (see #11) should make it so the end-user can spot what/where something is wrong in a glimpse.
The repository overview graph should show whether something is wrong 'somewhere in the repo'. The
remark_counts_childrenin the JSON response should be used for this.To not 'cry wolf' we should not include all the
ASN1Issues andencodingIssuesin these numbers, as those issues typically occur in all objects for a repo. One way to go at this, is to only show the count for theERRORRemarkLevel in the graph (if it that count is > 0 ). Assuming errors are relatively rare, the combination of the number and the textual representation of errors (see #11) should make it so the end-user can spot what/where something is wrong in a glimpse.