- Newest
- Most votes
- Most comments
Hi,
your call parameters look OK, so usually when you get an empty result it is driven by a typo in dimension values, that the metric is actually empty, or that the start-time and end-time don't match any data.
In order to lift ambiguity for a possible mistake in dimension values, the best would be to call aws cloudwatch list-metrics --namespace "AWS/MediaLive" and make sure the output lists NetworkOut with the exact array of dimensions and dimension values you're trying to query. According to MediaLive documentation, NetworkOut supports dimensions ChannelId, Pipeline => are you missing the Pipeline dimension? If you are, you'd need to add it to your array of dimensions, you must have a 100% match of the dimension array in your get-metric-data call with the dimension arrays that list-metrics will give you.
@Jsc thank you for your answer but it did't worked. Can you please suggest where i am wrong.
1- could you please share the output of aws cloudwatch list-metrics --namespace "AWS/MediaLive" --dimensions "[ { "Name": "ChannelId", "Value": "4333058" } ]" for double check? 2- can you try with a wider time range, have you checked for possible time sync issues or timezone discrepancy between what the date command gives you and your data?
If you get the metric name and full list of dimensions 100% right, the next thing I can think of is timestamp mismatch
Relevant content
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago