-
1. Re: How to configure wildfly log to log node name
jamezp Mar 28, 2016 5:05 PM (in response to valsaraj007)What do you mean by the node name?
--
James R. Perkins
-
2. Re: How to configure wildfly log to log node name
valsaraj007 Mar 28, 2016 11:35 PM (in response to jamezp)Hi James,
I mean jboss.node.name or any identifier to know the node since we are logging messages from all nodes in single file.
Thanks!
-
3. Re: How to configure wildfly log to log node name
wdfink Mar 29, 2016 7:29 AM (in response to valsaraj007)1 of 1 people found this helpfulI would not recommend to log different server instances to the same logfile. You might have concurrecy issues. You should have a logfile per node/instance and name the logfile with the node name instead of server.log
-
4. Re: How to configure wildfly log to log node name
jamezp Mar 29, 2016 11:57 AM (in response to valsaraj007)1 of 1 people found this helpfulAre you running several standalone servers and logging those into the same file? I'd agree with Wolf that's not advisable. If you're looking for centralized logging a syslog server or the ELK stack is probably best.
--
James R. Perkins
-
5. Re: How to configure wildfly log to log node name
valsaraj007 Mar 29, 2016 11:38 PM (in response to jamezp)I am running in domain node with 2 servers runinning on 2 machines. Each server has 2 nodes ie, 2 nodes per machine. Machine 1 runs master and other machine is slave. On each machine, the logs from 2 nodes are saved to single file called server.log.
-
6. Re: How to configure wildfly log to log node name
jamezp Mar 30, 2016 1:22 PM (in response to valsaraj007)I wouldn't advise having two processes write to the same file. You could end up with log messages mixed around within each other. If you need central logging a syslog server, splunk, ELK stack etc is the way to go.
--
James R. Perkins