Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 672712

Summary: RFE: Complete Monitoring, Error-Reporting Parts of Deployment Guide
Product: Red Hat Enterprise Linux 6 Reporter: Douglas Silas <dhensley>
Component: doc-Deployment_GuideAssignee: Jaromir Hradilek <jhradile>
Status: CLOSED WONTFIX QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: mhideo
Target Milestone: rcKeywords: Documentation, FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://bu-platform.devel.redhat.com/PMRHEL6/rhel6/features/reliability-availability-scalability-ras/fault-analysis/?searchterm=None
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Reason: Result (if any):
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-11 14:25:50 UTC Type: ---
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: 733539    
Bug Blocks:    

Description Douglas Silas 2011-01-25 23:46:03 UTC
This RFE supersedes bug 548254 by presenting a concrete proposal for error-collecting documentation in the RHEL6 Deployment Guide.

CURRENT STATUS

Kernel error collection tools include:

    kdump - [complete]
    netdump - [undocumented]
    diskdump - [undocumented]
    kerneloops - [reporting of is undocumented]

Note: the crash package (also undocumented) utilizes kdump, netdump and diskdump to collect data for analysis.

User-space error collection tools include:

    ABRT - [complete; implementation and documentation ongoing]
    SOS Report - [undocumented]

Related monitoring tools include:

    new kernel 'perf' infrastructure - [undocumented; higher priority than OProfile]
    OProfile - [To be completed for 6.2/3]
    
Original plan for error-reporting framework linked to in the URL.

Comment 3 Jaromir Hradilek 2011-01-26 11:55:51 UTC
*** Bug 548254 has been marked as a duplicate of this bug. ***

Comment 4 Jaromir Hradilek 2011-01-26 12:24:39 UTC
(In reply to comment #0)
> Note: the crash package (also undocumented) utilizes kdump, netdump and
> diskdump to collect data for analysis.

The basic usage of the crash utility is actually covered in The kdump Crash Recovery Service chapter (see Analyzing the Core Dump). Nevertheless, if we decide to document netdump and/or diskdump, this section will need to be reviewed as well.

Comment 7 RHEL Program Management 2014-07-11 14:25:50 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.