Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1363907 - allow crm_mon option to specify what sections to display
Summary: allow crm_mon option to specify what sections to display
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: pre-dev-freeze
: 8.1
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-03 22:23 UTC by Ken Gaillot
Modified: 2019-03-28 20:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1361533
Environment:
Last Closed:
Type: Feature Request


Attachments (Terms of Use)

Description Ken Gaillot 2016-08-03 22:23:20 UTC
+++ This bug was initially created as a clone of Bug #1361533 +++

--- Additional comment from Tomas Jelinek on 2016-08-03 07:09:39 EDT ---

(In reply to Ken Gaillot from comment #3)
> I'll try to fix the header issue for 7.3, but understand that the console
> output changes from one pacemaker version to another, so it can't be relied
> on in the long term.
> 
> Is your goal to display only certain sections of the crm_mon output? For
> example, just the resources, or just the resources and the failcounts. If

yes

> that's the case, I have an idea for an enhancement that could make it into
> 7.4. We could add an --include option to crm_mon that would take a
> comma-separated list of sections you want to display. E.g. "crm_mon
> --include resources,failcounts". Would that be sufficient?

That would be great!

Comment 2 Ken Gaillot 2017-03-15 17:25:06 UTC
Unfortunately, due to capacity constraints, this will not be ready for 7.4. It will be a priority for 7.5.

Comment 3 Ken Gaillot 2017-08-29 21:18:05 UTC
Due to a short time frame and limited capacity, this will not make 7.5.

Comment 4 Ken Gaillot 2019-01-15 17:32:45 UTC
Bumping to 8.1 due to devel/QA capacity constraints


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