There are two existing drivers for AWS MediaConnect - what's the difference and when should they be used?
There is indeed a free and a paid tier for Amazon AWS CloudWatch. More information about the pricing is available here: https://aws.amazon.com/cloudwatch/pricing/.
In short, there is a free tier, but this only provides a basic set of metrics that are only refreshed at a specific rate. Metrics will be charged as soon as you want to deviate from this (higher refresh rate or custom metrics).
As far as I can tell, using the MediaConnect API is free as you are charged for the services that you use and not how you initiate them.
Hi Bruno,
Here are some details about the metrics related to Media Connect current implementations. Both drivers retrieve this information using the Cloud Watch API.
On Media Connect driver:
- 53 metrics per flow
- 26 metrics per source
On Cloud Watch driver
- 22 metrics per flow, source and zones
Both have the capability to poll specific metrics in case an alarm is configured on Cloud Watch to notify DataMiner.
Related to the Media Connect API
The Media Connect Driver currently implements
- ListFlows
- StartFlow
- StopFlow
- DescribeFlow (information about Sources and Outputs)
- ListEntitlements
It will be implementing
- AddFlowSources
- UpdateFlowSource
- RemoveFlowSource
I hope this may help.
great intel, real helpful. Thanks, Julio.
The latest MediaConnect driver now supports updating of Flow Sources and Destinations via DataMiner.
And while we are at it, just to piggy back on this question. I have heard that the AWS CloudWatch driver has various options in it to enable / disable the collection of specific individual metrics and to customize the refresh rate (i.e. the rate at which DataMiner goes and fetches updates for individual metrics), and that the reason for that is because the charge for the CloudWatch service is based on how much data you are pulling from it. Is that correct? And also, if so, does that apply as well to the MediaConnect native API used by the other driver?