The 6.4 beta1 console log view doesn't allow you to page through the full servers log, nor does it allow you to see the tail end of the server.log for the current messages.

What are the exact expectations for the log viewer? The log viewer which ships with EAP 6.4.0.Beta1 shows the complete log file in a read-only view inside the console. Thus paging through the log file would mean scrolling up and down. To see the tail of the log file you'd need to scroll to the end of the log file. Additionally you can download the log file and view it offline in an external editor. Does that match your use cases? 

The version I used for testing (you can obtain the version information by clicking on the version number in the lower left corner in the console):

- EAP 6.4.0.Beta1
- Console 2.5.2.Final-redhat-1

This is not working correctly.  When I compare what I see in the console view vs what is in the server.log the console does not show everything.  It does not even show the tail of the log.

This is the same case in WFLY 8.2.

Please note that the log viewer in the console shows a snapshot of the log file taken at the moment the log file is opened. 

Furthermore the log viewer provides slightly different features in EAP 6.4 and WildFly 8.2:

1. EAP 6.4 (and the upcoming WildFly 9.0) 
This version uses a newer set of management operations which opens the complete log file in the log viewer. You can easily navigate and search in the log file. However please note that the log is not refreshed automatically. Hence the log file is just a snapshot. 

2. WildFly 8.2 
This version uses an older version of the log viewer which shows only a portion of the log file. The navigation through the log file is more complicated (you cannot scroll using the mouse). However this version includes the feature to follow the last n lines of the log file. 

We think the log viewer should give you a complete view of the log file. It should be easy for the user to navigate through the log file. That's the reason we switched the implementation for EAP 6.4 / WildFly 9.

I hope the features you see in the console match my descriptions. If not, please describe the problem and specify the name and version of the product / console.

I don't know any other way to explain this.  But you really need to look at it because it does not work the way you say!!!

The logviewer in EAP 6.4 or HAL2.5.2 whatever you want to call it, does not allow you to see/page through the log file.  It only shows a portion, so to me it is of no use.  What is the point if you can only see a portion and not look thought the log.  It doesn't even show the tail of the log.  Its definitely not prime time.

I suggest that you provide screenshots and version information. A more detailed error report other than "it doesn't work" would help as well. Can you please provide details about your environment: standalone / domain mode, OS and browser version.

Is this still relevant?

I see what the issue is.  The log viewer is looking at jboss.server.log.dir.  We are writing our server.log to a custom area defined in the host-slave.xml file.  below is how we have this defined in the host-slave.xml.

 <paths>
      <path name="custom.jboss.server.log.dir" path="/apps/logs/server1"/>
 </paths>

This is then referenced in the domain.xml as:

<file relative-to="custom.jboss.server.log.dir" path="server.log"/>

I suppose there's no way to get the log viewer to look at custom.jboss.server.log.dir instead of jboss.server.log.dir?

Yes that's true. The management operation we're using allows only to look at log files under jboss.server.log.dir. 

From the description of the list-log-files operations:
--------------------
[domain@localhost:9990 /] /host=master/server=server-one/subsystem=logging:read-operation-description(name=list-log-files)
{
    "outcome" => "success",
    "result" => {
        "operation-name" => "list-log-files",
        "description" => "Lists the log files in the jboss.server.log.dir directory that are defined on a file-handler, periodic-rotating-file-handler or size-rotating-file-handler.",
...
--------------------

Since the log viewer does work correctly regarding the limitations given by the management operations, I'd like to close this issue. Do you have any objections against closing this?

Could I submit a request to have this customizable?  Other that that, you can close this.

Thanks.

Sure. I recommend to file a separate issue using the logging component and referencing this issue.