| Author |
Message
|
| pandeg |
 Posted: Fri Sep 30, 2016 4:11 am Post subject: tail application specific log in SysOut.log file |
 |
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| Hi, We have Application server where multiple application/interface logs are rolling at the same time. In Application Server SysOut.log file, all these different application logs are shown as mixed logs and it is difficult to monitor them. Is there a way to tail application specific logs in Windows using python or batch scripting without affecting the SysOut.log file |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Sep 30, 2016 4:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You could probably use splunk or similar to extract application specific information from the main log into application specific logs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pandeg |
| Posted: Fri Sep 30, 2016 5:58 am Post subject: |
|
|
Disciple
Joined: 21 Oct 2014
Posts: 195
|
| Vitor wrote: |
| You could probably use splunk or similar to extract application specific information from the main log into application specific logs. |
Thanks Vitor, but do you think that Application Developers should log these application specific messsage in separate application.log file instead of throwing in SystemOut.log. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 30, 2016 6:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
They should log them somewhere other than files... like a database. then you don't have to tail them or etc.
If they're using java.log or whatever it is, then you can change the config without them caring.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 30, 2016 6:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pandeg wrote: |
| Vitor wrote: |
| You could probably use splunk or similar to extract application specific information from the main log into application specific logs. |
Thanks Vitor, but do you think that Application Developers should log these application specific messsage in separate application.log file instead of throwing in SystemOut.log. |
Personally? I think they should use separate logs, using the kind of configuration my most worthy associate mentions.
I'm not a WAS person, I'm by no means a Java person and when I've expressed that opinion I've been shouted down by people who are on most sites I've worked on. Objections have been (but are not limited to):
- "adding extra log configuration is another configuration to go wrong"
- "the system log is the recommended place for errors"
- "separate logs add overhead"
- "using application logs is anti-pattern for Java"
I've assumed for the last few years that these are synonyms for "system log is easy and we can't be bothered to do anything else", and set up splunk or it's more sophisticated cousins to scrape the system logs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
