Bug 1297643

Summary:	Specific detail for ceph log and log level.
Product:	Red Hat Ceph Storage	Reporter:	vickie.c <vickie.c>
Component:	Documentation	Assignee:	Aron Gunn <agunn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.3.2	CC:	agunn, asriram, bhubbard, flucifre, hnallurv, kdreyer, ngoswami, smanjara
Target Milestone:	rc	Keywords:	Documentation, ZStream
Target Release:	1.3.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-01 08:23:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description vickie.c 2016-01-12 05:35:17 UTC

Description of problem:
The documents provides how to set and enable log but no detail.
If the log level increase what kind information will record into file？
And what mean of each value in log？


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Enable rbd log into log level 1/5 and set path to /var/log/ceph/rbd.log
2. Create a rbd image from client.
3. Check /var/log/ceph/ on monitor and osd severs.


Actual results:
Can not find any rbd image access information from log.

Expected results:
The log will record image create success(or fail) and some information of client IP image name, logical image size...

Additional info:

Comment 4 Federico Lucifredi 2016-02-12 15:09:18 UTC

Clearly, per Dan's feedback you cannot meet the "value of each" requirement. You will NEVER, EVER, be able to meet that, it is syslog, it is unbound. So let's forget that part. Let's address the rest.

What you should focus on is having a few examples showing what level of detail is provided in the log at different log levels, that's all. It should take you an hour to do if you have a cluster to play with. You can only provide examples at the different log levels — and if there are any other details worth sharing, Dan would know, but let's have the examples at a minimum.


I am leaving this one in this release, let's just wrap it and be done with it so we can close it.

Comment 6 shilpa 2016-02-18 06:31:45 UTC

Doc looks good to me.