openstack/openstack-manuals
Code Issues Proposed changes
29d54dc0f6
openstack-manuals/doc/admin-guide-cloud/source/dashboard_view_cloud_resources.rst
Bernd Bausch 34ea37e470 Setting up Administrator Guide Dashboard Chapter, part 2 
Introducing Admin User Guide dashboard content to
the Cloud Admin Guide as a part of the reorganisation
goal. This patch is the second step in creating a new
Dashboard section for Admin Users in the Cloud Admin Guide,
as discussed in the User Guide Specialty team meetings.

First step: https://review.openstack.org/281635

Chapters copied:

   dashboard_manage_resources.rst
   dashboard_manage_services.rst
   dashboard_manage_volumes.rst
   dashboard_set_quotas.rst
   dashboard_view_cloud_resources.rst
   dashboard_admin_manage_roles.rst

dashboard.rst TOC updated.

Change-Id: Idc8a900d3a8b7396e884764d7962a0a8991948ac
Implements: blueprint user-guides-reorganised
2016-02-22 15:50:25 +09:00

1.5 KiB
Raw Blame History

View cloud usage statistics

The Telemetry service provides user-level usage data for OpenStack-based clouds, which can be used for customer billing, system monitoring, or alerts. Data can be collected by notifications sent by existing OpenStack components (for example, usage events emitted from Compute) or by polling the infrastructure (for example, libvirt).

Note

You can only view metering statistics on the dashboard (available only to administrators). The Telemetry service must be set up and administered through the ceilometer command-line interface (CLI).

For basic administration information, refer to the "Measure Cloud Resources" chapter in the OpenStack End User Guide.

View resource statistics

  1. Log in to the OpenStack dashboard as a user with Admin privileges.
  2. On the Admin tab, click the Resource Usage category.
  3. Click the:
    • Usage Report tab to view a usage report per tenant (project) by specifying the time period (or even use a calendar to define a date range).
    • Stats tab to view a multi-series line chart with user-defined meters. You group by project, define the value type (min, max, avg, or sum), and specify the time period (or even use a calendar to define a date range).