![]() If provided with no value or the value input, prints a sample input JSON that can be used as an argument for -cli-input-json. Prints a JSON skeleton to standard output without sending an API request. This may not be specified along with -cli-input-yaml. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. If other arguments are provided on the command line, those values will override the JSON-provided values. The JSON string follows the format provided by -generate-cli-skeleton. Reads arguments from the JSON string provided. cli-input-json | -cli-input-yaml (string) CloudWatch does not perform unit conversions. ![]() If you specify a unit that does not match the data collected, the results of the operation are null. If you specify a unit, the operation returns only data that was collected with that unit specified. If you omit Unit, all data that was collected with any unit is returned, along with the corresponding units that were specified when the data was reported to CloudWatch. If you make a query at 15:07:17 for the previous 5 minutes of data, using a period of 5 seconds, you receive data timestamped between 15:02:15 and 15:07:15. For example, if you make a query at (HH:mm:ss) 01:05:23 for the previous 10-second period, the start time of your request is rounded down and you receive data from 01:05:10 to 01:05:20. If you set Period to 5, 10, or 30, the start time of your request is rounded down to the nearest time that corresponds to even 5-, 10-, or 30-second divisions of a minute. Start time greater than 63 days ago - Round down to the nearest 1-hour clock interval.Start time between 15 and 63 days ago - Round down to the nearest 5-minute clock interval.Start time less than 15 days ago - Round down to the nearest whole minute.In a raw HTTP query, the time stamp must be in ISO 8601 UTC format (for example, ).ĬloudWatch rounds the specified time stamp as follows: The value specified is inclusive results include data points with the specified time stamp. Start times are evaluated relative to the time that CloudWatch receives the request. The time stamp that determines the first data point to return. After 63 days, the data is further aggregated and is available with a resolution of 1 hour.ĬloudWatch started retaining 5-minute and 1-hour metric data as of July 9, 2016.įor information about metrics and dimensions supported by Amazon Web Services services, see the Amazon CloudWatch Metrics and Dimensions Reference in the Amazon CloudWatch User Guide. After 15 days, this data is still available, but is aggregated and retrievable only with a resolution of 5 minutes. For example, if you collect data using a period of 1 minute, the data remains available for 15 days with 1-minute resolution. Data points with a period of 3600 seconds (1 hour) are available for 455 days (15 months).ĭata points that are initially published with a shorter period are aggregated together for long-term storage.Data points with a period of 300 seconds (5-minute) are available for 63 days.Data points with a period of 60 seconds (1-minute) are available for 15 days.These data points are high-resolution metrics and are available only for custom metrics that have been defined with a StorageResolution of 1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |