Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latency and Limits graph for monitorKinesisFirehose don't work #351

Open
bschondo opened this issue Apr 7, 2023 · 2 comments
Open

Latency and Limits graph for monitorKinesisFirehose don't work #351

bschondo opened this issue Apr 7, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@bschondo
Copy link

bschondo commented Apr 7, 2023

Version

v1.18.4

Steps and/or minimal code example to reproduce

  1. Create a stack with kinesis firehose.
  2. Setup monitoring for kinesis firehose with monitoring.monitorKinesisFirehose().
  3. 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

@bschondo bschondo added the bug Something isn't working label Apr 7, 2023
@echeung-amzn
Copy link
Member

Limits graphs are fixed by #378

@jiashuChen
Copy link
Contributor

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants