fixing cron schedule. remove unnecessary log files (collector process is redirecting stdout & stderr to pid1 stdout/stderr).

pull/162/head
Jason Kulatunga 4 years ago
parent 011642a708
commit c55bdcbf28

@ -1,3 +1,4 @@
MAILTO=""
# Example of job definition: # Example of job definition:
# .---------------- minute (0 - 59) # .---------------- minute (0 - 59)
# | .------------- hour (0 - 23) # | .------------- hour (0 - 23)
@ -7,9 +8,8 @@
# | | | | | # | | | | |
# * * * * * user-name command to be executed # * * * * * user-name command to be executed
# TODO: correctly route collector logs (STDOUT & STDERR), print to Cron foreground (collectable by Docker STDOUT?) # correctly route collector logs (STDOUT & STDERR) to Cron foreground (collectable by Docker STDOUT)
# TODO: change cron schedule to daily at midnight: '0 0 0 * * *' # cron schedule to run daily at midnight: '0 0 * * *'
# System environmental variables are stripped by cron, source our dump of the docker environmental variables before each command # System environmental variables are stripped by cron, source our dump of the docker environmental variables before each command (/env.sh)
* * * * * root . /env.sh; /scrutiny/bin/scrutiny-collector-metrics run >> /var/log/scrutiny.log 2>&1 0 0 * * * root . /env.sh; /scrutiny/bin/scrutiny-collector-metrics run >/proc/1/fd/1 2>/proc/1/fd/2
* * * * * root date >> /var/log/cron.log
# An empty line is required at the end of this file for a valid cron file. # An empty line is required at the end of this file for a valid cron file.

Loading…
Cancel
Save