Dashboard

Feature: Dashboards

Dashboards are the place that users can get an overview of their resources and see pertinent information. A dashboard consists of a number of widgets, users can add and remove widgets to their dashboard.
Users can have more than one dashboard, they can add and remove dashboards.
They are customisable in terms of what widgets are displayed and where. Most widgets also have customisable content and titles.
Users can choose which dashboard is their “default” when they open the application.

Maxims

There is no maximum number of widgets on a dashboard or number of dashboards a user can create or share.

Feature: Sharing

A dashboard can be configured to be shared to other users who are part of the customer, sharing with a user is an explicit operation to a particular user - the target user can then choose to accept that dashboard or not.
When a user accesses a dashboard they have to have permission to view all data in the dashboard or “permission denied” will be returned for the data set they don’t have access to see.

Feature: Widgets

No.

Name Details
1 Server List
A list of server resources.
  • Provider
  • Instance name
  • Instance state
  • Number of CPU Cores
  • Memory Size
  • Local Storage Size
Widget contents should be filterable.
2

Network List (roadmap)

A list of network/subnet resources. The following columns will be displayed:
  • Provider
  • Instance name
  • Subnet
Widget contents should be filterable.
3 Storage List
A list of storage resources.
  • Provider
  • Instance name
  • Storage Size
Widget contents should be filterable.
4

Compute Pool List (roadmap)

A list of compute pools.
  • Provider
  • Instance name
  • Number of CPUs
  • Memory Size
  • Storage Size
Widget contents should be filterable.
5

Network Appliance List (roadmap)

A list of network appliances.
  • Provider
  • Instance name
  • A list of network appliances.

Widget contents should be filterable.
6

Type of Network Appliance

A breakdown of storage by provider accounts - also shows the total storage.
Widget contents should be filterable.
7 Application overview
The application show the following information about an application.
  • Application Name
  • Total CPU Cores
  • Total Memory
The application shown would be picked by the user on widget creation.
8 Heat Map
Shows a heat map for with each square showing the status of a resource. Status is the status reported by the Cloud Provider.
Widget contents should be filterable.
9

Heat Map (CPU Utilisation) (roadmap)

Shows a heat map for with each square showing the CPU% of a resource.
Widget contents should be filterable.
10 Performance graph

Shows a graph based on a predefined graph definition (built in the performance wizard)

11 Spend last 12 months

A column chart of the last 12 months spend for a department, application or account.

12 Spend month to-date

A column chart of the last month to-date spend for a department, application or account.

13 Map
Map showing where resources are, resources can be grouped by:
  • Data Center
  • City
  • State
  • Country
  • Region
User can decide what area to view on the map e.g. World, Europe, Japan. The widget indicates how many resources are in each location. User can filter what resource are shown.
14

Server Details (roadmap)

Shows the details of a particular server including:
  • Name
  • Provider
  • Status
  • CPU Cores
  • Memory
  • Key Performance Metric
The user can select which server to show the details for and what metric is the “key metric”.
15

Log View (roadmap)

Shows the results of a pre-defined query against the logging system, the following information can be seen for each event
  • Timestamp
  • Log Level
  • Summary