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
Setup monitoring for kinesis firehose with monitoring.monitorKinesisFirehose().
Deploy cdk to aws account.
Expected behavior
The graphs display information about the kinesis firhose normally.
Actual behavior
The Latency (P90) graph and the Limits (rate) graph both show now data do to their metrics being incorrect. The PutRecords and PutRecordsBatch metrics for kinesis firehose don't support percentiles so the Latency graph doesn't display any data. Also the DeliveryStreamName dimension isn't isn't specified for BytesPerSecondLimit so the Limits graph doesn't display any data.
Other details
No response
The text was updated successfully, but these errors were encountered:
regarding to Latency graph, I think the issue should be raised with AWS CloudWatch service, as per Doc indicated, Kinesis metric should support percentile.
Another thing worth checking is the region where your kinesis firehose is deployed. According to the news release here from 2016, only the following regions are supported US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), EU (Ireland), EU (Frankfurt), S. America (São Paulo), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Mumbai) and Asia Pacific (Sydney). (this could have changed since then).
Version
v1.18.4
Steps and/or minimal code example to reproduce
monitoring.monitorKinesisFirehose()
.Expected behavior
The graphs display information about the kinesis firhose normally.
Actual behavior
The Latency (P90) graph and the Limits (rate) graph both show now data do to their metrics being incorrect. The PutRecords and PutRecordsBatch metrics for kinesis firehose don't support percentiles so the Latency graph doesn't display any data. Also the DeliveryStreamName dimension isn't isn't specified for BytesPerSecondLimit so the Limits graph doesn't display any data.
Other details
No response
The text was updated successfully, but these errors were encountered: