From 62a4ad66d1281c70fd5225ea619bcd98ae0398c1 Mon Sep 17 00:00:00 2001 From: Yehuda Sadeh Date: Thu, 21 Jun 2012 10:46:55 -0700 Subject: [PATCH] docs: update usage logging info added some text under radosgw, examples under radosgw-admin Signed-off-by: Yehuda Sadeh --- doc/man/8/radosgw-admin.rst | 17 +++++++++++++++-- doc/man/8/radosgw.rst | 8 ++++---- 2 files changed, 19 insertions(+), 6 deletions(-) diff --git a/doc/man/8/radosgw-admin.rst b/doc/man/8/radosgw-admin.rst index 78a14fc121f3f..d4d45c07b3105 100644 --- a/doc/man/8/radosgw-admin.rst +++ b/doc/man/8/radosgw-admin.rst @@ -141,9 +141,22 @@ Remove a bucket:: $ radosgw-admin bucket unlink --bucket=foo -Show the logs of a bucket from April 1st 2011:: +Show the logs of a bucket from April 1st, 2012:: - $ radosgw-admin log show --bucket=foo --date=2011=04-01 + $ radosgw-admin log show --bucket=foo --date=2012=04-01 + +Show usage information for user from March 1st to April 1st, 2012:: + + $ radosgw-admin usage show --uid=johnny \ + --start-date=2012-03-01 --end-date=2012-04-01 + +Show only summary of usage information for all users:: + + $ radosgw-admin usage show --show-log-entries=false + +Trim usage information for user until March 1st, 2012:: + + $ radosgw-admin usage trim --uid=johnny --end-date=2012-04-01 Availability ============ diff --git a/doc/man/8/radosgw.rst b/doc/man/8/radosgw.rst index 66ab2fc4a15b5..3adf471c7e452 100644 --- a/doc/man/8/radosgw.rst +++ b/doc/man/8/radosgw.rst @@ -104,11 +104,11 @@ The **radosgw** maintains an asynchronous usage log. It accumulates statistics about user operations and flushes it periodically. The logs can be accessed and managed through **radosgw-admin**. -The information that is being logged contains total data transfr, +The information that is being logged contains total data transfer, total operations, and total successful operations. The data is being -accounted under the bucket owner, unless the operation was done on -the service (e.g., when listing a bucket) in which case it is -accounted under the operating user. +accounted in an hourly resolution under the bucket owner, unless the +operation was done on the service (e.g., when listing a bucket) in +which case it is accounted under the operating user. Following is an example configuration:: -- 2.39.5