Continuity Counter errors in CloudWatch

AWS Elemental MediaConnect reports Continuity Counter (CC) errors to CloudWatch for all PIDs in the transport stream, not just video and audio PIDs. The ContinuityCounter metric tracks instances where packets arrive out of order or are lost entirely, regardless of the PID type.

These CC errors are classified as TR 101 290 Priority 1 metrics, which signify critical stream disruptions. In your case, if your source encoder had a micro burst of CC errors on PID 17 (SDT), CloudWatch would detect and report those errors through the ContinuityCounter or SourceContinuityCounter metrics.

CC errors occur when there's high packet loss that cannot be recovered, or when the transport stream contains errors during encoding or delivery from upstream applications. These errors may manifest as pixelation in decoded video content.

You can monitor these metrics in CloudWatch using various dimensions including Flow ARN, Source ARN, Availability Zone, or across all flows, depending on which metric you're using (ContinuityCounter for flow health or SourceContinuityCounter for source health).
Sources
Troubleshooting SRT and Zixi with AWS Elemental MediaConnect | AWS for M&E Blog
AWS Elemental MediaConnect metrics to monitor flow health - AWS Elemental MediaConnect
AWS Elemental MediaConnect metrics to monitor source health - AWS Elemental MediaConnect
Capturing AWS Elemental MediaConnect events with Amazon CloudWatch logs | AWS for M&E Blog