AWS Monitor Addition - FAQs
Best Practices while adding an Amazon monitor in Applications Manager:
- Provide proper 'Display name' for the Amazon monitor.
- Select the Amazon services you want to discover from the Amazon services drop box. By default, all the services will be selected. Currently Applications Manager supports EC2, ElasticBeanstalk, DynamoDB, Load Balancers, ECS, EKS, Lambda, SNS, SQS, S3 and RDS. To know more, refer here.
- To monitor an AWS Account, you need an Access Key ID and Secret Access Key. To create the Access Key ID and Secret Access Key, follow these steps.
- Use the keys you obtained from the above step to fill the Access Key ID and Secret Access Key fields when adding an Amazon monitor in Applications Manager.
- Select the appropriate Account Type for the credentials. By default, the Account Type is AWS Global. To monitor AWS services running in the AWS China/AWS Gov Cloud regions, choose Account Type as AWS China/AWS Gov Cloud and try adding the monitor.
- Based on the Account Type, Global Regions or China Regions or AWS Gov Cloud Regions will be shown. Only from the chosen regions, the resources will be discovered and monitored. By default, 'All regions' will be selected for AWS Global account type.
- Use the Child Discovery option to specify how to discover and monitor the resources (All the discovered monitors under amazon will be considered as child monitors).
- Do not discover: Adds amazon monitor but discovery will not happen.
- Discover and unmanage: Discovers all the child monitors but will set them in the unmanaged state by default.
- Discover and monitor child monitors: Discovers and monitors all the child monitors.
- Enable Advanced Settings for the below options:
-> You can also choose to configure an automatic action for a deleted resource using 'Action on Deleted Resource'.
- Continue Alerting: The option will keep the deleted instances in the AWS console and deleted alerts will be shown in the child and parent monitor in APM. You will receive alerts during every poll.
- Stop Alerting: The option will not affect the health of the deleted instances and will stop alerting.
- Unmanage Resource: The option will unmanage the deleted resources.
- Delete Resource: The option will delete the monitors which have been deleted from the AWS console.
Note : EC2 instance will be deleted or unmanaged only after it is deleted in the AWS console. As per AWS, EC2 will be deleted from console after 60 mins.
- Regex to filter EC2 Instances name : A regex can be specified in the field to filter and discover the EC2 instances whose name matches the regex.
- Regex may contain alphanumeric characters, hyphen(-), underscore(_) and period(.).
- Specify '.*' to ignore characters. More than one set of '.*' can be used.
- By default, '.*' is specified that allows all the instances.
- At least one '.*' should be present in the regex.
- EC2 instances without names are automatically omitted unless their instance ID match with regex.
- Examples :
- ".*" (allows all instances with any name)
- ".*test" (Allows instances whose name ends with test)
- ".*-.*demo" (Allows instances whose name contains '-' in the middle and ends with demo).
- Stop Discovery : Used to stop further discovery of child resources.
- This option will be useful for editing and updating AWS monitor in APM.
While editing and updating existing AWS monitor:
- If a service is unselected from Amazon Services, all the existing monitors under that service will be deleted from Applications Manager.
- If a region is unselected from Global regions/ China regions, existing monitors in that region will be retained.
- The option Do not discover in child discovery will be applicable to all the services. Existing monitors won't be affected. If you want to stop discovery for a specific service use Stop discovery option in Advanced Settings. (Point 5 mentioned below)
- The options Discover and unmanage and Discover and monitor child monitors will be applicable to newly discovered monitors only. Existing monitors will remain in their existing state.
- If you check the Stop Discovery check box, it enables the Services to Stop Discovery drop down. You can choose the services for which you want to stop the further discovery of resources but the existing monitors will continue to be monitored.
- If you change from Discover and unmanage to Discover and monitor child monitors or vice versa, the existing state of the child monitors will be retained.
- When you 'Unmanage' and 'Manage' an Amazon monitor, all the child monitors will be unmanaged and managed respectively irrespective of their existing state. This is the behavior of all the parent-child monitors in Applications Manager.
REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...
AWS EKS Troubleshooting FAQs
AWS EKS monitor can be configured only if you have already added an Amazon monitor in Applications Manager. Ensure that you have met the pre-requisites for the Amazon monitor before monitoring Elastic Kubernetes Service in Applications Manager. How ...
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for long time. Follow below steps for troubleshooting Check prerequisites to done : Real User Monitor requires RUM Agent to be installed and mapped to Applications Manager. Refer the help page to know how to setup ...
Script Monitor FAQs
Common queries, errors and troubleshooting: 1. To execute scripts other than .bat /.vbs in Windows and .sh / .bash in Linux: It is better to execute the script in the form of a command. Eg. To execute python script, you can use command py ...
Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...