@rochacbruno Currently everything is logged in /var/log/messages. When I see the frequency we are running we will utilize too much disk size, We will have to write log rotate or log cleaner for this.
@rochacbruno do you know any way we can process all log from /var/log/message to something like /var/log/jirasync.log from restarting process itself?
(env) [root@okhatavk jirasync]# tail -f /var/log/messages
Aug 8 12:41:33 okhatavk jirasync: Connecting to jira at http://localhost:8080
Aug 8 12:41:33 okhatavk jirasync: Using basic authentication
Aug 8 12:41:33 okhatavk jirasync: Searching Jira for pr_create#robottelo#7251 using query [project = 10000 AND summary ~ \"pr_create\u0023robottelo\u00237251\"]
@rochacbruno Currently everything is logged in /var/log/messages. When I see the frequency we are running we will utilize too much disk size, We will have to write log rotate or log cleaner for this.
If we use Monit https://mmonit.com/wiki/Monit/ConfigurationExamples#system, we will solve this problem, either we can logrotate or clean file. We would also generate alert for us in case of any issues.
@rochacbruno do you know any way we can process all log from /var/log/message to something like /var/log/jirasync.log from restarting process itself?
(env) [root@okhatavk jirasync]# tail -f /var/log/messages Aug 8 12:41:33 okhatavk jirasync: Connecting to jira at http://localhost:8080 Aug 8 12:41:33 okhatavk jirasync: Using basic authentication Aug 8 12:41:33 okhatavk jirasync: Searching Jira for pr_create#robottelo#7251 using query [project = 10000 AND summary ~ \"pr_create\u0023robottelo\u00237251\"]