# Monitoring and tagging in AWS Elemental MediaConnect Monitoring and tagging Monitoring is an important part of maintaining the reliability, availability, and performance of AWS Elemental MediaConnect and your other AWS solutions. AWS provides the following monitoring tools to watch MediaConnect, report when something is wrong, and take automatic actions when appropriate: + *MediaConnect flow source monitoring* displays detailed information about a source stream and its program media. You can view status messages about the stream as well as details about the program video, audio, and other data. For more information, see the [Monitoring using source metadata](monitor-with-source-stream-monitoring.md) section of this guide. + *AWS CloudTrail* captures API calls and related events made by or on behalf of your AWS account and delivers the log files to an Amazon S3 bucket that you specify. You can identify which users and accounts called AWS, the source IP address from which the calls were made, and when the calls occurred. For more information, see the [AWS CloudTrail User Guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/). + *Amazon EventBridge* delivers a near real-time stream of system events that describe changes in AWS resources. EventBridge enables automated event-driven computing, as you can write rules that watch for certain events and trigger automated actions in other AWS services when these events happen. For more information, see the [Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). + *Amazon CloudWatch* monitors your AWS resources and the applications that you run on AWS in real time. You can collect and track metrics, create customized dashboards, and set alarms that notify you or take actions when a specified metric reaches a threshold that you specify. For example, you can have CloudWatch track the number of dropped and unrecovered packets on your AWS Elemental MediaConnect flows and automatically notify you when those values exceed a certain number. For more information, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/). # Monitoring with the AWS Elemental MediaConnect console Monitoring with the MediaConnect console AWS Elemental MediaConnect offers several ways to monitor your resources directly within the MediaConnect console. This allows you to quickly view the status and health of your flows, sources, and content without having to switch to other AWS services. In the MediaConnect console, you can use the following monitoring capabilities: + **Content quality analysis** - Monitor your source streams for issues like black frames, frozen frames, and audio silence. + **Thumbnails** - View visual thumbnail previews of your video content to verify streams. + **Source metadata** - View detailed information about transport streams, programs, and media tracks. + **Flow and source health** - Monitor the overall health and status of your flows and sources. By using these built-in monitoring tools, you can proactively identify and troubleshoot issues with your MediaConnect resources. The following sections provide details on how to use each monitoring feature in the MediaConnect console. **Contents** + [Monitoring with content quality analysis in AWS Elemental MediaConnect](monitor-content-quality-analysis.md) + [Viewing thumbnails of the source video](monitor-with-thumbnails.md) + [Monitoring using source metadata](monitor-with-source-stream-monitoring.md) + [Monitoring flow and source health](monitor-flow-and-source-health.md) # Monitoring with content quality analysis in AWS Elemental MediaConnect Monitoring with content quality analysisContent quality analysis You can now use MediaConnect content quality analysis to monitor your source streams more effectively. You can use MediaConnect content quality analysis to monitor your source streams more effectively. This feature enables you to track specific audio and video metrics, helping you ensure that your content meets required quality standards. By monitoring these metrics, you can quickly identify anomalies in your streams, enabling you to promptly resolve issues and maintain content quality. When used alongside other MediaConnect monitoring tools, content quality analysis provides you with a comprehensive view of your stream's quality. This integrated monitoring approach enables you to implement proactive measures and ensure a smooth and reliable media delivery workflow. **Contents** + [Key points](#monitor-content-quality-analysis-key-points) + [How content quality analysis works](#how-content-quality-analysis-works) + [Considerations](#content-quality-analysis-considerations) + [Next steps](#content-quality-analysis-next-steps) ## Key points ### How content quality analysis works You can monitor for the following content quality issues: + **Silent audio periods -** Use this metric to detect periods of audio silence in the stream. This is useful for catching muted microphones in live broadcasts, unintended silence in recordings, or audio encoding issues. + **Black frames -** Use this metric to detect periods of black video frames in the stream. This is helpful for identifying issues in live broadcasts, pre-recorded content, or your video encoding process. + **Frozen frames -** Use this metric to detect periods of unchanging video frames in the stream. This is valuable for live events, identifying equipment issues, or detecting problems in your content delivery. For each metric, you can set custom duration thresholds to fine-tune when alerts are triggered based on your specific needs. MediaConnect then monitors the status of the content within your source stream, posting warnings and alerts when issues occur in the areas you've chosen to monitor. ### Considerations + Content quality analysis works with transport stream source flows only. CDI flows and bridge flows aren't currently supported. + The content quality analysis feature only monitors the first video stream and the first audio stream it encounters within a single source. + Content quality analysis monitoring is limited to flows with 10 outputs or fewer. If a flow exceeds 10 outputs, MediaConnect automatically disables content analysis for that flow. + This feature is available at no additional charge in all AWS Regions where MediaConnect is available. ## Next steps To get started with this feature, see [Enabling content quality analysis and configuring thresholds](enable-content-quality-analysis.md). # Enabling content quality analysis and configuring thresholds Enabling content quality analysis You enable content quality analysis for each flow in MediaConnect individually. You can do this when you create a new flow, or when you update an existing one. For each flow, you can customize the monitoring experience by configuring thresholds for individual metrics or disabling specific metrics as needed. This page guides you through the process of enabling content quality analysis and configuring its metrics. ## Prerequisites If you want to enable content quality analysis for an existing flow, ensure that the flow state is `STANDBY`, `UPDATING`, or `ACTIVE` before you start. ## Procedure You can enable content quality analysis through the AWS Management Console, the AWS CLI, and the MediaConnect API. ### Enabling content quality analysis when you create a flow ------ #### [ Console ] **To enable content quality analysis when you create a flow** Follow the instructions for [Creating a flow](flows-create.md). In the **Source monitoring configuration** step, make sure to turn on **Content quality analysis state. ** When you enable content quality analysis, you can specify a threshold for the following metrics. For each metric, you can populate a value between 10 and 60 seconds. The default threshold is 30 seconds. **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/enable-content-quality-analysis.html) ------ #### [ AWS CLI ] **To enable content quality analysis with default settings** Run the [create-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/create-flow.html) command as shown in the following example: ``` aws mediaconnect create-flow --flow-name "myFlow" \ --source-arn "sourceFlowARN" \ --source-monitoring-config ContentQualityAnalysisState=ENABLED \ --other-required-parameters ``` MediaConnect automatically enables all individual metrics with a default value of 30 seconds, as shown below: ``` { "Flow": { "FlowArn": , ... "SourceMonitoringConfig": { "ContentQualityAnalysisState": "ENABLED", "AudioMonitoringSettings": [ { "SilentAudio": { "State": "ENABLED", "ThresholdSeconds": 30 } } ], "VideoMonitoringSettings": [ { "BlackFrames": { "State": "ENABLED", "ThresholdSeconds": 30 }, "FrozenFrames": { "State": "ENABLED", "ThresholdSeconds": 30 } } ] } } } ``` **To enable content quality analysis with custom thresholds** Run the [create-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/create-flow.html) command with the `--source-monitoring-config` parameter configured as shown below. The following example command enables all three metrics with custom thresholds: ``` aws mediaconnect create-flow --flow-name "myFlow" \ --source-arn "sourceFlowARN" \ --source-monitoring-config '{"ContentQualityAnalysisState": "ENABLED", \ "VideoMonitoringSettings": [{ \ "FrozenFrames": {"State": "ENABLED", "ThresholdSeconds": }, \ "BlackFrames": {"State": "ENABLED", "ThresholdSeconds": }}], \ "AudioMonitoringSettings": [{ \ "SilentAudio": {"State": "ENABLED", "ThresholdSeconds": }}]}' ``` Keep in mind the following: + For each threshold, replace ** with a value between 10 and 60 seconds. + If you don't specify a threshold, the default value of 30 seconds is used. + You can enable one or more of the following metrics. + If you enable video monitoring, you must enable at least one of the `BlackFrames` or `FrozenFrames` metrics. + If you enable audio monitoring, you must enable the `SilentAudio` metric. **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/enable-content-quality-analysis.html) ------ ### Enabling content quality analysis in an existing flow ------ #### [ Console ] **To enable content quality analysis in an existing flow** Follow the instructions for [Updating a flow](flows-update.md). In the **Source monitoring configuration** step, make sure to turn on **Content quality analysis state. ** When you enable content quality analysis, you can specify a threshold for the following metrics. For each metric, you can populate a value between 10 and 60 seconds. The default threshold is 30 seconds. **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/enable-content-quality-analysis.html) ------ #### [ AWS CLI ] **To enable content quality analysis with default settings** Run the [update-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/update-flow.html) command as shown in the following example: ``` aws mediaconnect update-flow --flow-arn "FlowArn" \ --source-monitoring-config ContentQualityAnalysisState=ENABLED ``` MediaConnect automatically enables all individual metrics with a default value of 30 seconds, as shown below: ``` { "Flow": { "FlowArn": , ... "SourceMonitoringConfig": { "ContentQualityAnalysisState": "ENABLED", "AudioMonitoringSettings": [ { "SilentAudio": { "State": "ENABLED", "ThresholdSeconds": 30 } } ], "VideoMonitoringSettings": [ { "BlackFrames": { "State": "ENABLED", "ThresholdSeconds": 30 }, "FrozenFrames": { "State": "ENABLED", "ThresholdSeconds": 30 } } ] } } } ``` **To enable content quality analysis with custom thresholds** Run the [update-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/update-flow.html) command with the `--source-monitoring-config` parameter configured as shown below. This example command enables all three metrics with custom thresholds. ``` aws mediaconnect update-flow \ --flow-arn "FlowArn" \ --source-monitoring-config '{"ContentQualityAnalysisState": "ENABLED", \ "VideoMonitoringSettings": [{ \ "FrozenFrames": {"State": "ENABLED", "ThresholdSeconds": }, \ "BlackFrames": {"State": "ENABLED", "ThresholdSeconds": }}], \ "AudioMonitoringSettings": [{ "SilentAudio": {"State": "ENABLED", "ThresholdSeconds": }}]}' \ ``` Keep in mind the following: + For each threshold, replace ** with a value between 10 and 60 seconds. + If you're enabling a metric for the first time and you don't specify a threshold, the default value of 30 seconds is used. + If you're updating a previously enabled metric and you don't specify a threshold, the previously set value is retained. + You can enable one or more of the following metrics. + If you enable video monitoring, you must enable at least one of the `BlackFrames` or `FrozenFrames` metrics. + If you enable audio monitoring, you must enable the `SilentAudio` metric. **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/enable-content-quality-analysis.html) ------ ## Next steps + After you enable content quality analysis for a flow, MediaConnect starts analyzing the source stream and reporting any detected issues. For instructions on how to review these issues, see [Viewing content quality analysis settings and alerts](content-quality-analysis-viewing.md). + If you no longer want to analyze content quality for your flow, you can disable the feature. For instructions, see [Disabling content quality analysis](disable-content-quality-analysis.md). ## Additional resources + [Creating a flow](flows-create.md) + [Updating a flow](flows-update.md) + [Monitoring and tagging in AWS Elemental MediaConnect](monitor.md) # Viewing content quality analysis settings and alerts Viewing content quality issues When you enable content quality analysis, MediaConnect starts posting warnings and alerts for the enabled metrics in your AWS account. This page guides you through the process of confirming your content quality analysis settings, and viewing any warnings and alerts for the flows in your account. ## Prerequisites The following procedure assumes that you have already enabled content quality analysis for a flow. ## Procedure You can view content quality warnings and alerts through the AWS Management Console, the AWS CLI, and the MediaConnect API. ------ #### [ Console ] **To check if content quality analysis is enabled** 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. From the **Flows** screen, select the flow you want to inspect. 1. On the flow details page, choose the **Configuration** tab. 1. Under **Source monitoring configuration**, you can find the content quality analysis state. ![\[A MediaConnect flow with content quality analysis enabled.\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/images/content-quality-analysis-enabled.png) **To check if quality alerts are present** 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. From the **Flows** screen, select the flow you want to inspect. 1. On the **Alerts** tab, alerts appear when content quality problems are detected in the flow source. ![\[A content quality alert shown on a MediaConnect flow details page.\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/images/content-quality-analysis-alert.png) ------ #### [ AWS CLI ] To confirm if quality analysis metrics are enabled for a given flow, run the [describe-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/describe-flow.html) command: ``` aws mediaconnect describe-flow --flow-arn flowARN ``` The response shows which content quality analysis metrics are enabled: ``` { "Flow": { "FlowArn": "flowARN", ... "SourceMonitoringConfig": { "ContentQualityAnalysisState": "ENABLED", "AudioMonitoringSettings": [ { "SilentAudio": { "State": "DISABLED", "ThresholdSeconds": 15 } } ], "VideoMonitoringSettings": [ { "BlackFrames": { "State": "DISABLED", "ThresholdSeconds": 10 }, "FrozenFrames": { "State": "ENABLED", "ThresholdSeconds": 5 } } ] }, ... } } ``` The response also shows messages about any warnings or alerts that need your attention: ``` { ... "Messages": { "Errors": [ "Monitoring Stream Alert: Audio Stream Missing. Please investigate the flow source.", "Monitoring Stream Alert: Video Stream Missing. Please investigate the flow source." ] } } ``` Alternatively, if both audio and video streams are present but experiencing issues, you might see something like this: ``` { ... "Messages": { "Errors": [ "Monitoring Stream Alert: Black frames detected for more than 30 seconds. Please investigate the flow source.", "Monitoring Stream Alert: Frozen frames detected for more than 30 seconds. Please investigate the flow source.", "Monitoring Stream Alert: Silent audio detected for more than 30 seconds. Please investigate the flow source." ] } ``` **Note** These error messages are context-dependent. If an audio or video stream is missing, related quality alerts for that stream (such as silent audio or black/frozen frames) won't be triggered. ------ ## Next steps If you no longer want to analyze content quality for your flow, you can disable the feature. For instructions, see [Disabling content quality analysis](disable-content-quality-analysis.md). # Disabling content quality analysis Disabling content quality analysis You can disable the content quality analysis feature without losing your previously configured settings for individual metrics. If you re-enable content quality analysis in the future, your custom thresholds for individual metrics are preserved so that you don’t have to reconfigure them. This page guides you through the process of disabling the content quality analysis feature. ## Prerequisites The following procedure assumes that you have already enabled content quality analysis for a flow. You can disable content quality analysis on an active or inactive flow. If the flow is active, you don't have to stop it first. ## Procedure You can disable content quality analysis through the AWS Management Console, the AWS CLI, and the MediaConnect API. ------ #### [ Console ] **To disable content quality analysis** 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. From the **Flows** screen, select the flow for which you want to disable content quality analysis. 1. On the flow details page, choose the **Sources** tab. 1. In the **Source monitoring configuration **section, choose **Edit**. 1. Choose one of the following options: 1. To disable all metrics, turn off **Content quality analysis state**. 1. To disable specific metrics, turn off one or more of the following metrics: **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/disable-content-quality-analysis.html) 1. Choose **Update **to save your changes. ------ #### [ AWS CLI ] **To disable all metrics** Run the [update-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/update-flow.html) command as shown in the following example: ``` aws mediaconnect update-flow \ --flow-arn "flowARN" \ --source-monitoring-config ContentQualityAnalysisState=DISABLED ``` In the following example response, `ContentQualityAnalysisState` is now disabled, but individual metric settings remain unchanged: ``` { "Flow": { "FlowArn": "", ... "SourceMonitoringConfig": { "ContentQualityAnalysisState": "DISABLED", "ThumbnailState": "ENABLED", "AudioMonitoringSettings": [ { "SilentAudio": { "State": "ENABLED", "ThresholdSeconds": 30 } } ], "VideoMonitoringSettings": [ { "BlackFrames": { "State": "ENABLED", "ThresholdSeconds": 30 }, "FrozenFrames": { "State": "ENABLED", "ThresholdSeconds": 10 } } ] } } } ``` **Note** When `ContentQualityAnalysisState` is set to `DISABLED`, it takes precedence over the individual metric settings. This means that even though individual metrics (`SilentAudio`, `BlackFrames`, `FrozenFrames`) show as `ENABLED`, they are not active. This enables you to maintain your preferred configuration for individual metrics without having to reconfigure them each time you toggle the overall `ContentQualityAnalysisState`. When you want to re-enable content quality analysis, set `ContentQualityAnalysisState` back to `ENABLED`. Your previously configured individual metric settings will then become active again. **To disable specific metrics** Run the [update-flow](https://docs.aws.amazon.com/cli/latest/reference/mediaconnect/update-flow.html) command with the `--source-monitoring-config parameter` configured as shown below. The following example command disables the two video monitoring metrics while preserving the custom thresholds for future use: ``` aws mediaconnect update-flow \ --flow-arn "FlowArn" \ --source-monitoring-config ContentQualityAnalysisState=ENABLED \ '{"VideoMonitoringSettings": [ \ {"FrozenFrames": {"State": "DISABLED", "ThresholdSeconds": 10}}, \ {"BlackFrames": {"State": "DISABLED", "ThresholdSeconds": 15}}], \ "AudioMonitoringSettings": [ \ {"SilentAudio": {"State": "ENABLED", "ThresholdSeconds": 25}}]}' ``` In the following example response, `ContentQualityAnalysisState` remains enabled, but both of the video monitoring metrics are now disabled: ``` { "Flow": { "FlowArn": , ... "SourceMonitoringConfig": { "ContentQualityAnalysisState": "ENABLED", "AudioMonitoringSettings": [ { "SilentAudio": { "State": "ENABLED", "ThresholdSeconds": 25 } } ], "VideoMonitoringSettings": [ { "BlackFrames": { "State": "DISABLED", "ThresholdSeconds": 15 }, "FrozenFrames": { "State": "DISABLED", "ThresholdSeconds": 10 } } ] } } } ``` Keep in mind the following: + You don’t have to change or remove the existing thresholds for individual metrics. If you re-enable content quality analysis in the future, your custom thresholds are preserved so that you don’t have to reconfigure them. + You can disable one, two, or all three of the following metrics: **** [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/disable-content-quality-analysis.html) ------ ## Next steps You can re-enable the content quality analysis feature at any time. For instructions, see [Enabling content quality analysis in an existing flow](enable-content-quality-analysis.md#enable-content-quality-analysis-procedure-existing-flow). # Viewing thumbnails of the source video Monitoring with thumbnails AWS Elemental MediaConnect can generate JPEG-format thumbnails of the video that is in the source in any type of flow except for CDI flows. The thumbnail provides a visual verification that the content contains video. You can view the thumbnails on the console or retrieve them programmatically. ## How thumbnails are generated When you have enabled thumbnails in a flow and when the flow is active, MediaConnect generates a JPEG thumbnail with a 480 x 270 resolution. The rate for generating the thumbnail is as follows: + The fastest possible rate is one image every second. + The rate might be slower, depending on the characteristics of the source video. For example, one image every 6 seconds. ## How thumbnails are displayed As soon as the thumbnail is generated, MediaConnect displays it in the flow **Details** page, in the **Preview** section. It also makes the thumbnail available as base 64 binary data. You can use an AWS API to work with the binary data programmatically. MediaConnect encrypts thumbnails during retrieval to the console Preview window or in transit for API responses. The retrieval rate for thumbnails is as follows: + The refresh rate for the MediaConnect console is every 2 seconds. If the rate is faster than the generation rate, the same thumbnail is displayed more than once on the console. + The API retrieve rate is constrained by the [maximum TPS](quotas.md#limits-api). This constraint only matters if you are trying to retrieve thumbnails for multiple flows. If you are retrieving thumbnails for only one flow, there is no point retrieving the thumbnail more often than every second (the fastest possible generation rate). **Topics** + [ ## How thumbnails are generated ](#thumbnails-how-generated) + [ ## How thumbnails are displayed ](#thumbnails-how-displayed) + [ # Requirements for thumbnails ](thumbnails-specifications.md) + [ ## Limit on thumbnails in MediaConnect ](#thumbnails-api-limits) + [ # Enabling and viewing thumbnails in the console ](thumbnails-enable-view-console.md) + [ # Enabling and retrieving thumbnails programmatically ](thumbnails-enable-retrieve-programatically.md) # Requirements for thumbnails Requirements ## Requirements for the video source For MediaConnect to successfully generate thumbnails, make sure that the video source meets the following requirements. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/thumbnails-specifications.html) ## Requirements for the flow To successfully generate thumbnails, make sure that your flow meets the following requirements. | Characteristic of the flow | Requirement | | --- | --- | | Type of flows that support thumbnails | Any type of flow except CDI flows. | | Maximum number of outputs that can be attached to the flow | 10If the flow exceeds this limit, then MediaConnect won't generate any thumbnails for this flow. | | Maximum bitrate for all the outputs that are attached to the flow | 400 MbpsIf the flow exceeds this limit, then MediaConnect won't generate any thumbnails for this flow. | ## Limit on thumbnails in MediaConnect There is a limit to the number of thumbnails that you can view or retrieve. This limit is the TPS (transactions per second). The thumbnails feature shares the global limits for MediaConnect. For more details, see [Limits for API requests](quotas.md#limits-api). # Enabling and viewing thumbnails in the console View thumbnails using the console You enable thumbnails separately in each flow. You can enable thumbnails when you are creating the flow, or you can enable them in an existing flow. After you have enabled thumbnails, MediaConnect automatically starts to generate them whenever the flow is active. ## Enabling when you create a flow In the flow that you are creating, go to the **Source monitor configuration** section, and move the **Thumbnails state** slider to **Enabled**. When you start the new flow, MediaConnect will start to generate thumbnails. ## Enabling in an existing flow 1. On the left navigation bar, choose **Flows**. Select the flow by its name. 1. On the flow **Details** page, choose the **Sources** tab. In the **Source monitoring configuration** section, choose **Edit**. 1. Move the **Thumbnails state** slider to **Enabled**, then choose **Update**. If the flow is currently active, MediaConnect starts to generate thumbnails. You can enable and disable the thumbnails as often as you want, when the flow is active or inactive. ## Viewing thumbnails When thumbnails are enabled in an active flow, MediaConnect automatically generates thumbnails and displays them in the flow **Details** page, in the **Preview** section. If the flow becomes inactive, the thumbnail preview stops refreshing. After a few seconds, the preview is replaced by a message. **Viewing thumbnails on several flows** You might open several instances of the MediaConnect console, one instance for each active flow. You can do this, but if you enable thumbnails in all the instances, there might be issues with displaying thumbnails in one or more of the instances. We recommend that you enable thumbnails on only one active flow at a time, and disable it on other active flows. ## Disabling thumbnails You can disable thumbnails on an active or inactive flow. If the flow is active, you don't have to stop it first. Go to the flow **Details** page, choose the **Sources** tab, and move the **Thumbnails state** slider to **Disabled**. Then choose **Update**. # Enabling and retrieving thumbnails programmatically You can use the AWS CLI to work with thumbnails programmatically. The following information assumes that you are familiar with the basics of using the AWS CLI. For information about the basics, see the [AWS CLI Command Reference](https://docs.aws.amazon.com/cli/latest/reference/). You enable thumbnails separately in each flow. You can enable thumbnails when you first create a flow or you can enable them in an existing flow. After thumbnails are active, MediaConnect automatically starts to generate them whenever the flow is active. It generates one thumbnail at most once every second. (For more information about the generation rate, see [How thumbnails are generated](monitor-with-thumbnails.md#thumbnails-how-generated).) You can retrieve the most recently generated thumbnail. ## Enabling thumbnails Use the `CreateFlow` or `UpdateFlow` command. This command is represented differently in different interfaces: + In the AWS CLI, the commands are `create-flow` or `update-flow`. + In the API, the command is an `HTTP POST` on `CreateFlow` or by an `HTTP PUT` on `UpdateFlow`. + In the AWS SDKs, the command is represented by constructs that are suitable to that SDK language. **To enable thumbnails using the AWS CLI** Enter the `create-flow` or `update-flow` command. This example illustrates the `update-flow` command. Replace the ARN with your ARN. ``` aws mediaconnect update-flow --flow-arn arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:AwardsShow --source-monitoring-config ThumbnailState=ENABLED ``` ## Retrieving thumbnails To retrieve thumbnails with the AWS CLI, use the `DescribeFlowSourceThumbnail` command. This command is represented differently in different interfaces: + In the AWS CLI, the command is `describe-flow-source-thumbnail`. + In the API, the command is an `HTTP GET` on `Source-thumbnail`. + In the AWS SDKs, the command is represented by constructs that are suitable to that SDK language. **To retrieve thumbnails using the AWS CLI** Enter the `describe-flow-source-thumbnail` command. Replace the ARN with your ARN. ``` aws mediaconnect describe-flow-source-thumbnail --flow-arn arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:AwardsShow ``` **The response** The request results in a status code and a response. + **Status code 200**: The request was processed successfully. This typically means that the response includes the flow source thumbnail in base64 encoding. However, in some cases, MediaConnect might return a 200 status code even when a thumbnail couldn't be retrieved. In these situations, the response includes an error message explaining why the thumbnail couldn't be generated: + `ThumbnailDecodeError`: The video source doesn't meet [the requirements](thumbnails-specifications.md#thumbnails-source-video-requirements), or there is no ingress traffic on the flow. Therefore, MediaConnect can't generate a thumbnail. + `ThumbnailGenerationInProgress`: The thumbnail is still being generated. Wait a few seconds and try again. + `ThumbnailSuppressed`: Typically this error occurs because the CPU and memory required to process the flow is currently high. If MediaConnect generated thumbnails now, the flow handling would slow down. Try again after a few seconds. If the problem persists, see the information in [Requirements for the flow](thumbnails-specifications.md#thumbnails-flow-requirements). + **Status code 202**: The request is valid, but MediaConnect is still preparing the flow. As a result, a thumbnail can't be generated yet. Wait a few seconds and try again. + **Status code 4xx:** The request isn't valid. + **Status code 5xx**: The request is valid but MediaConnect couldn't fulfill the request. # Monitoring using source metadata Monitoring using source metadataSource stream monitoring: API Detailed information about MediaConnect flow source streams can be viewed using the source metadata monitoring API. Source metadata monitoring displays media information about the transport stream and its programs.Source stream monitoring: Console Detailed information about MediaConnect flow source streams can be viewed using source metadata monitoring in the MediaConnect console. Source metadata monitoring displays media information about the transport stream and its programs.Source stream monitoring: Additional fields Additional information about MediaConnect flow source streams can be viewed using source metadata monitoring in the MediaConnect console and API. Source metadata monitoring displays media information about the transport stream and its programs. MediaConnect source metadata monitoring displays information about the transport stream and its program media. You can view status messages about the flow's source as well as details about the program's video, audio, and other data. Source metadata monitoring can be used with the MediaConnect console, API, AWS CLI, or SDK. For more information about the API, see: [https://docs.aws.amazon.com/mediaconnect/latest/api/v1-flows-flowarn-source-metadata.html](https://docs.aws.amazon.com/mediaconnect/latest/api/v1-flows-flowarn-source-metadata.html) in the *MediaConnect API Reference.* **Note** If you are using more than one source for your flow, source metadata is only displayed for the source currently used by the flow. ## Source metadata details The following sections provide details about the type of information displayed by source metadata monitoring. ### Alerts and messages The **active alerts** section of the **Source metadata** console tab and the **messages** section of the `DescribeFlowSourceMetadata` API/CLI response can contain status messages with more information about the transport stream. If MediaConnect detects an issue or cannot retrieve the source stream metadata, an associated status message will be displayed. ### Programs The **programs** section contains information about the individual programs contained in the transport stream. This section contains the following fields: | Field | Details | | --- | --- | | Program number | The program number of the program. | | Program PID | The program Packet Identifier (PID). | | PCR PID | The Program Clock Reference (PCR) PID of the program. | | Program name | The name of the program. The program name is sourced from the service name value in the Service Description Table (SDT). | | Streams | The nested sections contain info about the video, audio, and data stream types. | ### Streams The **streams** section is nested within each individual transport stream program. This section contains the following fields: | Field | Details | | --- | --- | | Stream type | The type of content that the stream contains. This value can be video, audio, data, or unknown. | | Codec | The codec of the stream. This value will vary depending on the type of stream. Example: a video stream type might display a value of H264 while an audio stream type displays AAC. | | PID | The Packet Identifier (PID) of the stream. | | Frame rate | The frame rate of the video stream, displayed in frames-per-second (fps). | | Frame resolution | The resolution of the video stream. In the console, this field will display the frame width followed by the frame height. Example: A frame width of 1920 and a frame height of 1080 is displayed in the console as `1920 x 1080`.In the API/CLI response, the frame height and frame width are displayed as separate values. | | Channels | The number of channels in the audio stream. | | Sample rate | The sample rate of the audio stream. In the API/CLI response, the sample rate is displayed in hertz (Hz). In the console, the sample rate is displayed in Hz, unless it exceeds 1000 Hz, then it is displayed in kilohertz (kHz). | | Sample size | The sample size of the audio stream. The sample size is displayed in bits. | ## Using source metadata monitoring (console) You can retrieve the latest source metadata from MediaConnect by using the console. 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. From the **Flows** screen, select the flow you want to inspect. 1. Select the **Source metadata** tab. 1. The **source metadata** tab contains an expandable list of every active alert, program, and stream for the selected flow's source. ## Using source metadata monitoring (AWS CLI) You can retrieve the latest source metadata from MediaConnect by using the AWS CLI. The following example shows the AWS CLI command and return value for a typical scenario. 1. In the AWS CLI, use the `describe-flow-source-metadata` command with the `--flow-arn` option of the flow you want to inspect. ``` aws mediaconnect describe-flow-source-metadata --flow-arn arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:AwardsShow ``` 1. The return value will contain the media information for the selected flow's source. The following is a generic example of the format of the return value. In this example, there are no messages to display. ``` { "FlowArn": "arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:AwardsShow", "Messages": [], "Timestamp": "2023-12-06T19:57:54Z", "TransportMediaInfo": { "Programs": [ { "PcrPid": 1000, "ProgramNumber": 1, "ProgramPid": 2000, "ProgramName": "AwardsShow HD", "Streams": [ { "Codec": "H264", "FrameRate": "59.94", "FrameResolution": { "FrameHeight": 1080, "FrameWidth": 1920 }, "Pid": 256, "StreamType": "Video" }, { "Channels": 1, "Codec": "AAC", "Pid": 257, "SampleRate": 50, "SampleSize": 16, "StreamType": "Audio" }, { "StreamType": "Data", "Codec": "SCTE35", "Pid": 258 } ] } ] } } ``` ### Example source metadata API/CLI response The following is another example of the response from the `DescribeFlowSourceMetadata` API/CLI. In this example, there are two programs. Each program has one video stream and two audio streams. The first program has a SCTE-35 data stream. The second program has an invalid stream type on PID 139. The invalid stream type is indicated by the status code in the messages section and the `Unknown` stream type in the program section. ``` { "FlowArn": "arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:BasketballGame", "TransportMediaInfo": { "Messages": [ { "StatusCode": "InvalidType", "Message": "We could not determine the type of pid 139 on program 2" } ], "Programs": [ { "ProgramNumber": 1, "ProgramPid": 16, "PcrPid": 56, "ProgramName": "Basketball HD", "Streams": [ { "Codec": "H264", "FrameRate": "59.94", "FrameResolution": { "FrameHeight": 1080, "FrameWidth": 1920 }, "Pid": 126, "StreamType": "Video" }, { "Channels": 1, "Codec": "AAC", "Pid": 127, "SampleRate": 50, "SampleSize": 16, "StreamType": "Audio" }, { "Channels": 1, "Codec": "AAC", "Pid": 128, "SampleRate": 50, "SampleSize": 16, "StreamType": "Audio" }, { "StreamType": "Data", "Codec": "SCTE35", "Pid": 129 } ] }, { "ProgramNumber": 2, "ProgramPid": 26, "PcrPid": 66, "ProgramName": "Basketball SD", "Streams": [ { "Codec": "H264", "FrameRate": "29.97", "FrameResolution": { "FrameHeight": 480, "FrameWidth": 640 }, "Pid": 136, "StreamType": "Video" }, { "Channels": 1, "Codec": "AAC", "Pid": 137, "SampleRate": 50, "SampleSize": 16, "StreamType": "Audio" }, { "Channels": 1, "Codec": "AAC", "Pid": 138, "SampleRate": 50, "SampleSize": 16, "StreamType": "Audio" }, { "StreamType": "Unknown", "Codec": "Unknown", "Pid": 139 } ] } ] }, } ``` # Monitoring flow and source health Monitoring flow and source health On the AWS Elemental MediaConnect console, you can monitor the health of your flows and their sources. *Flow* health indicates if your flow is not connected due to an issue with an entitlement or encryption. *Source* health indicates if your source is connected. If it is, the console shows Amazon CloudWatch metrics that provide the status of the source over a period of time. **Topics** + [ # Monitoring the health of a MediaConnect flow ](monitor-flow-health.md) + [ # Monitoring the health of a MediaConnect source ](monitor-source-health.md) # Monitoring the health of a MediaConnect flow Monitoring flow health The **Alerts** tab on the MediaConnect console displays a list of alerts that occurred when you started or stopped the current flow. For the full list of alerts for a flow, see Amazon CloudWatch. MediaConnect displays the following alerts on the **Alerts** tab: + Contextual error messages about your flow, called [**stream errors**](#monitor-flow-health-stream-alerts). + The entitlement that this flow is based on is already in use. This occurs if you create more than one flow based on the same entitlement. If the one of those flows is already running, MediaConnect displays an alert if you try to start the second flow. + The entitlement that this flow is based on no longer exists. This occurs if the account that granted the entitlement (the content originator) revokes the entitlement. + The entitlement that this flow is based on does not have an active source. This occurs if the originator's flow is deleted or stopped. When you start your flow based on that entitlement, there is no content coming from the originator's flow. + The decryption or encryption information for the flow isn't valid. This can happen for a number of reasons. For example, the decryption key doesn't match the type for the specified algorithm. Or, your flow is based on an entitlement that uses SPEKE encryption and MediaConnect can't contact the conditional access (CA) platform key provider. + Your flow is based on an entitlement, and the content originator's flow already has the maximum number of outputs. ## Stream errors Stream errorsMediaConnect Alerts: stream errors The user guide has been updated to include information about stream error Alerts. MediaConnect **Alerts** can also contain contextual errors for the flow's sources and outputs. These are called *stream errors* and follow a specific format. + Source *source name* Stream Error: *error message*. Please investigate the flow source. + Output *output name* Stream Error: *error message*. Please investigate the flow output. The error message will provide more context for the issue and you can use it as an indicator of where to begin troubleshooting. **Example** If you received the following alert on a flow named *NationalBroadcast*: Source *StudioFeed2* Stream Error: *CDI Configuration Error*. Please investigate the flow source. This would indicate an error with the inbound CDI at the source. Specifically, your next step should be to verify the settings for the *StudioFeed2* source on the flow named *NationalBroadcast*. You would need to pay special attention to the CDI-specific source settings such as the **inbound port**, the **VPC interface** being used, and the **media streams**. ## Viewing flow alerts Viewing flow alerts **To view any active alerts (console)** 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. On the **Flows** page, choose the name of the flow. 1. Choose the **Alerts** tab. The service displays a list of alerts, if there are any, on the flow. # Monitoring the health of a MediaConnect source Monitoring source healthSource health metrics In the MediaConnect console, you can view Amazon CloudWatch metrics that show the health of the source over a period of time. In the AWS Elemental MediaConnect console, you can view Amazon CloudWatch metrics that show the health of the source over a period of time. Source health is reported with the following metrics: + **Source bitrate** – The bitrate of the incoming video. + **Total packets received** – The total number of packets that MediaConnect received. **To monitor the health of a source (console)** 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. On the **Flows** page, choose the name of the flow. 1. Choose the **Source** tab and view the status of your source. This includes: + The **Source health** field provides the current status of the source. + **Connected** indicates that the flow is connected successfully to its source. + **Disconnected** indicates that the flow is not connected to its source. To resolve this issue, verify that the source is actually sending content. Also, check the source settings on the flow such as the allowlist CIDR and the protocol configuration. + **The flow is inactive** indicates that the flow has not been started. To resolve this issue, [start the flow](flows-start.md). + **Error** indicates that MediaConnect doesn't have permission to communicate with CloudWatch. To resolve the error, you must sign in to the AWS Management Console as an entity that allows MediaConnect to get metric statistics from CloudWatch. For guidance, see [this example](security_iam_id-based-policy-examples.md#security_iam_id-based-policy-examples-console). + The **Source health metrics** section is visible only if your source health is **Connected**. The charts show source bitrate and total packets received over the last hour. You can choose different time periods from the dropdown in the top-right corner of the section. **Note** MediaConnect refreshes data from CloudWatch automatically every 1 minute, 5 minutes, or 30 minutes, depending on the time period that you chose. When the charts refresh, data is 1 minute behind real time. # Monitoring AWS Elemental MediaConnect with Amazon CloudWatch metrics Monitoring with CloudWatch metricsMediaConnect high resolution metrics MediaConnect metrics can now be viewed in intervals as short as one second. You can monitor AWS Elemental MediaConnect using CloudWatch, which collects raw data and processes it into readable, near real-time metrics. These metrics are kept for 15 months, so that you can access historical information and gain a better perspective on how your web application or service is performing. Most MediaConnect metrics can be accessed in periods as short as one second. You can also set alarms that watch for certain thresholds, and send notifications or take actions when those thresholds are met. For more information, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/). You can view CloudWatch metrics for your flows directly on the MediaConnect console. On the console, you can view these metrics in periods as short as one second or as long as 30 minutes. **Note** MediaConnect Gateway metrics are not available in high resolution periods (one second). You must select a period of at least one minute. # Definition of a metric for MediaConnect datapoints Definition of a metric AWS Elemental MediaConnect collects data that is the basis for metrics. It collects these *datapoints* every second and sends them immediately to Amazon CloudWatch. You can use CloudWatch to generate *metrics* for these datapoints. A metric is a collection of datapoints that has had an aggregation (a *statistic*) applied and that has a *period* and a *time range*. For example, you can request the Dropped packets metric as an average (the statistic) for a 1 minute period over 10 minutes (the time range). This result of this request is 10 metrics (because the range divided by the period is 10). ## Period Most MediaConnect metrics have a *high resolution period*, which means that the minimum period is one second. MediaConnect Gateway metrics are the only metrics not available in a high resolution period. ## Time range Each period has a *maximum time range*. For example, if you specify 1 day as the time range, you won't be able to retrieve metrics with a 10 second period. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metric-info.html) Periods don't have a *minimum time range*. But there is a point where the statistic you apply becomes meaningless if you have a low period. For example, assume that you set the period to one second. This means that CloudWatch retrieves one datapoint. You can't obtain an average, a minimum or a maximum on one datapoint. However, this doesn't mean that the metric is meaningless. Instead, the metric is for the raw datapoint, with no statistic. ## Maximum storage time Metrics are available for the last 15 months. Make sure that you specify a period that allows the time range that you want. # Viewing metrics for a MediaConnect flow Viewing metrics You can view some metrics in the MediaConnect console. You can view all metrics in the CloudWatch console. You can also retrieve metrics using the CLI, the REST API, or any AWS SDK. On the CloudWatch console, the minimum refresh rate for metrics is 30 seconds. **To view metrics on the MediaConnect console** You can view some metrics in the MediaConnect console. You can view the current metrics, going back from 1 hour to 1 week. (To view other metrics or to view historical metrics, you must use the CloudWatch console.) 1. Open the MediaConnect console at [https://console.aws.amazon.com/mediaconnect/](https://console.aws.amazon.com/mediaconnect/). 1. In the navigation pane, choose **Flows**. On the **Flows** page, choose the flow you want. The **Details** page appears. 1. Choose the **Health** tab. The metrics that MediaConnect supports on this tab appears. 1. Choose the period and time range. For example, **Past 1 day (5 min period)**. **To view metrics using the CloudWatch console** On the CloudWatch console you can view all MediaConnect metrics for any range of time — the current metrics or historical metrics. There is a charge to view metrics on the CloudWatch console. 1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/). 1. In the navigation pane, choose **Metrics**, then choose **All metrics**. In the bottom half of the page, the **Browse** tab shows cards with names. No cards appear if you are completely new to AWS, and you haven't performed an action that creates metrics in any service. 1. Select the card that is named **AWS/MediaConnect**. This card appears only if you have started at least one flow in the last 15 months in the AWS Region that is currently selected for CloudWatch. This card won't appear if have never started a MediaConnect flow. In this case, come back to this procedure after you have created and started a flow. (A card named **MediaConnect** might appear in the custom namespace section of the page. This card is for the old namespace for MediaConnect metrics. The two namespaces became duplicates of each other in September of 2022, so there is no advantage to choosing this card. Always choose **AWS/MediaConnect**.) 1. The **Browse** tab in the bottom half of the page now shows dimensions. Choose a metric dimension. For example, choose **Flow ARN**. The **Browse** tab now shows a table with one column that shows the chosen dimension (for example, Flow ARN) and one column that shows all the metrics. You can sort the table. 1. Select one or more rows. As soon as you select a row, it appears in the graph in the top half of the page. 1. In the bottom half of the page, choose the **Graphed metrics** tab. 1. On the choices on the right of the tab, specify the **Statistic** and the **Period**. When you choose the period, the graph refreshes to show the [maximum time range for that period](monitor-with-cloudwatch-metric-info.md#emx-metrics-about-time-range). If the graph is now empty on the left, you can adjust the timeline in the choices at the top right of the graph. Choose a lower number so that the full space is filled up. For example, change **1w** to **1d**. **To view metrics using the AWS CLI** + At a command prompt, use the following command: ``` aws cloudwatch list-metrics --namespace "AWS/MediaConnect" ``` # AWS Elemental MediaConnect metrics to monitor flow health Metrics to monitor flow health AWS Elemental MediaConnect sends metrics to CloudWatch. You can review specific metrics to evaluate the health of your flow. If the flow is unhealthy, these metrics can help you determine where the issue originates. For details about each metric, see the tables in this section. For information about source metrics, see [Metrics to monitor flow source health](monitor-with-cloudwatch-metrics-source-health.md). **Note** Metrics tracked by MediaConnect adhere to the standard as defined by the TR 101 290 spec. **Topics** + [ ## Flow metrics ](#monitor-with-cloudwatch-metrics-flow-health-flow) + [ ## TR 101 290 Priority 1 metrics ](#monitor-with-cloudwatch-metrics-flow-health-p1) + [ ## TR 101 290 Priority 2 metrics ](#monitor-with-cloudwatch-metrics-flow-health-p2) + [ ## Content quality metrics ](#monitor-with-cloudwatch-metrics-content-quality-metrics) + [ ## Maintenance metrics ](#monitor-with-cloudwatch-metrics-flow-health-maintenance) ## Flow metrics The following table lists network metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | ARQRecovered | The number of dropped packets that were recovered by automatic repeat request (ARQ). This metric doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. For flows that have multiple sources, use the SourceARQRecovered metric to view data for each source. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | ARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ) and received. This metric doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. For flows that have multiple sources, use the SourceARQRequests metric to view data for each source. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | BitRate | The bitrate of the incoming (source) video. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | Connected | The status of the source. A value of 1 indicates that the source is connected and a value of 0 (zero) indicates that the source is disconnected. This metric applies only to sources that use the Zixi, SRT, or RIST protocols. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | ConsecutiveDrops | The number of data packets that were dropped in a row during transmission of data to or from MediaConnect. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | ConsecutiveNotRecovered | The number of data packets that were not recovered in a row. After a data packet is dropped, error correction attempts to recover that packet. This metric helps to identify extended periods of data packets that were dropped and not recovered. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | Disconnections | The number of times that the source status changed from connected to disconnected. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | DroppedPackets | The number of packets that were lost during transit. This value is measured before any error correction takes place. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | FailoverSwitches | The total number of times the flow switches back and forth between sources when using the * Failover* mode for source failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | FECPackets | The number of packets that were transmitted using forward error correction (FEC) and received. This metric applies only to flows that have one source that uses the RTP-FEC or Zixi protocols. It doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. For flows that have multiple sources, use the SourceFECPackets metric to view data for each source. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | FECRecovered | The number of packets that were transmitted using forward error correction (FEC), lost during transit, and recovered. This metric applies only to flows that have one source that uses the RTP-FEC or Zixi protocols. It doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. For flows that have multiple sources, use the SourceFECRecovered metric to view data for each source. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MergeActive | The merge status of all sources on the flow. A value of 1 indicates that all sources are merged. A value of 0 (zero) indicates that at least one source is not actively merged with 2022-7. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MergeLatency | The maximum value for SourceMergeLatency. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | NotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | OverflowPackets | The number of packets that were lost in transit because the video required more buffer than was available. This metric doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PacketLossPercent | The percentage of packets that were lost during transit, even if they were recovered. Units: Percent Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | RecoveredPackets | The number of packets that were lost during transit, but recovered. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | RoundTripTime | The amount of time it takes for the source to send a signal and receive an acknowledgment from AWS Elemental MediaConnect. This metric doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. For flows that have multiple sources, use the SourceRoundTripTime metric to view data for each source. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | TotalPackets | The total number of packets that were received. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | ## TR 101 290 Priority 1 metrics The following table lists TR 101 290 Priority 1 metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | ContinuityCounter | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PATError | The number of times that a program association table (PAT) error occurred. This error indicates that the PAT is missing. The PAT lists the programs that are available in a transport stream (TS) and points to the program map tables (PMTs). The decoder needs the PAT to do its job. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PIDError | The number of times that a packet identifier (PID) error occurred. This error indicates that a PID is missing its associated data stream. The PIDs are identifiers that provide the location of the video, audio, and data streams. This error can occur after the transport stream has been multiplexed and then remultiplexed. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PMTError | The number of times that a program map table (PMT) error occurred. This error happens when the PMT is not received at least every 500 milliseconds (ms). Each PMT contains a list of PIDs, which help decoders reassemble data. The decoder needs the PMTs to do its job. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | TSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | TSSyncLoss | The number of times that a TS sync loss error occurred. This error happens after two or more consecutive TS byte errors. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | ## TR 101 290 Priority 2 metrics The following table lists TR 101 290 Priority 2 metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | CATError | The number of times that a conditional access table (CAT) error occurred. This error indicates that the CAT is not present. The CAT tells the integrated receiver decoder (IRD) where to find management messages for the conditional access (CA) systems that are in use. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | CRCError | The number of times that a cyclic redundancy check (CRC) error occurred. This error happens when a CRC determines that data is corrupted. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PCRAccuracyError | The number of times that a program clock register (PCR) accuracy error occurred. This error happens when the value of the transmitted PCR differs from what is expected by more than 500 nanoseconds (ns). When a stream is encoded, the encoder assigns periodic PCR values of the encoder's program clock. The decoder relies on these values to ensure that the stream is kept in sync. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PCRError | The number of times that a PCR error occurred. This error happens when PCR values are not sent frequently enough. The service relies on consistent, frequent PCRs to reset the local 27 MHz system clock. Although the error occurs when the interval exceeds 100 milliseconds (ms), best practices dictate that PCRs should be received at least every 40 ms. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | PTSError | The number of times that a presentation timestamp (PTS) error occurred. This error happens when a presentation timestamp (PTS) is not received at least every 700 ms. This can occur if the PTS is sent less frequently or not at all. The most common cause of this error is when the transport stream (TS) is scrambled. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | TransportError | The number of times that a primary transport error occurred. This error indicates that the TS packet is unusable. When this error occurs, ignore all other TR 101 290 errors for this packet. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | ## Content quality metrics The following table lists the content quality metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | AudioStreamMissing | Monitors instances when the expected audio stream is not detected in the content. A value of 1 indicates that the audio stream is missing from the source. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | BlackFramesBreaching | Monitors instances when the duration of black frames in the video exceeds the specified threshold. A value of 1 indicates that the duration is breaching the specified threshold and a value of 0 (zero) indicates that the duration is not breaching the specified threshold. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | FrozenFramesBreaching | Monitors instances when the video remains unchanged for longer than the specified threshold. A value of 1 indicates that the duration is breaching the specified threshold and a value of 0 (zero) indicates that the duration is not breaching the specified threshold. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | SilentAudioBreaching | Monitors instances when the duration of silent audio exceeds the specified threshold. A value of 1 indicates that the duration is breaching the specified threshold and a value of 0 (zero) indicates that the duration is not breaching the specified threshold. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | TimecodePresent | Indicates whether a valid timecode is present in the media stream. A value of 1 indicates that a valid timecode is present in the media stream and a value of 0 (zero) indicates that a valid timecode is not present in the media stream. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | VideoStreamMissing | Monitors instances when the expected video stream is absent from the content. A value of 1 indicates that the video stream is missing from the source. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | ## Maintenance metrics Maintenance CloudWatch metrics The user guide has been updated to include new CloudWatch metrics for MediaConnect maintenance. The following table lists flow maintenance metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | MaintenanceCanceled | Maintenance for this flow is cancelled by MediaConnect. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MaintenanceFailed | Maintenance did not complete successfully for this flow. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MaintenanceRescheduled | MediaConnect is unable to perform maintenance at the previously scheduled date and time. A new date and time has been automatically assigned by MediaConnect for this flow's maintenance. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MaintenanceScheduled | Maintenance is scheduled for the flow. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MaintenanceStarted | Maintenance has started and is currently in progress for this flow. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | | MaintenanceSucceeded | Maintenance completed successfully for this flow. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-flow-health.html) | # AWS Elemental MediaConnect metrics to monitor flow source health Metrics to monitor flow source health AWS Elemental MediaConnect sends metrics to CloudWatch. You can review specific metrics to evaluate the health of the source of your flow. If the flow is unhealthy, these metrics can help you determine whether the issue originates with the source. For details about each metric, see the tables in this section. For information about flow metrics, see [Metrics to monitor flow health](monitor-with-cloudwatch-metrics-flow-health.md). **Note** Metrics tracked by MediaConnect adhere to the standard as defined by the TR 101 290 spec. **Topics** + [ ## Source metrics for transport stream protocols ](#monitor-with-cloudwatch-metrics-source-health-source) + [ ## Source metrics for NDI® ](#monitor-with-cloudwatch-metrics-source-health-source-ndi) + [ ## Source metrics for CDI ](#monitor-with-cloudwatch-metrics-source-health-source-cdi) + [ ## Source metrics for router connections ](#monitor-with-cloudwatch-metrics-source-health-source-router) + [ ## TR 101 290 Priority 1 metrics ](#monitor-with-cloudwatch-metrics-source-health-p1) + [ ## TR 101 290 Priority 2 metrics ](#monitor-with-cloudwatch-metrics-source-health-p2) ## Source metrics for transport stream protocols The following table lists source metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | SourceARQRecovered | The number of dropped packets that were recovered by automatic repeat request (ARQ). This metric applies to sources that use the RIST, Zixi, or SRT protocol. It doesn't apply to flows that receive content from an entitlement. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ) and received. This metric applies to sources that use the RIST, Zixi, or SRT protocol. It doesn't apply to flows that receive content from an entitlement. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceBitRate | The bitrate of the incoming (source) video. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) Both MediaConnect and the Zixi protocol use bandwidth optimization techniques that can affect bitrate measurements: In flows with Zixi sources, Zixi often optimizes network usage by substituting repetitive content packets with null packets. For entitlements, MediaConnect performs similar optimization between the content originator's flow and the subscriber's flow. For example, in a 30 Mbps stream with repetitive content (like a black slate), either optimization might reduce the bitrate to 5 Mbps. These bitrate fluctuations are normal and don't affect content quality, but they might be noticeable in your bitrate monitoring. We recommend that you monitor source health as a combination of `SourceBitRate` and other metrics such as `SourceContinuityCounter` and `SourceNotRecoveredPackets`. | | SourceConnected | The status of the source. A value of 1 indicates that the source is connected and a value of 0 (zero) indicates that the source is disconnected. This metric applies only to sources that use the Zixi or SRT protocol. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceDisconnections | The number of times that the source status changed from connected to disconnected. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceDroppedPackets | The number of packets that were lost during transit. This value is measured before any error correction takes place. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceFECPackets | The number of packets that were transmitted using forward error correction (FEC) and received. This metric applies only to sources that use the RTP-FEC or Zixi protocols. It doesn't apply to flows that receive content from an entitlement. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceFECRecovered | The number of packets that were transmitted using forward error correction (FEC), lost during transit, and recovered. This metric applies only to sources that use the RTP-FEC or Zixi protocols. It doesn't apply to flows that receive content from an entitlement. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceMergeActive | An indication of the status of the source with respect to other sources. This metric is useful when the flow has multiple sources for failover and you are using the Merge failover mode. A value of 1 indicates that the flow has multiple sources and that this source is actively in use, with 2022-7 merge. A value of 0 (zero) indicates that the flow is not using the source to form the stream. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceSelected | An indication if a source is being used as the input for flow ingest. This metric applies if your flow uses source failover, and the failover mode is set to *Failover*. A value of 1 indicates that the source is being used as the input. A value of 0 (zero) indicates that the flow is being used as the backup stream. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceMergeLatency | The amount of time that this source trails the primary source. If this source is the primary source, the value is 0 (zero). Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceMergeStatusWarnMismatch | A status metric warning that the flow is receiving mismatched sources. This means that any dropped packets will not be recovered and will result in poor network reliability. This metric only applies to sources using merge mode failover. Merge mode failover requires both sources to be binary identical. To be binary identical, the sources must originate from the same encoder. This will ensure the sources can share missing packets, as the packets are identical.Units: CountValid dimensions:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceMergeStatusWarnSolo | A status metric warning that the flow is only receiving one source. This means any dropped packets will not be recovered and will result in poor network reliability. This metric only applies to sources using **merge mode** failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceMissingPackets | A packet was missing from both source streams, this means the packet could not be recovered. This metric only applies to sources using **merge mode** failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceOverflowPackets | The number of packets that were lost in transit because the video required more buffer than was available. This metric doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePacketLossPercent | The percentage of packets that were lost during transit, even if they were recovered. Units: Percent Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceRecoveredPackets | The number of packets that were lost during transit, but recovered. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceRoundTripTime | The amount of time it takes for the source to send a signal and receive an acknowledgment from AWS Elemental MediaConnect. This metric applies to sources that use the RIST, Zixi, or SRT protocol. It doesn't apply to flows that receive content from an entitlement. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTotalPackets | The total number of packets that were received. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTotalBytes | Total amount of bytes transferred to MediaConnect from the source. Units: Bytes Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceConsecutiveDrops | The number of data packets that were dropped in a row during transmission of data to MediaConnect. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceConsecutiveNotRecovered | The number of data packets that were not recovered in a row. After a data packet is dropped, error correction attempts to recover that packet. This metric helps to identify extended periods of data packets that were dropped and not recovered. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceJitter | The current network jitter, measured in milliseconds. Network jitter is a measurement of changes in latency. An increase in network jitter indicates inconsistency in the latency and can negatively impact quality. Units: milliseconds (ms) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceLatency | The stream latency of the source. Latency is the time it takes for data packets to travel from your source to MediaConnect. Units: milliseconds (ms) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceUptime | The number of seconds that the source has been active. If the source is disconnected or has a connection timeout, this metric resets to zero. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | ## Source metrics for NDI® The following table lists NDI source metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | SourceAudioFrames | The number of audio frames received by the NDI source. This metric applies to NDI sources only. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceConnected | The status of the source. A value of 1 indicates that the source is connected to an NDI sender and a value of 0 (zero) indicates that the source is disconnected. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceDiscoveredSources | The total number of available NDI senders discovered by the NDI source. This metric applies to NDI sources only. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceVideoFrames | The number of video frames received by the NDI source. This metric applies to NDI sources only. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | ## Source metrics for CDI The following table lists CDI source metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | SourceDroppedPayloads | Payloads that were lost during transit to MediaConnect from the source. A payload is a frame of video or an audio sample. Payloads can consist of multiple packets. Payload metrics are only applicable when using CDI. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceLatePayloads | Packets of a payload that arrive outside of the configured **Max sync buffer** time frame. A payload is a frame of video or an audio sample. Payloads can consist of multiple packets. Payload metrics are only applicable when using CDI. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTotalPayloads | Total amount of payloads delivered to MediaConnect from the source. A payload is a frame of video or an audio sample. Payloads can consist of multiple packets. Payload metrics are only applicable when using CDI. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | ## Source metrics for router connections The following table lists source metrics that AWS Elemental MediaConnect sends to CloudWatch when a flow source receives content from a router output. | Metric | Description | | --- | --- | | SourceBitRate | The bitrate of the incoming (source) video. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceContinuityCounter | The number of continuity counter errors in the transport stream. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceLatency | The stream latency of the source. Latency is the time it takes for data packets to travel from the source to MediaConnect. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceRecoveredPackets | The number of packets that were recovered through retransmission. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTotalPackets | The total number of packets that were received. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceUptime | The number of seconds that the source has been active. If the source is disconnected or has a connection timeout, this metric resets to zero. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | In addition to the preceding metrics, all TR 101 290 Priority 1 and Priority 2 metrics are also published for router-connected sources. For details about those metrics, see [TR 101 290 Priority 1 metrics](#monitor-with-cloudwatch-metrics-source-health-p1) and [TR 101 290 Priority 2 metrics](#monitor-with-cloudwatch-metrics-source-health-p2). ## TR 101 290 Priority 1 metrics The following table lists TR 101 290 Priority 1 metrics that AWS Elemental MediaConnect sends to CloudWatch. These metrics apply only to transport stream protocols. | Metric | Description | | --- | --- | | SourceContinuityCounter | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePATError | The number of times that a program association table (PAT) error occurred. This error indicates that the PAT is missing. The PAT lists the programs that are available in a transport stream (TS) and points to the program map tables (PMTs). The decoder needs the PAT to do its job. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePIDError | The number of times that a packet identifier (PID) error occurred. This error indicates that a PID is missing its associated data stream. The PIDs are identifiers that provide the location of the video, audio, and data streams. This error can occur after the TS has been multiplexed and then remultiplexed. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePMTError | The number of times that a program map table (PMT) error occurred. This error happens when the PMT is not received at least every 500 milliseconds (ms). Each PMT contains a list of PIDs, which help decoders reassemble data. The decoder needs the PMTs to do its job. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTSByteError | The number of times that a TS byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTSSyncLoss | The number of times that a TS sync loss error occurred. This error happens after two or more consecutive TS byte errors. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | ## TR 101 290 Priority 2 metrics The following table lists TR 101 290 Priority 2 metrics that AWS Elemental MediaConnect sends to CloudWatch. These metrics apply only to transport stream protocols. | Metric | Description | | --- | --- | | SourceCATError | The number of times that a conditional access table (CAT) error occurred. This error indicates that the CAT is not present. The CAT tells the integrated receiver decoder (IRD) where to find management messages for the conditional access (CA) systems that are in use. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceCRCError | The number of times that a cyclic redundancy check (CRC) error occurred. This error happens when a CRC determines that data is corrupted. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePCRAccuracyError | The number of times that a program clock register (PCR) accuracy error occurred. This error happens when the value of the transmitted PCR differs from what is expected by more than 500 nanoseconds (ns). When a stream is encoded, the encoder assigns periodic PCR values from the encoder's program clock. The decoder relies on these values to ensure that the stream is kept in sync. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePCRError | The number of times that a PCR error occurred. This error happens when PCR values are not sent frequently enough. The service relies on consistent, frequent PCRs to reset the local 27 MHz system clock. Although the error occurs when the interval exceeds 100 milliseconds (ms), best practices dictate that PCRs should be received at least every 40 ms. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourcePTSError | The number of times that a presentation timestamp (PTS) error occurred. This error happens when a presentation timestamp (PTS) is not received at least every 700 ms. This can occur if the PTS is sent less frequently or not at all. The most common cause of this error is when the TS is scrambled. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | | SourceTransportError | The number of times that a primary transport error occurred. This error indicates that the TS packet is unusable. When this error occurs, ignore all other TR 101 290 errors for this packet. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-source-health.html) | # AWS Elemental MediaConnect metrics to monitor flow output health Metrics to monitor flow output health AWS Elemental MediaConnect sends metrics to CloudWatch. You can review specific metrics to evaluate the health of the output of your flow. **Topics** + [ ## Output metrics for transport stream protocols ](#monitor-with-cloudwatch-metrics-output-health-ts) + [ ## Output metrics for NDI® ](#monitor-with-cloudwatch-metrics-output-health-ndi) + [ ## Output metrics for CDI protocols ](#monitor-with-cloudwatch-metrics-output-health-cdi) + [ ## Output metrics for router connections ](#monitor-with-cloudwatch-metrics-output-health-router) ## Output metrics for transport stream protocols | Metric | Description | | --- | --- | | ConnectedOutputs | The number of outputs that are currently connected. This metric applies to outputs that use the Zixi or SRT protocol. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ) and received. This metric applies to outputs that use the SRT protocol or output to MediaLive. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputBitrate | The bitrate of the outgoing (output) video. This metric applies to outputs that use the SRT protocols or output to MediaLive. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) Both MediaConnect and the Zixi protocol use bandwidth optimization techniques that can affect bitrate measurements: In flows with Zixi outputs, Zixi often optimizes network usage by substituting repetitive content packets with null packets. For entitlements, MediaConnect performs similar optimization between the content originator's flow and the subscriber's flow. For example, in a 30 Mbps stream with repetitive content (like a black slate), either optimization might reduce the bitrate to 5 Mbps. These bitrate fluctuations are normal and don't affect content quality, but they might be noticeable in your bitrate monitoring. Additionally, the `OutputBitrate` value can vary depending on the selected protocol due to non-payload packets, retransmitted packets, packet headers, and other protocol-specific packets. Due to these factors, the bitrate value reported by this metric might vary between outputs. | | OutputConnected | The status of the output. A value of 1 indicates that the output is connected, and a value of 0 (zero) indicates that the output is disconnected. This metric applies to outputs that use the Zixi or SRT protocol. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputDisconnections | The number of times that the output status changed from connected to disconnected. This metric applies to outputs that use the Zixi or SRT protocol. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. This metric applies to outputs to MediaLive. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputResentPackets | The number of packets that were retransmitted to the output destination. This metric applies to outputs that use the SRT protocol or output to MediaLive. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputRoundTripTime | The amount of time it takes for the output to send a signal and receive an acknowledgment from the output destination. This metric applies to outputs that use the SRT protocol or output to MediaLive. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputTotalPackets | The total number of packets that were sent to the output. This metric applies to outputs that use the SRT protocols or output to MediaLive. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | ## Output metrics for NDI® | Metric | Description | | --- | --- | | OutputConnectedReceivers | The number of NDI receivers that are connected to the flow output. This metric applies to NDI outputs only. Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputGeneratedAudioSamples | The number of audio samples that are sent to each individual NDI receiver. This metric applies to NDI outputs only. This metric is published even if no receivers are currently connected. If multiple receivers are connected, keep in mind this value represents the number sent to each receiver, not the total across all receivers. The value is not multiplied based on the number of receivers. Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputGeneratedVideoFrames | The number of video frames that are sent to each individual NDI receiver. This metric applies to NDI outputs only. This metric is published even if no receivers are currently connected. If multiple receivers are connected, keep in mind this value represents the number sent to each receiver, not the total across all receivers. The value is not multiplied based on the number of receivers. Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | ## Output metrics for CDI protocols | Metric | Description | | --- | --- | | OutputDroppedPayloads | Payloads that were lost during transit from MediaConnect to the output. A payload is a frame of video or an audio sample. Payloads can consist of multiple packets. Payload metrics are only applicable when using CDI. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputLatePayloads | Packets of a payload that arrive at the output outside of MediaConnect's internal buffer. A payload is a frame of video or an audio sample. Payloads can consist of multiple packets. Payload metrics are only applicable when using CDI. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputTotalBytes | Total amount of bytes transferred from MediaConnect to the output. This metric is only applicable when using CDI. Units: Bytes Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputTotalPayloads | Total amount of payloads delivered from MediaConnect to the output. A payload is a frame of video or an audio sample. Payloads can consist of multiple packets. Payload metrics are only applicable when using CDI. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | ## Output metrics for router connections The following table lists source metrics that MediaConnect sends to CloudWatch when a flow output sends content to a router input. | Metric | Description | | --- | --- | | OutputEnabled | The status of the output. A value of 1 indicates that the output is enabled, and a value of 0 (zero) indicates that the output is disabled. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | | OutputBitrate | The bitrate of the outgoing (output) video. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-output-health.html) | # AWS Elemental MediaConnect metrics to monitor router input health Metrics to monitor router input health AWS Elemental MediaConnect sends metrics to CloudWatch. You can review specific metrics to evaluate the health of your router inputs. For details about each metric, see the tables in this section. For information about flow metrics, see [Metrics to monitor flow health](monitor-with-cloudwatch-metrics-flow-health.md). **Topics** + [ ## Router input metrics ](#monitor-with-cloudwatch-metrics-router-input) + [ ## Failover metrics for router inputs ](#monitor-with-cloudwatch-metrics-router-input-failover) + [ ## Merge metrics for router inputs ](#monitor-with-cloudwatch-metrics-router-input-merge) + [ ## Router input metrics for MediaConnect flow connections ](#monitor-with-cloudwatch-metrics-router-input-flow) ## Router input metrics The following table lists router input metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | RouterInputARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ). Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT | | RouterInputBitRate | The bitrate of the payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputCCErrors | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputConnected | The status of the input. A value of 1 indicates that the input is connected, and a value of 0 (zero) indicates that the input is disconnected. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputDisconnections | The number of times that the input status changed from connected to disconnected. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputFECPackets | The number of forward error correction packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP/FEC | | RouterInputJitter | The jitter measurement specific to the protocol being used. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT | | RouterInputLatency | The recovery latency of the input stream. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT, RTP/FEC | | RouterInputNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRecoveredPackets | The number of packets that were recovered through retransmission. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRejections | The number of times the connection was rejected by the peer. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputRoundTripTime | The amount of time it takes for the input to send a signal and receive an acknowledgment. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTotalPackets | The total number of packets received by the input. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101PCRAccuracyError | The number of PCR accuracy errors in the transport stream. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSSyncLoss | The number of transport stream sync loss errors. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputUptime | The amount of time the input has been receiving data. Units: Seconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | ## Failover metrics for router inputs When you configure a router input for failover, MediaConnect collects two sets of metrics: aggregate metrics for the overall router input, as well as source-level metrics to track the individual failover sources. ### Aggregate failover metrics These metrics give you a view of the failover router input's performance. | Metric | Description | | --- | --- | | RouterInputFailoverActiveSource | Index of the currently active source. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputFailoverSwitches | The total number of times the router input has switched sources. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: Protocols: All | | RouterInputPostFailoverBitRate | The bitrate of the payload after failover, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostFailoverCCErrors | The number of continuity errors in the transport stream after failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostFailoverNotRecoveredPackets | The number of unrecovered packets after failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostFailoverRecoveredPackets | The number of recovered packets after failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostFailoverTR101PCRAccuracyError | The number of PCR accuracy errors in the transport stream after failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostFailoverTR101TSByteError | The number of times that a transport stream byte error occurred after failover. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostFailoverTR101TSSyncLoss | The number of transport stream sync loss errors after failover. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | ### Source-level failover metrics For router inputs that are configured for failover, the basic router input metrics are also available with an additional `RouterInputFailoverSourceIndex` dimension. This enables you to monitor the performance of the first failover source (`RouterInputFailoverSourceIndex=0`) and the second failover source (`RouterInputFailoverSourceIndex=1`) separately. | Metric | Description | | --- | --- | | RouterInputARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ). Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT | | RouterInputBitRate | The bitrate of the payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputCCErrors | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputConnected | The status of the input. A value of 1 indicates that the input is connected, and a value of 0 (zero) indicates that the input is disconnected. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputDisconnections | The number of times that the input status changed from connected to disconnected. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputFECPackets | The number of forward error correction packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP/FEC | | RouterInputJitter | The jitter measurement specific to the protocol being used. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT | | RouterInputLatency | The recovery latency of the input stream. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRecoveredPackets | The number of packets that were recovered through retransmission. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRejections | The number of times the connection was rejected by the peer. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputRoundTripTime | The amount of time it takes for the input to send a signal and receive an acknowledgment. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTotalPackets | The total number of packets received by the input. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101PCRAccuracyError | The number of PCR accuracy errors in the transport stream. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSSyncLoss | The number of transport stream sync loss errors. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputUptime | The amount of time the input has been receiving data. Units: Seconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | ## Merge metrics for router inputs Similar to failover, when you configure a router input for merge, MediaConnect provides both aggregate and source-level metrics. ### Aggregate merge metrics These metrics give you a high-level, overall view of the merge input's performance. They include data that applies to the entire merge configuration, without differentiating between the two merge sources. | Metric | Description | | --- | --- | | RouterInputMergeActive | The merge status of all router input sources. A value of 1 indicates that all sources are merged. A value of 0 (zero) indicates that at least one source is not actively merged with 2022-7. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP, RIST | | RouterInputMergeSkew | Maximum time skew between the two router input sources. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html)Protocols: RTP, RIST | | RouterInputPostMergeBitRate | The bitrate of the payload after merge, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP, RIST | | RouterInputPostMergeCCErrors | The number of continuity errors in the transport stream after merge. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP, RIST | | RouterInputPostMergeNotRecoveredPackets | The number of unrecovered packets after merge. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP, RIST | | RouterInputPostMergeRecoveredPackets | The number of recovered packets after merge. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP, RIST | | RouterInputPostMergeTR101PCRAccuracyError | The number of PCR accuracy errors in the transport stream after merge. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostMergeTR101TSByteError | The number of times that a transport stream byte error occurred after merge. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputPostMergeTR101TSSyncLoss | The number of transport stream sync loss errors after merge. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | ### Source-level merge metrics For router inputs that are configured for merge, the basic router input metrics are also available with an additional `RouterInputMergeSourceIndex` dimension. This enables you to monitor the performance of the first merge source (`RouterInputMergeSourceIndex=0`) and the second merge source (`RouterInputMergeSourceIndex=1`) separately. | Metric | Description | | --- | --- | | RouterInputARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ). Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputBitRate | The bitrate of the payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputCCErrors | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputConnected | The status of the input. A value of 1 indicates that the input is connected, and a value of 0 (zero) indicates that the input is disconnected. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputDisconnections | The number of times that the input status changed from connected to disconnected. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputFECPackets | The number of forward error correction packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RTP/FEC | | RouterInputJitter | The jitter measurement specific to the protocol being used. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT | | RouterInputLatency | The recovery latency of the input stream. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRecoveredPackets | The number of packets that were recovered through retransmission. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRejections | The number of times the connection was rejected by the peer. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: SRT | | RouterInputRoundTripTime | The amount of time it takes for the input to send a signal and receive an acknowledgment. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTotalPackets | The total number of packets received by the input. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101PCRAccuracyError | The number of PCR accuracy errors in the transport stream. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSSyncLoss | The number of transport stream sync loss errors. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputUptime | The amount of time the input has been receiving data. Units: Seconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | ## Router input metrics for MediaConnect flow connections When a router input receives content from a MediaConnect flow, MediaConnect sends the following metrics to CloudWatch. | Metric | Description | | --- | --- | | RouterInputBitRate | The bitrate of the payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputCCErrors | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputLatency | The recovery latency of the input stream. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: RIST, SRT, RTP/FEC | | RouterInputNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputRecoveredPackets | The number of packets that were recovered through retransmission. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101PCRAccuracyError | The number of PCR accuracy errors in the transport stream. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputTR101TSSyncLoss | The number of transport stream sync loss errors. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | | RouterInputUptime | The amount of time the input has been receiving data. Units: Seconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-input-health.html) Protocols: All | **Note** When no MediaConnect flow is connected to the router input, the UpstreamFlowOutputName and UpstreamFlowARN dimensions display as ``. # AWS Elemental MediaConnect metrics to monitor router output health Metrics to monitor router output health AWS Elemental MediaConnect sends metrics to CloudWatch. You can review specific metrics to evaluate the health of your router outputs. For details about each metric, see the tables in this section. For information about flow metrics, see [Metrics to monitor flow health](monitor-with-cloudwatch-metrics-flow-health.md). **Topics** + [ ## Standard output metrics ](#monitor-with-cloudwatch-metrics-router-output) + [ ## Router output metrics for MediaConnect flow connections ](#monitor-with-cloudwatch-metrics-router-output-flow) + [ ## Router output metrics for MediaLive connections ](#monitor-with-cloudwatch-metrics-router-output-medialive) + [ ## Route metrics ](#monitor-with-cloudwatch-metrics-router-output-route) ## Standard output metrics The following table lists router standard output metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | RouterOutputARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ). Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: RIST, SRT | | RouterOutputBitRate | The bitrate of the output stream payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: All | | RouterOutputConnected | The status of the output. A value of 1 indicates that the output is connected, and a value of 0 (zero) indicates that the output is disconnected. Units: None Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: SRT | | RouterOutputDisconnections | The number of times that the output status changed from connected to disconnected. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: SRT | | RouterOutputFECPackets | The number of forward error correction packets sent by the output. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: RTP/FEC | | RouterOutputLatency | The latency of the output stream. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: SRT | | RouterOutputRejections | The number of times the connection was rejected by the peer. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: SRT | | RouterOutputResentPackets | The number of packets that were retransmitted to the output destination. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: RIST, SRT | | RouterOutputRoundTripTime | The amount of time it takes for the output to send a signal and receive an acknowledgment. Units: Milliseconds Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: RIST, SRT | | RouterOutputTotalPackets | The total number of packets sent by the output. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: All | ## Router output metrics for MediaConnect flow connections When a router output sends content to a MediaConnect flow, MediaConnect sends the following metrics to CloudWatch. | Metric | Description | | --- | --- | | RouterOutputBitRate | The bitrate of the output stream payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: All | **Note** When no AWS Elemental MediaConnect flow is connected to the router output, the DownstreamFlowSourceName and DownstreamFlowARN dimensions display as ``. ## Router output metrics for MediaLive connections When a router output sends content to a MediaLive input, MediaConnect sends the following metrics to CloudWatch. | Metric | Description | | --- | --- | | RouterOutputBitRate | The bitrate of the output stream payload, not including protocol overhead. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: All | **Note** When no MediaLive input is connected to the router output, the DownstreamMediaLiveInputID dimension displays as ``. ## Route metrics These metrics track the connection between a router input and a router output. MediaConnect publishes these metrics on the output side of the route. | Metric | Description | | --- | --- | | RouteBitRate | The bitrate of the content on the route between the router input and the router output. Units: bits per second (bps) Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: All | | RouteNotRecoveredPackets | The number of packets lost between the router input and the router output. Units: Count Valid dimensions: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-router-output-health.html) Protocols: All | **Note** When the router output is running but not connected to a router input, the RouterInputName, RouterInputID and RouterInputAvailabilityZone dimensions display as ``. # AWS Elemental MediaConnect metrics to monitor gateway health Metrics to monitor gateway healthMediaConnect Gateway metrics The user guide has been updated to include new CloudWatch metrics for the MediaConnect Gateway feature. AWS Elemental MediaConnect sends metrics to CloudWatch. You can review specific metrics to evaluate the health of your gateways. If the flow in or out of the gateway is unhealthy, these metrics can help you determine where the issue originates from. For details about each metric, see the tables in this section. **Note** MediaConnect Gateway metrics are not available in high resolution periods (one second). You must select a period of at least one minute. **Topics** + [ ## Gateway ingress metrics ](#monitor-with-cloudwatch-metrics-gateway-ingress) + [ ## Gateway ingress source metrics ](#monitor-with-cloudwatch-metrics-gateway-ingress-source) + [ ## Gateway egress metrics ](#monitor-with-cloudwatch-metrics-gateway-egress) + [ ## Gateway egress source metrics ](#monitor-with-cloudwatch-metrics-gateway-egress-source) ## Gateway ingress metrics The following table lists gateway ingress metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | IngressBridgeBitRate | The bitrate of the ingress bridge's source, after the failover merge. This source originates from your local datacenter. Units: bits per second (bps) Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeCATError | The number of times that a conditional access table (CAT) error occurred. This error indicates that the CAT is not present. The CAT tells the integrated receiver decoder (IRD) where to find management messages for the conditional access (CA) systems that are in use.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeCRCError | The number of times that a cyclic redundancy check (CRC) error occurred. This error happens when a CRC determines that data is corrupted.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeContinuityCounter | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeDroppedPackets | The number of packets that were lost during transit. This value is measured before any error correction takes place.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeFailoverSwitches | The total number of times the bridge switches back and forth between sources when using the Failover mode for source failover.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeMergeActive | The merge status of all sources on the bridge. A value of 1 indicates that all sources are merged. A value of 0 (zero) indicates that at least one source is not actively merged with 2022-7.Units: NoneValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePATError | The number of times that a program association table (PAT) error occurred. This error indicates that the PAT is missing. The PAT lists the programs that are available in a transport stream (TS) and points to the program map tables (PMTs). The decoder needs the PAT to do its job.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePCRAccuracyError | The number of times that a program clock register (PCR) accuracy error occurred. This error happens when the value of the transmitted PCR differs from what is expected by more than 500 nanoseconds (ns). When a stream is encoded, the encoder assigns periodic PCR values of the encoder's program clock. The decoder relies on these values to ensure that the stream is kept in sync.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePCRError | The number of times that a PCR error occurred. This error happens when PCR values are not sent frequently enough. The service relies on consistent, frequent PCRs to reset the local 27 MHz system clock. Although the error occurs when the interval exceeds 100 milliseconds (ms), best practices dictate that PCRs should be received at least every 40 ms.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePIDError | The number of times that a packet identifier (PID) error occurred. This error indicates that a PID is missing its associated data stream. The PIDs are identifiers that provide the location of the video, audio, and data streams. This error can occur after the transport stream has been multiplexed and then remultiplexed.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePMTError | The number of times that a program map table (PMT) error occurred. This error happens when the PMT is not received at least every 500 milliseconds (ms). Each PMT contains a list of PIDs, which help decoders reassemble data. The decoder needs the PMTs to do its job.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePTSError | The number of times that a presentation timestamp (PTS) error occurred. This error happens when a presentation timestamp (PTS) is not received at least every 700 ms. This can occur if the PTS is sent less frequently or not at all. The most common cause of this error is when the transport stream (TS) is scrambled.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgePacketLossPercent | The percentage of packets that were lost during transit, even if they were recovered.Units: PercentValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeRecoveredPackets | The number of packets that were lost during transit, but recovered.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeTSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeTSSyncLoss | The number of times that a transport stream sync loss error occurred. This error happens after two or more consecutive transport stream byte errors.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeTotalPackets | The total number of packets that were received.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeTransportError | The number of times that a primary transport error occurred. This error indicates that the transport stream packet is unusable. When this error occurs, ignore all other TR 101 290 errors for this packet.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | ## Gateway ingress source metrics The following table lists gateway ingress source metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | IngressBridgeSourceARQRecovered | The number of dropped packets that were recovered by automatic repeat request (ARQ). It doesn't apply to flows that receive content from an entitlement. Units: Count Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceARQRequests | The number of retransmitted packets that were requested through automatic repeat request (ARQ) and received. It doesn't apply to flows that receive content from an entitlement.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceBitRate | The bitrate of the ingress bridge's source, prior to any failover merge. This source originates from your local datacenter. Units: bits per second (bps) Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceCATError | The number of times that a conditional access table (CAT) error occurred. This error indicates that the CAT is not present. The CAT tells the integrated receiver decoder (IRD) where to find management messages for the conditional access (CA) systems that are in use.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceCRCError | The number of times that a cyclic redundancy check (CRC) error occurred. This error happens when a CRC determines that data is corrupted.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceContinuityCounter | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceDroppedPackets | The number of packets that were lost during transit. This value is measured before any error correction takes place.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceFECPackets | The number of packets that were transmitted using forward error correction (FEC) and received. It doesn't apply to flows that receive content from an entitlement.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceFECRecovered | The number of packets that were transmitted using forward error correction (FEC), lost during transit, and recovered. It doesn't apply to flows that receive content from an entitlement.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceMergeActive | An indication of the status of the source with respect to other sources. This metric is useful when the bridge has multiple sources for failover and you are using the Merge failover mode. A value of 1 indicates that the bridge has multiple sources and that this source is actively in use, with 2022-7 merge. A value of 0 (zero) indicates that the bridge is not using the source to form the stream.Units: NoneValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceMergeLatency | The amount of time that this source trails the primary source. If this source is the primary source, the value is 0 (zero).Units: MillisecondsValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceOverflowPackets | The number of packets that were lost in transit because the video required more buffer than was available. This metric doesn't apply to flows that receive content from an entitlement or to flows that have multiple sources.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePATError | The number of times that a program association table (PAT) error occurred. This error indicates that the PAT is missing. The PAT lists the programs that are available in a transport stream (TS) and points to the program map tables (PMTs). The decoder needs the PAT to do its job.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePCRAccuracyError | The number of times that a program clock register (PCR) accuracy error occurred. This error happens when the value of the transmitted PCR differs from what is expected by more than 500 nanoseconds (ns). When a stream is encoded, the encoder assigns periodic PCR values from the encoder's program clock. The decoder relies on these values to ensure that the stream is kept in sync.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePCRError | The number of times that a PCR error occurred. This error happens when PCR values are not sent frequently enough. The service relies on consistent, frequent PCRs to reset the local 27 MHz system clock. Although the error occurs when the interval exceeds 100 milliseconds (ms), best practices dictate that PCRs should be received at least every 40 ms.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePIDError | The number of times that a packet identifier (PID) error occurred. This error indicates that a PID is missing its associated data stream. The PIDs are identifiers that provide the location of the video, audio, and data streams. This error can occur after the transport stream has been multiplexed and then remultiplexed.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePMTError | The number of times that a program map table (PMT) error occurred. This error happens when the PMT is not received at least every 500 milliseconds (ms). Each PMT contains a list of PIDs, which help decoders reassemble data. The decoder needs the PMTs to do its job.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePTSError | The number of times that a presentation timestamp (PTS) error occurred. This error happens when a presentation timestamp (PTS) is not received at least every 700 ms. This can occur if the PTS is sent less frequently or not at all. The most common cause of this error is when the TS is scrambled.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourcePacketLossPercent | The percentage of packets that were lost during transit, even if they were recovered.Units: PercentValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceRecoveredPackets | The number of packets that were lost during transit, but recovered.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceRoundTripTime | The amount of time it takes for the source to send a signal and receive an acknowledgment from AWS Elemental MediaConnect. It doesn't apply to flows that receive content from an entitlement. Units: Milliseconds Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceTSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceTSSyncLoss | The number of times that a transport stream sync loss error occurred. This error happens after two or more consecutive transport stream byte errors.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceTotalPackets | The total number of packets that were received.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | IngressBridgeSourceTransportError | The number of times that a primary transport error occurred. This error indicates that the transport stream packet is unusable. When this error occurs, ignore all other TR 101 290 errors for this packet.Units: CountValid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | ## Gateway egress metrics The following table lists gateway egress metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | EgressBridgeBitRate | The bitrate of the egress bridge's source, after the failover merge. This source originates from a MediaConnect flow. Units: bits per second (bps) Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeCATError | The number of times that a conditional access table (CAT) error occurred. This error indicates that the CAT is not present. The CAT tells the integrated receiver decoder (IRD) where to find management messages for the conditional access (CA) systems that are in use.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeCRCError | The number of times that a cyclic redundancy check (CRC) error occurred. This error happens when a CRC determines that data is corrupted.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeContinuityCounter | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeDroppedPackets | The number of packets that were lost during transit. This value is measured before any error correction takes place.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeFailoverSwitches | The total number of times the bridge switches back and forth between sources when using the Failover mode for source failover.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeMergeActive | The merge status of all sources on the bridge. A value of 1 indicates that all sources are merged. A value of 0 (zero) indicates that at least one source is not actively merged with 2022-7.Units: NoneValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePATError | The number of times that a program association table (PAT) error occurred. This error indicates that the PAT is missing. The PAT lists the programs that are available in a transport stream (TS) and points to the program map tables (PMTs). The decoder needs the PAT to do its job.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePCRAccuracyError | The number of times that a program clock register (PCR) accuracy error occurred. This error happens when the value of the transmitted PCR differs from what is expected by more than 500 nanoseconds (ns). When a stream is encoded, the encoder assigns periodic PCR values of the encoder's program clock. The decoder relies on these values to ensure that the stream is kept in sync.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePCRError | The number of times that a PCR error occurred. This error happens when PCR values are not sent frequently enough. The service relies on consistent, frequent PCRs to reset the local 27 MHz system clock. Although the error occurs when the interval exceeds 100 milliseconds (ms), best practices dictate that PCRs should be received at least every 40 ms.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePIDError | The number of times that a packet identifier (PID) error occurred. This error indicates that a PID is missing its associated data stream. The PIDs are identifiers that provide the location of the video, audio, and data streams. This error can occur after the transport stream has been multiplexed and then remultiplexed.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePMTError | The number of times that a program map table (PMT) error occurred. This error happens when the PMT is not received at least every 500 milliseconds (ms). Each PMT contains a list of PIDs, which help decoders reassemble data. The decoder needs the PMTs to do its job.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePTSError | The number of times that a presentation timestamp (PTS) error occurred. This error happens when a presentation timestamp (PTS) is not received at least every 700 ms. This can occur if the PTS is sent less frequently or not at all. The most common cause of this error is when the transport stream (TS) is scrambled.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgePacketLossPercent | The percentage of packets that were lost during transit, even if they were recovered.Units: PercentValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeRecoveredPackets | The number of packets that were lost during transit, but recovered.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeTSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeTSSyncLoss | The number of times that a transport stream sync loss error occurred. This error happens after two or more consecutive transport stream byte errors.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeTotalPackets | The total number of packets that were received.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeTransportError | The number of times that a primary transport error occurred. This error indicates that the transport stream packet is unusable. When this error occurs, ignore all other TR 101 290 errors for this packet.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | ## Gateway egress source metrics The following table lists gateway egress source metrics that AWS Elemental MediaConnect sends to CloudWatch. | Metric | Description | | --- | --- | | EgressBridgeSourceBitRate | The bitrate of the egress bridge's source, prior to any failover merge. This source originates from a MediaConnect flow. Units: bits per second (bps) Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceCATError | The number of times that a conditional access table (CAT) error occurred. This error indicates that the CAT is not present. The CAT tells the integrated receiver decoder (IRD) where to find management messages for the conditional access (CA) systems that are in use.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceCRCError | The number of times that a cyclic redundancy check (CRC) error occurred. This error happens when a CRC determines that data is corrupted.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceContinuityCounter | The number of times that a continuity error occurred. This error indicates an incorrect packet order or lost packets.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceDroppedPackets | The number of packets that were lost during transit. This value is measured before any error correction takes place.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceMergeActive | An indication of the status of the source with respect to other sources. This metric is useful when the bridge has multiple sources for failover and you are using the Merge failover mode. A value of 1 indicates that the bridge has multiple sources and that this source is actively in use, with 2022-7 merge. A value of 0 (zero) indicates that the bridge is not using the source to form the stream.Units: NoneValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceMergeLatency | The amount of time that this source trails the primary source. If this source is the primary source, the value is 0 (zero).Units: MillisecondsValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceNotRecoveredPackets | The number of packets that were lost during transit and were not recovered by error correction.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePATError | The number of times that a program association table (PAT) error occurred. This error indicates that the PAT is missing. The PAT lists the programs that are available in a transport stream (TS) and points to the program map tables (PMTs). The decoder needs the PAT to do its job.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePCRAccuracyError | The number of times that a program clock register (PCR) accuracy error occurred. This error happens when the value of the transmitted PCR differs from what is expected by more than 500 nanoseconds (ns). When a stream is encoded, the encoder assigns periodic PCR values from the encoder's program clock. The decoder relies on these values to ensure that the stream is kept in sync.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePCRError | The number of times that a PCR error occurred. This error happens when PCR values are not sent frequently enough. The service relies on consistent, frequent PCRs to reset the local 27 MHz system clock. Although the error occurs when the interval exceeds 100 milliseconds (ms), best practices dictate that PCRs should be received at least every 40 ms.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePIDError | The number of times that a packet identifier (PID) error occurred. This error indicates that a PID is missing its associated data stream. The PIDs are identifiers that provide the location of the video, audio, and data streams. This error can occur after the transport stream has been multiplexed and then remultiplexed.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePMTError | The number of times that a program map table (PMT) error occurred. This error happens when the PMT is not received at least every 500 milliseconds (ms). Each PMT contains a list of PIDs, which help decoders reassemble data. The decoder needs the PMTs to do its job.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePTSError | The number of times that a presentation timestamp (PTS) error occurred. This error happens when a presentation timestamp (PTS) is not received at least every 700 ms. This can occur if the PTS is sent less frequently or not at all. The most common cause of this error is when the TS is scrambled.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourcePacketLossPercent | The percentage of packets that were lost during transit, even if they were recovered.Units: PercentValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceRecoveredPackets | The number of packets that were lost during transit, but recovered.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceTSByteError | The number of times that a transport stream byte error occurred. This error indicates that the sync byte did not appear after the prescribed number of bytes.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceTSSyncLoss | The number of times that a transport stream sync loss error occurred. This error happens after two or more consecutive transport stream byte errors. Units: Count Valid dimension sets: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceTotalPackets | The total number of packets that were received.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | | EgressBridgeSourceTransportError | The number of times that a primary transport error occurred. This error indicates that the transport stream packet is unusable. When this error occurs, ignore all other TR 101 290 errors for this packet.Units: CountValid dimension sets:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-with-cloudwatch-metrics-gateway-health.html) | # Using metrics to troubleshoot problems with your MediaConnect flow Using metrics to troubleshoot You can monitor the health of your stream by reviewing the metrics that AWS Elemental MediaConnect sends to CloudWatch. In particular, if you encounter a problem on your MediaConnect flow, these metrics can help you isolate the problem. The specific metrics to watch depend on the protocol that your source uses. Review the lists below, which are sorted by source protocol. **Topics** + [ ## Metrics to watch if your source uses the RIST protocol ](#monitor-with-cloudwatch-metrics-troubleshooting-rist) + [ ## Metrics to watch if your source uses the RTP protocol ](#monitor-with-cloudwatch-metrics-troubleshooting-rtp) + [ ## Metrics to watch if your source uses the RTP-FEC protocol ](#monitor-with-cloudwatch-metrics-troubleshooting-rtp-fec) + [ ## Metrics to watch if your source uses the SRT protocol ](#monitor-with-cloudwatch-metrics-troubleshooting-SRT) + [ ## Metrics to watch if your source uses the Zixi push protocol ](#monitor-with-cloudwatch-metrics-troubleshooting-zixi-push) + [ ## Metrics to watch if your source comes from an entitlement ](#monitor-with-cloudwatch-metrics-troubleshooting-entitlement) + [ ## Metrics to watch if you are using gateways ](#monitor-with-cloudwatch-metrics-troubleshooting-gateway) ## Metrics to watch if your source uses the RIST protocol If the protocol of your source is RIST, watch the metrics below to evaluate the health of your source. + `ARQRecovered` + `ARQRequests` + `DroppedPackets` + `NotRecoveredPackets` + `OverflowPackets` + `PacketLossPercent` + `RecoveredPackets` + `RoundTripTime` + `TotalPackets` ## Metrics to watch if your source uses the RTP protocol If the protocol of your source is RTP, watch the metrics below to evaluate the health of your source. + `DroppedPackets` + `OverflowPackets` + `RoundTripTime` + `TotalPackets` ## Metrics to watch if your source uses the RTP-FEC protocol If the protocol of your source is RTP-FEC, watch the metrics below to evaluate the health of your source. + `DroppedPackets` + `FECPackets` + `FECRecovered` + `NotRecoveredPackets` + `OverflowPackets` + `RecoveredPackets` + `RoundTripTime` + `TotalPackets` ## Metrics to watch if your source uses the SRT protocol If the protocol of your source is SRT (listener or caller), watch the metrics below to evaluate the health of your source. + `ARQRecovered` + `ARQRequests` + `DroppedPackets` + `NotRecoveredPackets` + `OverflowPackets` + `RecoveredPackets` + `RoundTripTime` + `TotalPackets` ## Metrics to watch if your source uses the Zixi push protocol If the protocol of your source is Zixi push, watch the metrics below to evaluate the health of your source. + `ARQRecovered` + `ARQRequests` + `DroppedPackets` + `FECPackets` + `FECRecovered` + `NotRecoveredPackets` + `OverflowPackets` + `RecoveredPackets` + `RoundTripTime` + `TotalPackets` ## Metrics to watch if your source comes from an entitlement If your source comes from an entitlement that was granted to your account by another AWS account, watch the metrics below to evaluate the health of your source. + `ARQRecovered` + `ARQRequests` + `DroppedPackets` + `FECPackets` + `FECRecovered` + `NotRecoveredPackets` + `OverflowPackets` + `RecoveredPackets` + `RoundTripTime` + `TotalPackets` ## Metrics to watch if you are using gateways Watch the metrics below to evaluate the health of your gateway. ### Metrics to watch if you are using a gateway with an ingress bridge Watch the metrics below to evaluate the health of your gateway's ingress bridge. The recommended ingress bridge troubleshooting metrics are separated by protocol. + RTP + `IngressBridgeTotalPackets` + `IngressBridgeDroppedPackets` + `IngressBridgeSourceTotalPackets` + `IngressBridgeSourceDroppedPackets` + `IngressBridgeSourceOverflowPackets` + `IngressBridgeSourceRoundTripTime` + RTP-FEC + `IngressBridgeTotalPackets` + `IngressBridgeDroppedPackets` + `IngressBridgeRecoveredPackets` + `IngressBridgeNotRecoveredPackets` + `IngressBridgeSourceTotalPackets` + `IngressBridgeSourceDroppedPackets` + `IngressBridgeSourceRecoveredPackets` + `IngressBridgeSourceNotRecoveredPackets` + `IngressBridgeSourceOverflowPackets` + `IngressBridgeSourceFECPackets` + `IngressBridgeSourceFECRecovered` + `IngressBridgeSourceRoundTripTime` + UDP + `IngressBridgeTotalPackets` + `IngressBridgeSourceTotalPackets` + `IngressBridgeSourceOverflowPackets` ### Metrics to watch if you are using a gateway with an egress bridge Watch the metrics below to evaluate the health of your gateway's egress bridge. + `EgressBridgeTotalPackets` + `EgressBridgeDroppedPackets` + `EgressBridgeRecoveredPackets` + `EgressBridgeNotRecoveredPackets` + `EgressBridgeSourceTotalPackets` + `EgressBridgeSourceDroppedPackets` + `EgressBridgeSourceRecoveredPackets` + `EgressBridgeSourceNotRecoveredPackets` # Monitoring with Amazon EventBridge events Monitoring with EventBridge eventsHealth EventBridge events New flow, source, and output health monitoring EventBridge events have been added to MediaConnect. EventBridge enables you to automate your AWS services and respond automatically to system events such as application availability issues or resource changes. Events from AWS services are delivered to EventBridge in near real time. You can write simple rules to indicate which events are of interest to you, and what automated actions to take when an event matches a rule. The actions that can be automatically triggered using EventBridge include the following: + Invoking an AWS Lambda function + Invoking Amazon EC2 Run Command + Relaying the event to Amazon Kinesis Data Streams + Activating an AWS Step Functions state machine + Notifying an Amazon SNS topic or an Amazon SQS queue For more information, see the [Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). **Topics** + [ # MediaConnect flow state change event ](monitoring-cloudwatch-events-flow-state-change.md) + [ # MediaConnect flow maintenance event ](monitoring-cloudwatch-events-flow-maintenance.md) + [ # MediaConnect flow health event ](monitoring-cloudwatch-events-flow-health.md) + [ # MediaConnect alert event ](monitoring-cloudwatch-events-alert.md) + [ # MediaConnect source health event ](monitoring-cloudwatch-events-source-health.md) + [ # MediaConnect output health event ](monitoring-cloudwatch-events-output-health.md) + [ # MediaConnect flow content quality event ](monitoring-eventbridge-events-content-quality.md) # MediaConnect flow state change event Flow state change event This event is published when a flow's state has changed from or to any of the following states: Standby, Active, Updating, Deleting, Starting, Stopping, or Error. For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). The following message is an example of this event. ``` { "account": "111122223333", "detail": { "currentStatus": "STARTING", "previousStatus": "STANDBY" }, "detail-type": "MediaConnect Flow Status Change", "id": "01234567-0123-0123-0123-0123456789ab", "region": "us-east-1", "resources": ["arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:AwardsShow"], "source": "aws.mediaconnect", "time": "2022-01-06T00:45:47Z", "version": "0" } ``` # MediaConnect flow maintenance event Flow maintenance eventMaintenance EventBridge event The user guide has been updated to include a new EventBridge event for MediaConnect maintenance. This event is published when a flow's maintenance status has changed, either to or from any of the following states: + **SCHEDULED** - Maintenance is scheduled for the flow. + **RESCHEDULED** - MediaConnect is unable to perform maintenance at the previously scheduled date and time. A new date and time has been automatically assigned by MediaConnect for this flow's maintenance. + **CANCELED** - Maintenance for this flow is cancelled by MediaConnect. + **INPROGRESS** - Maintenance has started and is currently in progress for this flow. + **FINISHED** - Maintenance completed successfully for this flow. + **FAILED** - Maintenance did not complete successfully for this flow. For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). For information about MediaConnect maintenance, see [MediaConnect flow maintenance](https://docs.aws.amazon.com/mediaconnect/latest/ug/maintenance.html). The following message is an example of this EventBridge event. ``` { "version": "0", "id": "01234567-0123-0123-0123-0123456789ab", "detail-type": "MediaConnect Flow Maintenance", "source": "aws.mediaconnect", "account": "111122223333", "time": "2022-02-14T00:45:47Z", "region": "us-east-1", "resources": [ "arn:aws:mediaconnect:us-east-1:111122223333:flow:1-23aBC45dEF67hiJ8-12AbC34DE5fG:ExampleFlow" ], "detail": { "currentStatus": "FINISHED" } } ``` # MediaConnect flow health event Flow health event AWS Elemental MediaConnect publishes flow health events after a flow health indicator state changes. MediaConnect publishes this event any time there is a state change to one or more of the following flow health indicators. This event publishes the current and previous state of the flow. The following are flow health indicators: + **Source state** + Possible states: `connected`, `receiving`, `disconnected`, `idle` + **Failover switch** + Possible states: `true`, `false` + **TR-101**: TR-101 is an industry standard technical recommendation for the monitoring of transport streams (TS). The following events are only published for TS based protocols. + **TS sync loss** is `true` when source payloads do not look like a valid transport stream. + **Continuity count error** is `true` when the source finds continuity count errors. + **Transport error** is `true` when the TS has the transport indicator set. + **PCR error** is `true` when there is a PCR discontinuity or a long gap in PCR packet reception. For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). The following message is an example of this event. ``` { "version": "0", "id": "01234567-0123-0123-0123-0123456789ab", "detail-type": "MediaConnect Flow Health", "source": "aws.mediaconnect", "account": "012345678901", "time": "2006-01-02T15:04:05Z", "region": "us-east-1", "resources": [ "arn:aws:mediaconnect:us-east-1:012345678901:flow:1-AbCdEfGhIjKlMnOp-abcdef123455:ExampleFlow" ], "detail": { "unhealthy": true, "current": { "failover_switch": false, "source_state": "CONNECTED", "tr101": { "ts_sync_loss": false, "continuity_count_error": true, "transport_error": true, "pcr_error": true } }, "previous": { "failover_switch": false, "source_state": "CONNECTED", "tr101": { "ts_sync_loss": false, "continuity_count_error": false, "transport_error": false, "pcr_error": false } } } } ``` # MediaConnect alert event Alert event MediaConnect publishes an alert event when a resource encounters an error. The event contains an error code and a message that describes the issue. These alerts are visible on the MediaConnect console, or by using the `describe-flow` AWS Command Line Interface (AWS CLI) command. For more information about the `describe-flow` command, see [AWS CLI Command Reference](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/mediaconnect/describe-flow.html). For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). The following message is an example of this event. ``` { "version": "0", "id": "01234567-0123-0123-0123-0123456789ab", "detail-type": "MediaConnect Alert", "source": "aws.mediaconnect", "account": "111122223333", "time": "2022-01-06T00:45:47Z", "region": "us-east-1", "resources": [ "arn:aws:mediaconnect:us-east-1:111122223333:flow:1-AbCdEfGhIjKlMnOp-abcdef123455:ExampleFlow" ], "detail": { "errored": true, "error-code": "AccessDeniedException", "error-message": "Permission denied accessing encryption key for output Test. Removing output until it is fixed (secret arn:aws:secretsmanager:us-east-1:111122223333:secret:ExampleSecret, role arn:aws:iam::111122223333:role/ExampleKey)" } } ``` # MediaConnect source health event Source health event AWS Elemental MediaConnect publishes source health events after a source health indicator state changes. MediaConnect publishes this event any time there is a state change to one or more of the following source health indicators. This event publishes the current and previous state of the flow. Note that the source health event lists the affected flow and source in the `resources` section. The following are source health indicators: + **Source state** + Possible states: `connected`, `receiving`, `disconnected`, `idle` + **TR-101**: TR-101 is an industry standard technical recommendation for the monitoring of transport streams (TS). The following events are only published for TS based protocols. + **TS sync loss** - true when source payloads do not look like a valid transport stream. + **Continuity count error** - true when the source finds continuity count errors. + **Transport error** - true when the TS has the transport indicator set. + **PCR error** - true when there is a PCR discontinuity or a long gap in PCR packet reception. For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). The following message is an example of this event. ``` { "version": "0", "id": "01234567-0123-0123-0123-0123456789ab", "detail-type": "MediaConnect Source Health", "source": "aws.mediaconnect", "account": "012345678901", "time": "2006-01-02T15:04:05Z", "region": "us-east-1", "resources": [ "arn:aws:mediaconnect:us-east-1:012345678901:flow:1-AbCdEfGhIjKlMnOp-abcdef123455:ExampleFlow", "arn:aws:mediaconnect:us-east-1:012345678901:source:1-AbCdEfGhIjKlMnOp-abcdef123455:ExampleSource" ], "detail": { "unhealthy": true, "current": { "state": "CONNECTED", "tr101": { "ts_sync_loss": false, "continuity_count_error": true, "transport_error": true, "pcr_error": true } }, "previous": { "state": "CONNECTED", "tr101": { "ts_sync_loss": false, "continuity_count_error": false, "transport_error": false, "pcr_error": false } } } } ``` # MediaConnect output health event Output health event AWS Elemental MediaConnect publishes output health events after an output health indicator state changes. MediaConnect publishes this event any time there is a state change to one or more of the following output health indicators. This event publishes the current and previous state of the flow. Note that the output health event lists the affected flow and output in the `resources` section. The following are output health indicators: + **Output state** + Possible states: `connected`, `sending`, `disconnected`, `idle` For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). The following message is an example of this event. ``` { "version": "0", "id": "01234567-0123-0123-0123-0123456789ab", "detail-type": "MediaConnect Output Health", "source": "aws.mediaconnect", "account": "012345678901", "time": "2006-01-02T15:04:05Z", "region": "us-east-1", "resources": [ "arn:aws:mediaconnect:us-east-1:012345678901:flow:1-AbCdEfGhIjKlMnOp-abcdef123455:ExampleFlow", "arn:aws:mediaconnect:us-east-1:012345678901:output:1-AbCdEfGhIjKlMnOp-abcdef123455:ExampleOutput" ], "detail": { "current": { "state": "CONNECTED" }, "previous": { "state": "DISCONNECTED" } } } ``` # MediaConnect flow content quality event Content quality eventContent quality EventBridge events A new content quality monitoring EventBridge event has been added to MediaConnect. AWS Elemental MediaConnect publishes the following event when an issue is detected with content quality: `MediaConnect Flow Content Quality` MediaConnect publishes this event in three scenarios: 1. When the duration threshold is breached for one of the following metrics: + **Black frames**: Periods of black video frames are detected in the stream. + **Frozen frames**: Periods of unchanging video frames are detected in the stream. + **Silent audio**: Periods of audio silence are detected in the stream. 1. When audio or video content is missing from the stream. This happens when monitoring is configured for audio or video streams, but MediaConnect can’t detect the expected data to monitor. 1. When a previously reported issue has been resolved (clearing state). MediaConnect publishes these events whenever the state of any monitored condition changes. This includes when issues are first detected, when they clear, or any combination of these changes. For example, a single event might show some issues that are clearing while others are being detected, depending on what changed during that reporting period. In the event JSON, you'll see the following fields to indicate these issues: **For duration threshold breaches:** + `black_frames_duration_breaching`: true when black frames exceed the threshold + `frozen_frames_duration_breaching`: true when frozen frames exceed the threshold + `silent_audio_duration_breaching`: true when silent audio exceeds the threshold **For missing audio/video:** + `audio_missing`: true when audio content is missing + `video_missing`: true when video content is missing These alerts are visible on the MediaConnect console, or by using the `describe-flow` AWS Command Line Interface (AWS CLI) command. For more information about the `describe-flow` command, see the [AWS CLI Command Reference](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/mediaconnect/describe-flow.html). For information about subscribing to this event, see [Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). The following message is an example of the `MediaConnect Flow Content Quality` event. In this example, the event indicates both missing audio content and a frozen frames duration threshold breach in the stream. ``` { "impacted": true, "streams": [ { "audio_missing": true, }, } "frozen_frames_duration_breaching": true, } ] } ``` # Logging AWS Elemental MediaConnect API calls with AWS CloudTrail Logging API calls with AWS CloudTrail AWS Elemental MediaConnect is integrated with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in AWS Elemental MediaConnect. CloudTrail captures all API calls for AWS Elemental MediaConnect as events. The calls captured include calls from the AWS Elemental MediaConnect console and code calls to the AWS Elemental MediaConnect API operations. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for AWS Elemental MediaConnect. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in **Event history**. Using the information collected by CloudTrail, you can determine the request that was made to AWS Elemental MediaConnect, the IP address from which the request was made, who made the request, when it was made, and additional details. To learn more about CloudTrail, see the [AWS CloudTrail User Guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/). ## AWS Elemental MediaConnect information in CloudTrail CloudTrail is enabled on your AWS account when you create the account. When activity occurs in AWS Elemental MediaConnect, that activity is recorded in a CloudTrail event along with other AWS service events in **Event history**. You can view, search, and download recent events in your AWS account. For more information, see [Viewing Events with CloudTrail Event History](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html). For an ongoing record of events in your AWS account, including events for AWS Elemental MediaConnect, create a trail. A *trail* enables CloudTrail to deliver log files to an Amazon S3 bucket. By default, when you create a trail in the console, the trail applies to all AWS Regions. The trail logs events from all Regions in the AWS partition and delivers the log files to the Amazon S3 bucket that you specify. Additionally, you can configure other AWS services to further analyze and act upon the event data collected in CloudTrail logs. For more information, see the following: + [Overview for Creating a Trail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-create-and-update-a-trail.html) + [CloudTrail Supported Services and Integrations](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-aws-service-specific-topics.html#cloudtrail-aws-service-specific-topics-integrations) + [Configuring Amazon SNS Notifications for CloudTrail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/getting_notifications_top_level.html) + [Receiving CloudTrail Log Files from Multiple Regions](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html) and [Receiving CloudTrail Log Files from Multiple Accounts](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-receive-logs-from-multiple-accounts.html) All AWS Elemental MediaConnect actions are logged by CloudTrail and are documented in the [AWS Elemental MediaConnect API Reference](https://docs.aws.amazon.com/mediaconnect/latest/api/resources.html). For example, calls to the `CreateFlow`, `StartFlow` and `UpdateFlowOutput` operations generate entries in the CloudTrail log files. Every event or log entry contains information about who generated the request. The identity information helps you determine the following: + Whether the request was made with root or AWS Identity and Access Management (IAM) user credentials. + Whether the request was made with temporary security credentials for a role or federated user. + Whether the request was made by another AWS service. For more information, see the [CloudTrail userIdentity Element](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-user-identity.html). ## Understanding AWS Elemental MediaConnect log file entries A trail is a configuration that enables delivery of events as log files to an Amazon S3 bucket that you specify. CloudTrail log files contain one or more log entries. An event represents a single request from any source and includes information about the requested operation, the date and time of the operation, request parameters, and so on. CloudTrail log files aren't an ordered stack trace of the public API calls, so they don't appear in any specific order. The following example shows a CloudTrail log entry that demonstrates the `DescribeFlow` operation: ``` { "eventVersion": "1.05", "userIdentity": { "type": "IAMUser", "principalId": "ABCDEFGHIJKL123456789", "arn": "arn:aws:sts::111122223333:user/testUser", "accountId": "111122223333", "accessKeyId": "ABCDE12345EFGHIJKLMN", "sessionContext": { "attributes": { "mfaAuthenticated": "false", "creationDate": "2018-11-16T20:34:51Z", }, "sessionIssuer": { "type": "Role", "principalId": "ABCDEFGHIJKL123456789", "arn": "arn:aws:iam::111122223333:role/Administrator", "accountId": "111122223333", "userName": "Administrator", }, }, }, "eventTime": "2018-11-16T20:34:52Z", "eventSource": "mediaconnect.amazonaws.com", "eventName": "DescribeFlow", "awsRegion": "us-west-2", "sourceIPAddress": "203.0.113.17", "userAgent": "aws-cli/1.15.40 Python/3.6.5 Darwin/16.7.0 botocore/1.10.40", "requestParameters": { "flowArn": "arn%3Aaws%3Amediaconnect%3Aus-west-2%111122223333%3Aflow%3A1-23aBC45dEF67hiJ8-12AbC34DE5fG%3AAwardsShow", }, "responseElements": { }, "requestID": "1a2b3c4d-1234-5678-1234-1a2b3c4d5e6f", "eventID": "987abc65-1a2b-3c4d-5d6e-987abc654def", "readOnly": true, "eventType": "AwsApiCall", "recipientAccountId": "111122223333", } ``` # Tagging AWS Elemental MediaConnect resources Tagging resources A *tag* is a custom attribute label that you assign or that AWS assigns to an AWS resource. Each tag has two parts: + A *tag key* (for example, `CostCenter`, `Environment`, or `Project`). Tag keys are case sensitive. + An optional field known as a *tag value* (for example, `111122223333` or `Production`). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case sensitive. Tags help you do the following: + Identify and organize your AWS resources. Many AWS services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you could assign the same tag to an AWS Elemental MediaConnect flow that you assign to an AWS Elemental MediaLive channel output. + Track your AWS costs. You activate these tags on the AWS Billing and Cost Management dashboard. AWS uses the tags to categorize your costs and deliver a monthly cost allocation report to you. For more information, see [Use Cost Allocation Tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html) in the *AWS Billing User Guide*. The following sections provide more information about tags for AWS Elemental MediaConnect. **Topics** + [ # AWS Elemental MediaConnect resources that support tagging ](supported-resources.md) + [ # Tag naming and usage conventions ](tagging-restrictions.md) + [ # Managing tags ](tagging-add-edit-delete.md) # AWS Elemental MediaConnect resources that support tagging Supported resources The following resources in AWS Elemental MediaConnect support tagging: + Flows + Sources + Outputs + Entitlements For information about adding and managing tags, see [Managing tags](tagging-add-edit-delete.md). AWS Elemental MediaConnect doesn't support the tag-based access control feature of AWS Identity and Access Management (IAM). # Tag naming and usage conventions Tag naming and usage conventions The following basic naming and usage conventions apply to using tags with AWS Elemental MediaConnect resources: + Each resource can have a maximum of 50 tags. + For each resource, each tag key must be unique, and each tag key can have only one value. + The maximum tag key length is 128 Unicode characters in UTF-8. + The maximum tag value length is 256 Unicode characters in UTF-8. + Allowed characters are letters, numbers, spaces representable in UTF-8, and the following characters:*** . : \$1 = @ \$1 / -*** (hyphen). Amazon EC2 resources allow any characters. + Tag keys and values are case sensitive. As a best practice, decide on a strategy for capitalizing tags, and consistently implement that strategy across all resource types. For example, decide whether to use `Costcenter`, `costcenter`, or `CostCenter`, and use the same convention for all tags. Avoid using similar tags with inconsistent case treatment. + The `aws:` prefix is prohibited for tags; it's reserved for AWS use. You can't edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource quota. # Managing tags Managing tags Tags are made up of the `Key` and `Value` properties on a resource. You can use the AWS Elemental MediaConnect console, the AWS CLI, or the AWS Elemental MediaConnect API to add, edit, or delete the values for these properties. For information about working with tags, see the following: + [Resources](https://docs.aws.amazon.com/mediaconnect/latest/api/resources.html) in the *AWS Elemental MediaConnect API Reference* + [Managing tags on a flow](flows-manage-tags.md) in this guide + [Managing tags on a MediaConnect source](sources-manage-tags.md) in this guide + [Managing tags on a MediaConnect output](outputs-manage-tags.md) in this guide + [Managing tags on an entitlement](entitlements-manage-tags.md) in this guide # Monitoring AWS media services with workflow monitor Workflow monitorWorkflow monitor Analyze AWS media services and create signal maps, visualizations of the media workflow, between those services. Use the signal maps to generate monitoring alarms and notifications using CloudWatch, EventBridge, and CloudFormation. Workflow monitor is a tool for the discovery, visualization, and monitoring of AWS media workflows. Workflow monitor is available in the AWS console and API. You can use workflow monitor to discover and create visual mappings of your workflow's resources, called *signal maps*. You can create and manage Amazon CloudWatch alarm and Amazon EventBridge rule templates to monitor the mapped resources. The monitoring templates you create are transformed into deployable AWS CloudFormation templates to allow repeatability. AWS recommended alarm templates provide predefined best-practice monitoring. **Discover** Utilize signal maps to automatically discover interconnected AWS resources associated with your media workflow. Discovery can begin at any supported service resource and creates an end-to-end mapping of the workflow. Signal maps can be used as stand-alone visualization tools or enhanced with monitoring templates. ![\[Workflow monitor discovery components.\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/images/workflowmonitor-discovery.png) **Monitor** You can create custom CloudWatch alarm and EventBridge rule templates to monitor the health and status of your media workflows. Best practice alarm templates are available to import into your workflow monitor environment. You can use the best practice alarm templates as they are, or edit them to better fit your workflow. Any templates you create are transformed into CloudFormation templates for repeatable deployment. ![\[Workflow monitor monitoring components.\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/images/workflowmonitor-monitoring.png) **Note** There is no direct cost for using workflow monitor. However, there are costs associated with the resources created and used to monitor your workflow. When monitoring is deployed, Amazon CloudWatch and Amazon EventBridge resources are created. When using the AWS Management Console, prior to deploying monitoring to a signal map, you will be notified of how many resources will be created. For more information about pricing, see: [CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/) and [EventBridge pricing](https://aws.amazon.com/eventbridge/pricing/). Workflow monitor uses AWS CloudFormation templates to deploy the CloudWatch and EventBridge resources. These templates are stored in a standard class Amazon Simple Storage Service bucket that is created on your behalf, by workflow monitor, during the deployment process and will incur object storage and recall charges. For more information about pricing, see: [Amazon S3 pricing](https://aws.amazon.com/s3/pricing/). Previews generated in the workflow monitor signal map for AWS Elemental MediaPackage channels are delivered from the MediaPackage Origin Endpoint and will incur Data Transfer Out charges. For pricing, see: [MediaPackage pricing](https://aws.amazon.com/mediapackage/pricing/). ## Components of workflow monitor Workflow monitor has four major components: + CloudWatch alarm templates - Define the conditions you would like to monitor using CloudWatch. You can create your own alarm templates, or import predefined templates created by AWS. For more information, see: [CloudWatch alarm groups and templates for monitoring your AWS media workflow](monitor-with-workflow-monitor-configure-alarms.md) + EventBridge rule templates - Define how EventBridge sends notifications when an alarm is triggered. For more information, see: [EventBridge rule groups and templates for monitoring your AWS media workflow](monitor-with-workflow-monitor-configure-notifications.md) + Signal maps - Use an automated process to create AWS Elemental workflow maps using existing AWS resources. The signal maps can be used to discover resources in your workflow and deploy monitoring to those resources. For more information, see: [Workflow monitor signal maps](monitor-with-workflow-monitor-configure-signal-maps.md) + Overview - The overview page allows you to directly monitor the status of multiple signal maps from one location. Review metrics, logs, and alarms for your workflows. For more information, see: [Workflow monitor overview](monitor-with-workflow-monitor-operate-overview.md) ## Supported services Workflow monitor supports automatic discovery and signal mapping of resources associated with the following services: + AWS Elemental MediaConnect + AWS Elemental MediaLive + AWS Elemental MediaPackage + AWS Elemental MediaTailor + Amazon S3 + Amazon CloudFront **Topics** + [ ## Components of workflow monitor ](#monitor-with-workflow-monitor-components) + [ ## Supported services ](#monitor-with-workflow-monitor-supported-services) + [ # Configuring workflow monitor to monitor AWS media services ](monitor-with-workflow-monitor-configure.md) + [ # Using workflow monitor ](monitor-with-workflow-monitor-operate.md) # Configuring workflow monitor to monitor AWS media services Configuring workflow monitor To setup workflow monitor for the first time; you create the alarm and event templates, and discover signal maps that are used to monitor your media workflows. The following guide contains the steps necessary to setup both Administrator and Operator level IAM roles, create workflow monitor resources, and deploy monitoring to your workflows. **Topics** + [ # Getting started with workflow monitor ](monitor-with-workflow-monitor-configure-getting-started.md) + [ # Workflow monitor groups and templates ](monitor-with-workflow-monitor-configure-templates.md) + [ # Workflow monitor signal maps ](monitor-with-workflow-monitor-configure-signal-maps.md) + [ # Workflow monitor quotas ](monitor-with-workflow-monitor-configure-quotas.md) # Getting started with workflow monitor Getting started The following steps provide a basic overview of using workflow monitor for the first time. 1. Setup workflow monitor IAM permissions for administrator and operator level roles: [Workflow monitor IAM policies](monitor-with-workflow-monitor-configure-getting-started-IAM.md) 1. Build alarm templates or import predefined templates created by AWS: [CloudWatch alarms](monitor-with-workflow-monitor-configure-alarms.md) 1. Build notification events that will be delivered by EventBridge: [EventBridge rules ](monitor-with-workflow-monitor-configure-notifications.md) 1. Discover signal maps using your existing AWS Elemental resources: [Signal maps ](monitor-with-workflow-monitor-configure-signal-maps.md) 1. Attach the alarm templates and notification rules to your signal map: [Attaching templates](monitor-with-workflow-monitor-configure-signal-maps-attach.md) 1. Deploy the templates to begin monitoring the signal map: [Deploying monitoring templates](monitor-with-workflow-monitor-configure-deploy.md) 1. Monitor and review your workflow monitor resources using the overview section of the AWS console: [Overview](monitor-with-workflow-monitor-operate-overview.md) ![\[The individual steps of setting up workflow monitor. Begin by creating the IAM roles. Next, create templates for alarms and events. Next, discover a signal map and attach your templates to the map. After a signal map has templates attached, the templates must be deployed. The final step is monitoring using the templates and overview resources.\]](http://docs.aws.amazon.com/mediaconnect/latest/ug/images/workflowmonitor-overview-steps.png) # Workflow monitor IAM policies Workflow monitor IAM policies Workflow monitor interacts with multiple AWS services to create signal maps, build CloudWatch and EventBridge resources, and CloudFormation templates. Because workflow monitor interacts with a wide range of services, specific AWS Identity and Access Management (IAM) policies must be assigned for these services. The following examples indicate the necessary IAM policies for both administrator and operator IAM roles. ## Administrator IAM policy The following example policy is for an administrator-level workflow monitor IAM policy. This role allows for the creation and management of workflow monitor resources and the supported service resources that interact with workflow monitor. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "cloudwatch:List*", "cloudwatch:Describe*", "cloudwatch:Get*", "cloudwatch:PutAnomalyDetector", "cloudwatch:PutMetricData", "cloudwatch:PutMetricAlarm", "cloudwatch:PutCompositeAlarm", "cloudwatch:PutDashboard", "cloudwatch:DeleteAlarms", "cloudwatch:DeleteAnomalyDetector", "cloudwatch:DeleteDashboards", "cloudwatch:TagResource", "cloudwatch:UntagResource" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "cloudformation:List*", "cloudformation:Describe*", "cloudformation:CreateStack", "cloudformation:UpdateStack", "cloudformation:DeleteStack", "cloudformation:TagResource", "cloudformation:UntagResource" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "cloudfront:List*", "cloudfront:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "ec2:DescribeNetworkInterfaces" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "events:List*", "events:Describe*", "events:CreateEventBus", "events:PutRule", "events:PutTargets", "events:EnableRule", "events:DisableRule", "events:DeleteRule", "events:RemoveTargets", "events:TagResource", "events:UntagResource" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "logs:Describe*", "logs:Get*", "logs:TagLogGroup", "logs:TagResource", "logs:UntagLogGroup", "logs:UntagResource" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediaconnect:List*", "mediaconnect:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "medialive:*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediapackage:List*", "mediapackage:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediapackagev2:List*", "mediapackagev2:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediapackage-vod:List*", "mediapackage-vod:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediatailor:List*", "mediatailor:Describe*", "mediatailor:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "resource-groups:ListGroups", "resource-groups:GetGroup", "resource-groups:GetTags", "resource-groups:GetGroupQuery", "resource-groups:GetGroupConfiguration", "resource-groups:CreateGroup", "resource-groups:UngroupResources", "resource-groups:GroupResources", "resource-groups:DeleteGroup", "resource-groups:UpdateGroupQuery", "resource-groups:UpdateGroup", "resource-groups:Tag", "resource-groups:Untag" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "s3:*" ], "Resource": "arn:aws:s3:::workflow-monitor-templates*" }, { "Effect": "Allow", "Action": [ "sns:TagResource", "sns:UntagResource" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "tag:Get*", "tag:Describe*", "tag:TagResources", "tag:UntagResources" ], "Resource": "*" } ] } ``` ------ ## Operator IAM policy The following example policy is for an operator-level workflow monitor IAM policy. This role allows for limited and read-only access to the workflow monitor resources and the supported service resources that interact with workflow monitor. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "cloudwatch:List*", "cloudwatch:Describe*", "cloudwatch:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "cloudformation:List*", "cloudformation:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "cloudfront:List*", "cloudfront:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "ec2:DescribeNetworkInterfaces" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "events:List*", "events:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "logs:Describe*", "logs:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediaconnect:List*", "mediaconnect:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "medialive:List*", "medialive:Get*", "medialive:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediapackage:List*", "mediapackage:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediapackagev2:List*", "mediapackagev2:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediapackage-vod:List*", "mediapackage-vod:Describe*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "mediatailor:List*", "mediatailor:Describe*", "mediatailor:Get*" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "s3:Get*", "s3:List*" ], "Resource": "arn:aws:s3:::workflow-monitor-templates*" }, { "Effect": "Allow", "Action": [ "tag:Get*", "tag:Describe*" ], "Resource": "*" } ] } ``` ------ # Workflow monitor groups and templates Templates Before you can deploy workflow monitoring to a signal map, you must create the groups and templates for CloudWatch alarms and EventBridge notifications. The CloudWatch templates define what scenarios and thresholds will be used to trigger the alarms. The EventBridge templates will determine how these alarms are reported to you. If you only want mappings of your connected resources and do not want to use the monitoring template capabilities of workflow monitor, signal maps can be used without CloudWatch and EventBridge templates. For more information about using signal maps, see: [Signal maps ](monitor-with-workflow-monitor-configure-signal-maps.md) **Topics** + [ # CloudWatch alarm groups and templates for monitoring your AWS media workflow ](monitor-with-workflow-monitor-configure-alarms.md) + [ # EventBridge rule groups and templates for monitoring your AWS media workflow ](monitor-with-workflow-monitor-configure-notifications.md) # CloudWatch alarm groups and templates for monitoring your AWS media workflow CloudWatch alarms Workflow monitor alarms allow you to use existing CloudWatch metrics as the foundation of alarms for your signal maps. You can create an alarm template group to sort and classify the types of alarming that is important to your workflow. Within each alarm template group, you create alarm templates with specific CloudWatch metrics and parameters that you want to monitor. You can create your own alarm templates or import recommended alarm templates created by AWS. After creating an alarm template group and alarm templates within that group, you can attach one or more of these alarm template groups to a signal map. You must create an alarm template group first. After you have created an alarm template group, you can create your own templates or use recommended templates created by AWS. If you want to create your own alarm templates, continue on this page. For more information about importing recommended templates, see: [Recommended templates](monitor-with-workflow-monitor-configure-alarms-recommended-templates.md) This section covers the creation of CloudWatch alarms using workflow monitor. For more information about how the CloudWatch service handles alarms and details of the alarm components, see: [Using CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) in the *Amazon CloudWatch User Guide* ## Creating alarm template groups Alarm template groups allow you to sort and classify the types of alarms that are important to your workflow. **To create an alarm template group** 1. From the workflow monitor console's navigation pane, select **CloudWatch alarm templates**. 1. Select **Create alarm template group**. 1. Give the alarm template group a unique **Group name** and optional **Description**. 1. Select **Create**, You will be taken to the newly created alarm template group's details page. ## Creating alarm templates You can create alarm templates with the CloudWatch metrics and parameters that you want to monitor. **To create an alarm template** 1. From the alarm template group's details page, select **Create alarm template**. 1. Give the alarm template a unique **Template name** and optional **Description**. 1. In the **Choose metric** section: 1. Select a **Target Resource Type**. The target resource type is a resource for the respective service, such as a channel for MediaLive and MediaPackage or a flow for MediaConnect. 1. Select a **Metric Name**. This is the CloudWatch metric that acts as the foundation for the alarm. The list of metrics will change depending on the selected **Target Resource Type**. 1. In the **Alarm settings** section: **Note** For more information about how the CloudWatch service handles alarms and details of the alarm components, see: [Using CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) in the *Amazon CloudWatch User Guide* 1. Select the **Statistic**. This is a value such as a **Sum** or an **Average** that will be used to monitor the metric. 1. Select the **Comparison Operator**. This field references the **Threshold** that you set in the next step. 1. Set a **Threshold**. This is a numeric value that the **Comparison Operator** uses to determine greater than, less than, or equal to status. 1. Set a **Period**. This is a time value, in seconds. The **Period** is the length of time that the **Statistic**, **Comparison Operator**, and **Threshold** interact to determine if the alarm gets triggered. 1. Set the **Datapoints**. This value determines how many datapoints are needed to trigger the alarm. 1. Select how to **Treat Missing Data**. This selection determines how this alarm reacts to missing data. 1. Select **Create** to complete the process. An example of a completed alarm template could have the following parameters: A MediaConnect flow **Target Resource Type** is monitored for the Disconnections **Metric Name**. The **Statistic** value is set to Sum with a **Comparison Operator** of "greater than or equal to" and a **Threshold** of 10. The **Period** is set to 60 seconds, and only requires 1 out of 1 **Datapoints**. **Treat Missing Data** is set to "ignore." The result of these settings is: workflow monitor will monitor for disconnections on the flow. If 10 or more disconnections occur within 60 seconds, the alarm will be triggered. 10 or more disconnections in 60 seconds only needs to happen one time for the alarm to be triggered. # Recommended alarm templates for monitoring your AWS media workflow Recommended templates Workflow monitor's recommended templates are a curated selection of AWS Elemental service metrics with predefined alarm settings appropriate for the metric. If you do not want to create customized alarm templates, recommended templates provide you with best-practice monitoring templates that are created by AWS. Workflow monitor contains recommended template groups for each supported service. These groups are designed to apply best-practice monitoring to specific types of workflows. Each template group contains a curated selection of alarms configured from service-specific metrics. For example, a recommended template group for a MediaLive multiplex workflow will have a different set of preconfigured metrics than a MediaConnect CDI workflow. **To use recommended alarm templates** 1. Follow the steps to [create an alarm template group](monitor-with-workflow-monitor-configure-alarms.md#monitor-with-workflow-monitor-alarms-groups-create), or select an existing one. 1. In the **Alarm templates** section, select **Import**. You will need to import the AWS recommended templates into your template group. 1. Use the **CloudWatch alarm template groups** dropdown to select an AWS recommended group. These groups contain curated alarms for specific services. 1. Select the templates to import using the check boxes. Each template will list its metrics, preconfigured monitoring values, and provide a description of the metric. When you are done selecting templates, select the **Add** button. 1. The selected templates will move to the **Alarm template(s) to import** section. Review your choices and select **Import**. 1. After the import is complete, the selected templates will be added to the template group. If you want to add more templates, repeat the import process. 1. Imported templates can be customized after import. Alarm settings can be modified to fit your alarming needs. # EventBridge rule groups and templates for monitoring your AWS media workflow EventBridge rules CloudWatch uses Amazon EventBridge rules to send notifications. You begin by creating an event template group. In that event template group, you create event templates that determine what conditions create a notification and who is notified. This section covers the creation of EventBridge rules using workflow monitor. For more information about how the EventBridge service uses rules, see: [EventBridge rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rules.html) in the *Amazon EventBridge User Guide* ## Creating event template groups Event template groups allow you to sort and classify events based on your use case. **To create an event template group** 1. From the workflow monitor console's navigation pane, select **EventBridge rule templates**. 1. Select **Create event template group**. 1. Give the alarm template group a unique **Group name** and optional **Description**. 1. Select **Create**, You will be taken to the newly created alarm template group's details page. ## Creating event templates You can send notifications based on event templates you create. **To create an event template** 1. From the event template group's details page, select **Create event template**. 1. Give the event template a unique **Template name** and optional **Description**. 1. In the **Rule settings** section: 1. Select an **Event type**. When selecting an event type, you can choose between several events created by AWS or select **Signal map active alarm** to use an alarm created by an alarm template. 1. Select a **Target service**. This determines how you would like to be notified of this event. You can select Amazon Simple Notification Service or CloudWatch logs. 1. After selecting a target service, select a **Target**. This will be a Amazon SNS topic or a CloudWatch log group, depending on your target service selection. 1. Select **Create** to complete the process. # Workflow monitor signal maps Signal maps Signal maps are visual mappings of AWS resources in your media workflow. You can use workflow monitor to start the signal map discovery on any of the supported resource types. During the discovery process, workflow monitor will automatically and recursively map all connected AWS resources. After the signal map has been created, you can use the workflow monitor console to do things like deploy monitoring templates, view metrics, and view details of the mapped resources. **Topics** + [ # Creating signal maps for AWS media workflows ](monitor-with-workflow-monitor-configure-signal-maps-create.md) + [ # Viewing signal maps of AWS media workflows ](monitor-with-workflow-monitor-configure-signal-maps-view.md) + [ # Attaching alarm and event templates to the signal map of your AWS media workflow ](monitor-with-workflow-monitor-configure-signal-maps-attach.md) + [ # Deploying templates to the signal map of your AWS media workflow ](monitor-with-workflow-monitor-configure-deploy.md) + [ # Updating the signal map of your AWS media workflow ](monitor-with-workflow-monitor-configure-signal-maps-update.md) + [ # Deleting the signal map of your AWS media workflow ](monitor-with-workflow-monitor-configure-signal-maps-delete.md) # Creating signal maps for AWS media workflows Creating signal maps You can use workflow monitor signal maps to create a visual mapping of all connected AWS resources in your media workflow. **To create a signal map** 1. From the workflow monitor console's navigation pane, select **Signal maps**. 1. Select **Create signal map**. 1. Give the signal map a **Name** and **Description**. 1. In the **Discover new signal map** section, resources in the current account and selected region are displayed. Select a resource to begin signal map discovery. The selected resource will be the starting point for discovery. 1. Select **Create**. Allow a few moments for the discovery process to complete. After the process is complete, you will be presented with the new signal map. **Note** Previews generated in the workflow monitor signal map for AWS Elemental MediaPackage channels are delivered from the MediaPackage Origin Endpoint and will incur Data Transfer Out charges. For pricing, see: [MediaPackage pricing](https://aws.amazon.com/mediapackage/pricing/). # Viewing signal maps of AWS media workflows Viewing signal maps Workflow monitor signal maps allow you to see a visual mapping of all connected AWS resources in your media workflow. **Signal map views** After selecting a signal map, you have two views that can be used to monitor or configure the signal map. **Monitor signal map** and **Configure signal map** is a context-sensitive button found in the upper-right of the signal map console section. If you select the signal map using the **Signal maps** section of the navigation pane, your signal map will be displayed in the configuration view. The configuration view allows you to make changes to the template groups attached to this signal map, deploy the attached templates, and view the basic details and tags of the signal map. If you select the signal map using the **Overview** section of the navigation pane, your signal map will be displayed in monitoring view. The monitoring view displays the CloudWatch alarms, EventBridge rules, alerts, logs, and metrics for this signal map. The view can be changed at any time by selecting the **Monitor/Configure signal map** button in the upper-right. The configuration view requires administrator-level IAM permissions. Required IAM permissions can be viewed here: [Workflow monitor IAM policies](monitor-with-workflow-monitor-configure-getting-started-IAM.md) **Navigating the signal map** A signal map will contain nodes for every supported AWS resource discovered by workflow monitor. Certain resources, such as MediaLive channels and MediaPackage endpoints can display thumbnail previews of the content, if thumbnail previews are available. Selecting a resource node, and selecting **View selected resource details** from the **Actions** dropdown menu will take you to the associated service's details page. For example, selecting a MediaLive channel and selecting **View selected resource details** will open the MediaLive console's details page for that channel. Selecting a resource node will filter the list of active alarms to only that node. If you select the resource's **Target ARN** in the active alarm, you will be taken to the associated service's details page, with the selected resource open. # Attaching alarm and event templates to the signal map of your AWS media workflow Attaching templates After you have created alarm and event templates, you need to attach these to a signal map. Any of the alarm and event templates you have created can be attached to any discovered signal maps. **To attach alarm and event templates to your signal map** 1. From the workflow monitor console's navigation pane, select **Signal maps** and select the signal map you want to work with. 1. In the upper-right of the signal map page, in the **CloudWatch alarm template groups** tab, select **Attach CloudWatch alarm template groups**. 1. In the new section that opens, choose all of the alarm template groups that you want to apply to this signal map, then select **Add**. This will cause the selected alarm template groups to move to the **Attached CloudWatch alarm template groups** section. 1. Selecting **Save** will save your changes and return you to the signal map page. 1. At the right of the signal map page, select the **EventBridge rule template groups** tab then select **Attach EventBridge rule template groups**. 1. In the new section that opens, choose all of the event template groups that you want to apply to this signal map, then select **Add**. This will cause the selected rule template groups to move to the **Attached EventBridge rule template groups** section. 1. Selecting **Save** will save your changes and return you to the signal map page. 1. You have assigned CloudWatch alarm and EventBridge rule templates to the signal map, but the monitoring is not yet deployed. The next section will cover the deployment of the monitoring resources. # Deploying templates to the signal map of your AWS media workflow Deploying monitoring templates After you have attached the alarm and event templates to your signal map, you must deploy the monitoring. Until the deployment is complete, the monitoring of your signal map will not be active. Workflow monitor will only deploy alarms that are relevant to the selected signal map. For example, the attached alarm template group might contain alarms for multiple services, such as MediaLive, MediaPackage, and MediaConnect. If the selected signal map only contains MediaLive resources, no MediaPackage or MediaConnect alarms will be deployed. **To deploy the monitoring templates** 1. After attaching alarm and event template groups to your signal map and saving your changes, select **Deploy monitor** in the **Actions** dropdown menu. 1. You will be asked to confirm the deployment and presented with the number of CloudWatch and EventBridge resources that will be created. If you would like to proceed, select **Deploy**. **Note** There is no direct cost for using workflow monitor. However, there are costs associated with the resources created and used to monitor your workflow. When monitoring is deployed, Amazon CloudWatch and Amazon EventBridge resources are created. When using the AWS Management Console, prior to deploying monitoring to a signal map, you will be notified of how many resources will be created. For more information about pricing, see: [CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/) and [EventBridge pricing](https://aws.amazon.com/eventbridge/pricing/). Workflow monitor uses AWS CloudFormation templates to deploy the CloudWatch and EventBridge resources. These templates are stored in a standard class Amazon Simple Storage Service bucket that is created on your behalf, by workflow monitor, during the deployment process and will incur object storage and recall charges. For more information about pricing, see: [Amazon S3 pricing](https://aws.amazon.com/s3/pricing/). 1. The status of the deployment is displayed next to the name of the signal map. The deployment status is also visible in the **Stacks** section of the CloudFormation console. After a few moments of resource creation and deployment, your signal map monitoring will begin. # Updating the signal map of your AWS media workflow Updating signal maps If a change is made to your workflow, you might need to rediscover the signal map and redeploy monitoring resources. Workflow monitor is a visualization and monitoring tool that does not have the ability to make any changes to your workflow. Signal maps represent a point-in-time visualization of your workflow. In the event that you add, remove, or significantly modify parts of your media workflow, we recommend that you rediscover the signal map. If you have monitoring resources attached to the signal map, we recommend you redeploy monitoring after the rediscovery process. **To rediscover a signal map** 1. From the workflow monitor console's navigation pane, select **Signal maps** and select the signal map you want to work with. 1. Verify that you are in the **Configure signal map** view. For more information about changing views, see: [Viewing signal maps ](monitor-with-workflow-monitor-configure-signal-maps-view.md) 1. In the upper-right of the signal map page, select the **Actions** dropdown menu. Select **Rediscover**. 1. You will be presented with the rediscovery screen. Select a resource that is a part of the workflow you are rediscovering. Select the **Rediscover** button. 1. The signal map will be rebuilt according to the current workflow. If you need to redeploy monitoring resources, stay on this signal map's page. Any previously attached monitoring templates will remain attached, but will need to be redeployed. **To redeploy monitoring templates after a signal map rediscovery** 1. After the rediscovery, you will be directed to the updated signal map. To redeploy the monitoring templates, select **Deploy monitor** from the **Actions** dropdown menu. 1. You will be asked to confirm the deployment and presented with the number of any CloudWatch and EventBridge resources that will be created. If you would like to proceed, select **Deploy**. 1. The status of the deployment is displayed next to the name of the signal map. After a few moments of resource creation and deployment, your signal map monitoring will begin. # Deleting the signal map of your AWS media workflow Deleting signal maps If you not longer need a signal map, it can be deleted. If you have monitoring templates deployed on the signal map, the deletion process will ask you to delete any CloudWatch and EventBridge resources that have been deployed to this signal map. Deleting the deployed resources does not affect the templates that created them. This resource deletion is to ensure that you do not have CloudWatch and EventBridge resources that are deployed but not used. **To delete a signal map** 1. From the workflow monitor console's navigation pane, select **Signal maps** and select the radio button next to the signal map you want to delete. 1. Select the **Delete** button. You will be asked to confirm the deletion of the monitoring resources. Select **Delete** to begin the monitoring resource deletion process. 1. The **Monitor deployment** column will display the current status. When the status has changed to **DELETE\$1COMPLETE**, select the **Delete** button again. 1. You will be asked to confirm deletion of the signal map. Select **Delete** to proceed and delete the signal map. # Workflow monitor quotas Quotas The following section contains quotas for workflow monitor resources. Each quota is on a "per account" basis. If you need to increase a quota for your account, you can use the [AWS Service Quotas console](https://console.aws.amazon.com/servicequotas/home) to request an increase, unless otherwise noted in the following table. **Quotas** | Resource type | Quota | | --- | --- | | CloudWatch alarm template groups | 20 | | CloudWatch alarm templates | 200 | | EventBridge rule template groups | 20 | | EventBridge rule templates | 200 | | Signal maps | 30 | | Signal maps: CloudWatch alarm template groups attached to a single signal map | 5You cannot increase this quota. | | Signal maps: EventBridge rule template groups attached to a single signal map | 5You cannot increase this quota. | # Using workflow monitor Using workflow monitor Use the **overview** and **signal maps** sections of the workflow monitor console to review the current status of the workflows and any associated alarms, metrics, and logs. **Topics** + [ # Workflow monitor overview ](monitor-with-workflow-monitor-operate-overview.md) + [ # Overview logs and metrics for workflow monitor ](monitor-with-workflow-monitor-operate-logs-metrics.md) + [ # Using workflow monitor signal maps ](monitor-with-workflow-monitor-operate-signal-maps.md) # Workflow monitor overview Overview The **Overview** section of the workflow monitor console is a dashboard that provides at-a-glance information about your signal maps. In the overview section, you can see the current state of each signal map's monitoring, as well as CloudWatch metrics and any associated CloudWatch logs. You can select any signal map to be taken to that signal maps console page. **Overview filtering** Using the **Search** bar in the overview section, you can filter the list of signal maps using context sensitive constraints. After selecting the search bar, you will be presented with a list of **Properties** to filter by. Selecting a property will present **Operators** such as Equals, Contains, Does not equal, and Does not contain. Selecting an operator will create a list of resources from the selected property type. Selecting one of these resources will cause the signal map list to only display signal maps that fit the constraint you defined. # Overview logs and metrics for workflow monitor Logs and metrics To view CloudWatch metrics and logs for a signal map, select the radio button next to the name of the signal map. A tabbed interface for both metrics and logs will appear beneath the signal map list. **CloudWatch Metrics** CloudWatch metrics for the selected signal map will be context-sensitive and only display metrics associated with the services used in that signal maps workflow. You can use the on-screen metrics tools to customize the displayed metric periods and time ranges. **CloudWatch Logs ** If you associated a CloudWatch log group with the signal map, that group will be displayed here. # Using workflow monitor signal maps Using signal maps From the **overview** section of the console, you can select a specific signal map to view more information about that signal map and its attached monitoring resources. After selecting a signal map, you will be presented with the signal map and a number of tabbed section containing more information: + CloudWatch alarms + EventBridge rules + AWS Elemental alerts + Metrics + Logs + Basic details **Navigating the signal map** A signal map will contain nodes for every supported AWS resource discovered by workflow monitor. Certain resources, such as MediaLive channels and MediaPackage endpoints can display thumbnail previews of the content, if thumbnail previews are available. Selecting a resource node, and selecting **View selected resource details** from the **Actions** dropdown menu will take you to the associated service's details page. For example, selecting a MediaLive channel and selecting **View selected resource details** will open the MediaLive console's details page for that channel. Selecting a resource node will filter the list of active alarms to only that node. If you select the resource's **Target ARN** in the active alarm, you will be taken to the associated service's details page, with the selected resource open.