Follow the steps for installing Applicare SingleAgent
Note: Either the SingleAgent can be installed in a local or AWS EC2 instance. From agent machine it should have access to the RDS MySQL instance and controller machine.
Configuration in MySQL instance
- The MySQL instance should be accessed from outside the AWS.
- The user which we are going to configure in applicare should have the same permission as master user.
- performance_schema parameter value should be 1.
- performance_schema_events_statements_history_size value should be1024.
- performance_schema_events_statements_history_long_size value should be1024
- Whenever we modify the Performance Schema values, we must restart the db instance.
[Screenshot 1 is not available on this page.]
Steps to check the performance_schema is enabled
- Select the database instance and go to Configuration and check the Parameter group assigned to that.
[Screenshot 2 is not available on this page.]
- Go to RDS -> Parameter groups screen
[Screenshot 3 is not available on this page.]
- Select that parameter group which we are going to edit and select Edit option from the Parameter group actions dropdown.
[Screenshot 4 is not available on this page.]
- Search performance_schema and select the performance_schema parameter and check the value.
[Screenshot 5 is not available on this page.]
- Search performance_schema_events_statements_history_size and performance_schema_events_statements_history_long_size parameter and check the value.
[Screenshot 6 is not available on this page.]
The performance_schema value should be 1, performance_schema_events_statements_history_size value should be 1024 and performance_schema_events_statements_history_long_size value should be 1024.
If the values are different then edit that parameter group and change the value.
Steps to edit the parameter group
- Search performance_schema and select the performance_schema parameter and change the value to 1.
[Screenshot 7 is not available on this page.]
- Search performance_schema_events_statements_history_size and select the performance_schema_events_statements_history_size parameter and change the value to 1024.
[Screenshot 8 is not available on this page.]
- Likewise do the changes for the performance_schema_events_statements_history_long_size parameter.
- Save the changes
If we did any modifications in the performance_schema values then restart the db instance for the changes to take place. Otherwise db instance restart is not required.
Steps to Restart the DB instance
[Screenshot 9 is not available on this page.]
> [Screenshot 10 is not available on this page.]
Note:
If we are not able to modify the existing parameter group assigned to that db instance then create a new one which contains all the settings of the previous parameter group and modify the performance schema , performance_schema_events_statements_history_size and performance_schema_events_statements_history_long_size values in that and assign the new parameter group to the db instance.
Steps to create a new parameter group and assign to the Database.
- Go to RDS -> Parameter Group and click the Create parameter group
[Screenshot 11 is not available on this page.]
- Enter the Group name, Description and click Create button.
[Screenshot 12 is not available on this page.]
- Edit that parameter group and add the performance schema, performance_schema_events_statements_history_size and performance_schema_events_statements_history_long_size values and save the changes.
- Select the database instance and click the Modify button.
[Screenshot 13 is not available on this page.]
- Select the newly created parameter group in the DB Parameter group dropdown and save the changes.
[Screenshot 14 is not available on this page.]
- Restart the db instance for the changes to take place.