You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the kit to send custom metrics to Amazon CloudWatch.
By default the standard resolution has one-minute granularity, but there is a possibility to use high resolution, with data at a granularity of one second. More info (amazon docs)
// Encapsulates the information sent to either create a metric or add new values// to be aggregated into an existing metric.typeMetricDatumstruct {
...// Valid values are 1 and 60. Setting this to 1 specifies this metric as a high-resolution// metric, so that CloudWatch stores the metric with sub-minute resolution down// to one second. Setting this to 60 specifies this metric as a regular-resolution// metric, which CloudWatch stores at 1-minute resolution. Currently, high resolution// is available only for custom metrics. For more information about high-resolution// metrics, see High-Resolution Metrics (https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html#high-resolution-metrics)// in the Amazon CloudWatch User Guide.//// This field is optional, if you do not specify it the default of 60 is used.StorageResolution*int64`min:"1" type:"integer"`...
}
So, now using this kit there no possibility to set this parameter to custom value before sending to CloudWatch and it's set to 60 by default.
I'd like to implement this feature. I think it can be really useful for anyone who uses this kit to send custom metrics to Amazon CloudWatch.
The text was updated successfully, but these errors were encountered:
Hi there.
I'm using the kit to send custom metrics to Amazon CloudWatch.
By default the standard resolution has one-minute granularity, but there is a possibility to use high resolution, with data at a granularity of one second. More info (amazon docs)
So, now using this kit there no possibility to set this parameter to custom value before sending to CloudWatch and it's set to 60 by default.
I'd like to implement this feature. I think it can be really useful for anyone who uses this kit to send custom metrics to Amazon CloudWatch.
The text was updated successfully, but these errors were encountered: