RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1265108 - [DOC] -SBRVirt Request -log documentation needed
Summary: [DOC] -SBRVirt Request -log documentation needed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Virtualization_Deployment_and_Administration_Guide
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Jiri Herrmann
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 07:17 UTC by Laura Novich
Modified: 2019-03-06 01:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-02 15:11:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Laura Novich 2015-09-22 07:17:12 UTC
Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 
Teach customers how to:
How to find the issues within a log or multiple log files
How to set the filter settings properly
How to read a log
How to trace a problem from log to log
var/log/libvirt/qemu/logs - for VM issues from the hypervisor standpoint
many times the timestamp on the log entry for the host and guest match

Additional information: 
Information that really teaches about logs is lacking
Knowing your logs is crucial for proper case resolution
in most cases customers give a description of what happened but there is no data as to when it happened or SOS report.


Note You need to log in before you can comment on or make changes to this bug.