Default Parameters for AWSMSKMemoryTest

Using this test, administrators can proactively measure the memory usage of each cluster in AWS Managed Service Kafka server, and judge whether/not adequate free memory is available on the cluster of the target AWS MSK server. By detecting a potential memory contention on the cluster of the target server at the earliest, administrators can easily avert slowdowns or potential outages of the server.

This page depicts the default parameters that need to be configured for the AWSMSKMemoryTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the IP address of the target server that is being monitored.

• This test uses AWS CLI to interact with AWS Managed Service Kafka and pull relevant metrics. To enable the test to connect to AWS, you need to configure the test with the name of the region to which all requests for metrics should be routed, by default. Specify the name of this AWS Default Region, in the AWS DEFAULT REGION text box...

• To monitor AWS Managed Service Kafka, the eG agent has to be configured with the access key and secret key of a user with a valid AWS account. For this purpose, we recommend that you create a special user on the AWS cloud, obtain the AWS Access Key ID and AWS Secret Access Key of this user, and configure this test with these keys. The procedure for this has been detailed in the Obtaining an Access key and Secret key topic. Make sure you reconfirm the access and secret keys you provide here by retyping it in the corresponding CONFIRM PASSWORD text box.

• In the TIMEOUT text box, specify the maximum duration (in seconds) for which the test will wait for a response from the server. The default is 10 seconds.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.