HikeHills.com (HH) is an online specialty retailer that sells clothing and outdoor refreshment gear for trekking, go camping, boulevard biking, mountain biking, rock hiking, ice mountaineering, skiing, avalanche protection, snowboarding, fly fishing, kayaking, rafting, road and trace running, and many more. HHruns their entire online infrastructure on multiple java based web applications and other web framework applications running on AWS.
The HH is capturing click stream data and use custom- build recommendation engine to recommend products which eventually improve sales, understand customer preferences and already using AWS kinesis data streams (KDS) to collect events and transaction logs and process the stream.
Multiple departments from HH use different streams to address real-time integration and induce analytics into their applications and uses Kinesis as the backbone of real-time data integration across the enterprise. HHunderstand that Monitoring plays a major role in monitoring and managing the streaming platform.
HH using kinesis agent to process events and uses consumer library KCL o collect and disseminate streams.
What kind of monitoring is enabled by KCL Library? select 3 options.
Click on the arrows to vote for the correct answer
A. B. C. D. E.Answer: B,C, E.
Option A is incorrect - These metrics are published by Kinesis Streams to cloud watch.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-cloudwatch.htmlOption B is correct -This is one of the key metrics provided by KCL library.
Per-KCL-Application Metrics, The metrics that are aggregated across all KCL workers within the scope of the application, as defined by the Amazon CloudWatch namespace
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-kcl.htmlOption C is correct - This is one of the key metrics provided by KCL library.
Per-Worker Metrics, These metrics are aggregated across all record processors consuming data from a Kinesis data stream, such as an Amazon EC2 instance
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-kcl.htmlOption D is incorrect -These metrics are published by Kinesis Agent.
https://docs.aws.amazon.com/streams/latest/dev/agent-health.htmlOption E is correct -This is one of the key metrics provided by KCL library.
Per-Shard Metrics, The metrics are aggregated across a single record processor.
https://docs.aws.amazon.com/streams/latest/dev/monitoring-with-kcl.htmlKinesis Client Library (KCL) is a Java library that simplifies the process of building Java applications that use Amazon Kinesis Data Streams. It takes care of many of the complex tasks involved in consuming and processing data streams, such as load balancing, checkpointing, and error handling. KCL also provides a number of monitoring features that allow you to track the performance and health of your Kinesis Data Streams applications.
The following are the monitoring features that are enabled by KCL:
A. Metrics configured for streams are automatically collected and pushed to CloudWatch every minute: KCL automatically collects and publishes a set of metrics for the Kinesis data stream that your application is consuming. These metrics include the number of records processed, the number of bytes processed, and the latency of record processing. The metrics are collected every minute and are automatically pushed to Amazon CloudWatch, where you can use them to monitor the health of your application and troubleshoot issues.
B. Per-KCL-Application Metrics: In addition to the metrics that are collected for the Kinesis data stream, KCL also collects metrics for the application itself. These metrics are aggregated across all KCL workers within the scope of the application, as defined by the Amazon CloudWatch namespace. These metrics include the number of records processed by the application, the number of bytes processed, and the latency of record processing.
C. Per-Worker Metrics: KCL also collects metrics for each worker that is consuming data from the Kinesis data stream. These metrics are aggregated across all record processors consuming data from a Kinesis data stream, such as an Amazon EC2 instance. The metrics include the number of records processed, the number of bytes processed, and the latency of record processing.
D. The KCL publishes Bytes sent, number of records attempted, number of records that returned failure and the number of calls to PutRecords that resulted in a service error: KCL also publishes metrics related to the performance of PutRecords API calls, which are used to put records into the Kinesis data stream. These metrics include the number of bytes sent, the number of records attempted, the number of records that returned failure, and the number of calls to PutRecords that resulted in a service error.
E. Per-Shard Metrics: Finally, KCL collects metrics for each shard in the Kinesis data stream. These metrics are aggregated across a single record processor and include the number of records processed, the number of bytes processed, and the latency of record processing.
In summary, Kinesis Client Library provides several monitoring features that enable you to track the performance and health of your Kinesis Data Streams applications. These include metrics for the Kinesis data stream, the application itself, each worker, each shard, and PutRecords API calls. By using these metrics, you can identify and troubleshoot issues with your application and ensure that it is performing optimally.