Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1886965

Summary:	[DOCS] Need to document configuring log to file and logrotate
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Mike Hackett <mhackett>
Component:	Documentation	Assignee:	Ranjini M N <rmandyam>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vasishta <vashastr>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	agunn, hyelloji, kdreyer, mamccoma, rmandyam, vashastr, vereddy
Target Milestone:	---
Target Release:	4.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-16 13:40:47 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1966534

Description Mike Hackett 2020-10-09 20:27:12 UTC

Describe the issue:

In 4.1 we can configure containerized clusters to log to a file. We need to docuemnt how to do this as well as configure logrotate on this file in 4.1z2.

Describe the task you were trying to accomplish:
Log a containerized daemon to a file and logrotate that file.

Suggestions for improvement:
We need to add this right after chapter 2.7 in the Administration Guide.

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/administration_guide/index#viewing-log-files-of-ceph-daemons-that-run-in-containers_admin

Chapter/Section Number and Title:
2.7 Viewing log files of Ceph daemons that run in containers

Product Version:
RHCS 4.1

Environment Details:

Any other versions of this document that also needs this update:
n/a

Additional information:

Comment 1 Mike Hackett 2020-10-09 21:13:36 UTC

*** Bug 1886518 has been marked as a duplicate of this bug. ***