Bug 951168 - Filter-spec documentation is missing
Summary: Filter-spec documentation is missing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: EAP 6.1.1
Assignee: Scott Mumford
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-11 14:55 UTC by Petr Kremensky
Modified: 2014-08-14 15:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.8 Build Name: 11865, Administration and Configuration Guide-6-3 Build Date: 11-04-2013 11:39:36
Last Closed: 2013-09-16 20:21:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 982303 0 unspecified CLOSED Unable to use Filter Expressions in filter-spec 2021-02-22 00:41:40 UTC

Internal Links: 982303

Description Petr Kremensky 2013-04-11 14:55:25 UTC
http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6-Beta/html/Administration_and_Configuration_Guide/sect-Logging_Configuration_in_the_CLI.html

Filter-spec documentation is missing at all for Logging. This is replacement for filter which is now deprecated. We should offer few examples to user. 

Also CLI outputs for LOG-HANDLER:read-resource operation should be updated for whole section 12.3. Logging Configuration in the CLI
eg.
 - is:
[standalone@localhost:9999 /] /subsystem=logging/root-logger=ROOT:read-resource                                  
{
   "outcome" => "success",
   "result" => {
      "filter" => {"match" => "names"},
      "handlers" => [
            "CONSOLE",
            "FILE"
      ],
      "level" => "INFO"
   }
}
 - should be:
[standalone@localhost:9999 /] /subsystem=logging/root-logger=ROOT:read-resource
{
    "outcome" => "success",
    "result" => {
        "filter" => undefined,
        "filter-spec" => undefined,
        "handlers" => [
            "CONSOLE",
            "FILE"
        ],
        "level" => "INFO"
    }
}

Comment 3 Petr Kremensky 2013-07-08 15:41:50 UTC
The source of information is valid, but examples provided here are not working for me. 

I created BZ [1] for this. We have to wait for James' opinion.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=982303

Comment 5 Misty Stanley-Jones 2013-08-30 00:29:52 UTC
Not yet added to the book. I've asked Scott to look into this one.

Comment 6 Scott Mumford 2013-08-30 01:35:29 UTC
This topic has been added to the Admin and Config contentspec [19233] (revision 504422).

This bug will be moved to ON_QA once the document has been rebrewed.

Comment 8 Petr Kremensky 2013-09-04 06:29:57 UTC
Can you please modify the columns width for table 13.1.5? I would widen the "Filter Type expression" at the expense of "description" column as now I can see expressions rendered like:

Substitute 
All (substitu
teAll["pa
ttern","r
eplacemen
t 
value"])

which is quite ugly.

Comment 9 Scott Mumford 2013-09-04 22:01:45 UTC
Unfortunately, the column widths are automatically formatted by the build system. There's nothing that can be done about it (as manual column-width settings are ignored).

As long as the content is accurate, this bug should be moved to VERIFIED.

Comment 10 Petr Kremensky 2013-09-05 06:05:10 UTC
Alright than. Moving to Verified.


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