The Dashboard gives you a high level overview of all activity in your account. This is sometimes referred to as the homepage. It is divided up by the following tabs:
The Overview tab contains three pieces of information:
RightScale News - Brief news bulletins from RightScale such as information pertaining to an upcoming release, scheduled maintenance reminders, recent press releases, or reminders of upcoming webinars. If there are any new messages, they will be displayed first under the Overview tab.
Deployments Budget Estimate - For each deployment you can see the number of active/inactive servers, current hourly and daily run rate, and a 14-day average. There are also totals for all deployments for the estimated run rate and 14-day average at the tail end of the display. Important! - These figures are estimates only.
Cloud Service Credential Validity - Icons are now used to denote a credential's validity for each cloud and/or cloud service.
- indicates valid credentials for a cloud/service.
- indicates invalid credentials.
- indicates credentials for new services that have not been activated.
Until you have established valid credentials, you will continue to be presented with the "Enter your credentials" dialog box each time you log in. If all credentials are valid, they are displayed at the end of the Overview tab display. If any cloud credentials (AWS, GoGrid, FlexiScale, etc.) are invalid they will be displayed at the top (above RightScale News). Only the EC2 and S3 credentials are required for AWS to be valid as a whole. Credentials for other services, such as SQS and CloudFront are optional. To activate a new service (i.e. SQS or CloudFront), you must first sign-up for the service with the cloud provider (AWS) and then validate its credentials in the Dashboard. See Upgrade Your Account, Sign-up for AWS, Add AWS Credentials to RightScale, and Sign-up for Additional Cloud Services.
The Deployments tab shows information for instances that have been launched, as well as deployment information. Once your cloud credentials are valid, the Deployments tab will be shown by default when going to the Dashboard's homepage (Home -> Dashboard) or clicking the RightScale logo.
Instances - Active running instances that were launched using a base image, not a ServerTemplate. (Clouds -> "Cloud" -> Images)
Deployments - A list of deployments in the account. Deployments with active, running instances will be listed first. Subsequent deployment will be listed alphabetically. Each icon represents a server in the deployment.
A red square represents an inactive server (stopped)
A green circle represents an active server (booting, operational)
Arrays are bracketed
Server with a warning (possibly stranded)
Click the SSH icon to SSH into the running instance.
Server Arrays - If a deployment has any attached server arrays, they will be listed on the bottom section of the associated deployment.
The Dashboard Monitoring tab allows you to select and view the graphs of any operational server from any deployment. You may view graphical data at the Dashboard level to monitor servers across different deployments at the same time without switching from one page to another.
Other features and characteristics of the Monitoring tab include:
Common Graphs are automatically displayed
By default, if there are currently no graphs saved in the server, deployment, or dashboard monitoring section(s), the most commonly used monitoring graphs will automatically be shown (cpu overview, network interface traffic, apache scoreboard, and/or mysql operations overview).
CPU column with icons
The CPU column is included on the homepage of a deployment. The following icons are used to quickly denote the status of each server. If the monitoring feature is enabled for a running server, a thumbnail of its CPU usage graph will replace the operational icon.
The Alert tab shows detailed information about all of your alerts (specifications). Alerts and Alert Escalations are used to automatically take actions on a deployment on your behalf if certain user-defined conditions are met that trigger an alert. Alerts are commonly used with Server Arrays in order to set up autoscaling.
See Alerts, Alert Escalations, and Server Arrays for more information.
The Alerts section provides a high level overview of the alert conditions of your running servers and displays the most recent alert conditions.
Enabled - The number of alerts (not servers) that are active (enabled) and are currently being monitored. Only the enabled alerts on running servers will be shown. Once an alert is triggered, the associated alert escalation will be called and its actions will be run in sequence.
- A green ball denotes that there are no triggered alert conditions on any of your running servers.
- A red ball denotes a triggered server alert condition. A red ball will be shown for each triggered alert. When an alert is triggered, it will be listed below along with the associated alert escalation that was called, the state of the alert (true=enabled; false=quenched/disabled) and the length of time (min/hour/day) that the same alert condition has been triggered (i.e. the alert condition still exists; the alert escalation's actions have not resolved the alert condition).
- Click the icon, to view an alert's error message. Then click the "Show" link to view more detailed information about each alert that is triggered.
- In the example above, there are 63 alerts that are enabled across all of the servers in your account. Currently, there are 2 alerts that have been triggered. Remember, since each server can have multiple alerts, there could be one server with 3 alerts or there could 3 servers with the same alert.
Quenched - The number of alerts on running instances that have been temporarily quenched (disabled) (i.e. 1hr off, 24hr off).
Inactive - The number of alerts on running instances that have been turned off (disabled).
You also have the ability to change the state of the alert(s). See Changing the State of Alerts.
The Alerts section displays the alerts that have been recently triggered. You can also change the state of the alert on a running server if you want to prevent a triggered alert from calling an alert escalation by quenching the alert (1hr off / 24hr off) or disabling it by making it inactive. See Change the State of Alerts.
Click on the Alert Spec name (e.g. cpu idle) to view more detailed information about where the alert is being triggered including the name of the server, its deployment, the specifications of the alert, etc.