On the Coati GUI management screen, detailed configurations can be made for monitoring targets and Coati’s behavior. Configurable items are as follows.
- Selecting unmonitored EC2 instances
- Selecting unmonitored services
- Email notification timing
- Selecting a restoration mode
This chapter describes how to use and set GUI management screen.
Login
Logging in from the sign in screen let you access Coati's management screen. Please log in with your registered email address and password.
Dashboard
When login is completed, the dashboard will be displayed. A summary of information including Coati’s status is displayed here.
Dashboard
A link to the dashboard.
Instance Management
Displays the status of monitored/unmonitored instances and the status of each instance after failure detection.
Monitoring Settings
You can set a monitoring mode (monitor/unmonitor/monitoring only) for each instance and monitor/unmonitor configurations for each service.
Notification Settings
You can set rules for email notification when an event occurs.
Account Information
You can check the user's AWS account ID and IAM role name, as well as the plan you are using.
Coati Status
Coati’s status (active or not) is displayed here. If it shows “Active,” the target instances are properly monitored.
“Start/Stop Coati” button
A button to switch start/stop Coati's monitoring.
AWS Account ID
AWS account ID information to be monitored by Coati.
"Resources Discovery" button
By clicking this button, Coati loads the latest EC2 instance status from the AWS management console.
Dashboard: Main menu
Details of the information on the main menu of the dashboard are described below.
1.Status
At the top of the screen, information on the monitored instances, the total number of instances, and uptime of the current month are displayed. This information is always displayed on the screens other than the dashboard.
- Monitoring Instances
The total number of EC2 instances that Coati currently monitors. - Instances
The total number of EC2 instances discovered by Coati, including those being monitored and those not being monitored. This number includes the instances for which user disabled monitoring or those not subject to monitoring because they are out of scope of Coati’s support. - Month Uptime
The total number of hours of monitoring by Coati. For example, if 10 instances are monitored for 10 hours, 10 units*10 hours = 100 will be displayed.
Even when the number of instances increases or decreases due to user operations or Auto Scaling function etc., Coati periodically accesses the AWS Management Console to obtain the latest information. This update to the latest information is performed every 30 minutes.
If you want Coati to reflect the change immediately when a user changes the number of instances, please click the “Detect Resource” button described above.
2.Event history
- Time(UTC)
- Date and time when the event occurred.
- Event
- A type of the event: The event type is currently only recovery.
- Status
- SUCCEED: Coati recovered the service successfully.
- FAILED: Coati failed to recover the service from failure
- IN PROGRESS: Coati is recovering the service.
- EXECUTED: Recovery processing was executed from API.
- Instance
- Instance ID where the event occurred.
- Region
- A region to which the instance where the event occurred belongs.
- Tag
- Information on the tags attached to the instance where the event occurred.
- Service name
- The name of the service that detected the problem.
3.Notification settings
This screen shows on which timing Coati is set to send notification emails at the time of detecting failure or a recovery event. You can change these settings from “Notification settings” screen.
Instances Management
On this screen, detailed information on the EC2 instance recognized by Coati is displayed. You can see which instance is being monitored by Coati, or make sure that the instance you want to monitor is being monitored.
MONITORED INSTANCES
- A list of the instances that have currently been monitored by Coati is displayed.
UNMONITORED INSTANCES
A list of the instances that are set to be unmonitored by users is displayed.
ALL INSTANCES
A list of all the instances is displayed. The following instances are not included in this tab:
- Failed to recover from failure
- OS is not supported by Coati
- SSM is not installed
The description of each column is as follows.
Status
Displays the latest status of instance monitoring: either of “monitoring”, “monitoring stopped”, “unsupported OS”, “SSM unavailable”, “recovery failed”, or “others” is displayed.
Monitoring Settings
Displays the monitoring settings for the instances. Displayed as "Monitored" for those with normal monitoring settings, "Unmonitored" for those you set as unmonitored, and "N/A" for those that cannot be monitored for any reason.
- Monitoring
- Coati is monitoring correctly.
- Monitoring Stopped
- Coati stops monitoring. The monitoring restarts when monitoring setting is on.
- Unsupported OS
- Coati does not support the OS of the instance.
- SSM Not Available
- Coati cannot connect to the instance with SSM.
- Unsupported OS
- Coati stops monitoring. The monitoring restarts when monitoring setting is on.
- Recovery Failed
- The instance has not been monitored because recovery failed.
- N/A
- It does not fall under any of the above. Please contact the help desk.
Instance
Resource ID and Name tag of the instance are displayed.
Region
Indicates in which region the instance is running.
Tag
Display tags attached to each instance.
AWS Console
A link to the AWS console for the target instances.
Advanced Setting
A link to the advanced monitoring settings screen.
Monitoring Settings
Individual settings for monitoring targets
You can make advanced settings for instance monitoring here.
- Set behavior for newly detected instances
- Sets whether or not Coati starts monitoring for the instance automatically when Coati detects a new instance. By default, it is set to "Do not monitor."
To change the setting, please set either "Monitor" or "Do not monitor" from the list displayed after pushing "Behavior for newly detected instances" button and save it.
- Sets whether or not Coati starts monitoring for the instance automatically when Coati detects a new instance. By default, it is set to "Do not monitor."
- Set "Monitoring only, no recovery" all at once
- Coati automatically performs monitoring and recovery in the standard settings, but if only automatic monitoring for all instances is necessary and recovery is not required (administrator's manual recovery is required), checking this box enables you to make the "monitoring only" setting to all instances.
"Status", "Monitoring, "Instances", "Region" in each column are not described here because they are same as those on "Instance Management" screen.
- Check box “Check”
- A check box to set whether to monitor. If this isn’t checked, failure monitoring of the target instances will not be performed.
- “Recovery” List
- Default
- Disable
- Restart Only Services
- Restart Only Instances
- Service settings
- This opens a screen to select monitoring target services for each instance.
- You can also set with the "COATI=DISABLE" tag which was supported in the previous Coati. The instances to which this tag is attached are excluded from Coati’s monitoring. It takes up to 30 minutes for this setting to take effect. In order to reflect it immediately, please click "Detect Resource" button.
Service Settings
This is a screen for selecting the services to monitor for each instance.
The columns "Status", "Monitoring Settings", "instance", "Region", "Tag", "AWS Console" are the same as those on the "Instance Management" screen. You can select the services to monitor in the instance displayed here.
"Service name" on the screen is a list of services to monitor that Coati detected. The above screen is an example of Linux environment. A list of all monitored services is displayed in the same way for Windows as well.
You can exclude the services from monitoring target by unchecking the box of which you do not want to monitor.
When the monitoring settings of the instances and the services are completed, click "Save" at the bottom of the screen. The saved settings will be reflected from the next monitoring.
If "This service can not be monitored because it is restricted by Coati" is displayed under the service name, restarting the service by Coati may affect customer's environment, so it is restricted not to be monitored by Coati.
This message is displayed for the following reasons.
- The service is necessary for monitoring of Coati. If it is stopped Coati will not work properly.
- The service is a system service of OS. If it is rebooted in the usual way it will have some impact on the OS such as being unable to log in.
Account Information
You can view/change the account information from Account Information Screen. You can also upgrade to the Standard plan or unsubscribe Coati from this screen. After subscribing the Standard plan, you can access our Support for inquiries from here.
AWS Account ID
AWS Account ID which you are using for Coati.
IAM Role Name
IAM role name which you provided when registering.
You can change it from "Update IAM Role" button. For details, see "Create and enter AWS account ID and IAM Role name"
Email address
An email address you use to login to Coati. You can change it from "Update email address" button.
Plan Name
Your current Coati plan. If you use a free plan, you can upgrade by pressing "Change plan" button.
Change your email address
Change your email address which you use to login to Coati. After clicking the button, please enter new email address according to the prompted screen. After new email address is set, a verification code is sent to the new email address, and the verification code input dialog will be displayed when you access the account information screen. Please enter the verification code according described in the email. *If your email address is not verified, you will not be able to reset your password. Please be sure to enter the code.
Change your IAM Role
You can change IAM role name used by Coati. For details, see "Create and enter AWS account ID and IAM Role name"
Change your password
You can change login password to login to Coati.
Payment Information(Standard Plan only)
For Standard Plan users, the payment information registered when joining Standard plan is displayed here.
Update your credit card(Standard Plan only)
You can change a credit card that Coati makes a claim.
Update payment information(Standard Plan only)
You can change your payment information registered in Coati.
Payment History(Standard Plan only)
Your payment history is displayed.
Request for support(Standard Plan only)
You can contact Coati support desk. For details, refer to the "Support" chapter.
Cancel Membership
You can cancel your Coati membership.
Notification Settings
The notification setting screen allows you to set whether to receive notification emails at the time of Coati’s events: failure detected, recovery succeeded and recovery failed.
Notification Timing
- When detecting failure
- Send an email when detecting failure.
- When recovery succeeded
- Send an email to the designated address when recovery from the detected failure succeeded.
- When recovery failed
- Send an email to the designated address when recovery from the detected failure failed.
- Since notification of recovery failure is very important, it should not be disabled.
- When the status of the monitoring instance changes to "SSM Not Available"
- If it detects that the SSM agent of the monitoring instance can not be used, it will send an email to the designated addresses.
- While the status is "SSM Not Available", it does not monitor the corresponding instance. After that, if it becomes possible to use SSM, we will restart monitoring.
- When the status of the monitoring instance changes to "Command Unavailable"
- If it detects that monitoring, recovery and detection commands of Coati can not be executed normally even though SSM is available, it will send an email to the designated addresses.
Failure Report
Coati collects the information on the system and AWS when detecting failure and after the recovery, then creates a report. Users need to specify the S3 bucket for placing the report with this setting. This function will be implemented in the future.
Comments
0 comments
Please sign in to leave a comment.