Closed xhernandez closed 1 year ago
From what I see in the code, there is no specific filtering on job being done. So not sure where to add anything.
Based on the readme.md
from the repo:
python manage.py db upgrade
python manage.py runserver
DEBUG=True
to it to enable debug mode for your flask app.python manage.py proccess_jobs -n <number_of_days> -j <job_name>
So the application itself is not collecting the data, but some task should be running periodically to collect data from the selected jobs using the manage.py
script. Isn't there any cron job or similar that triggers a set of those commands ?
We have that:
So indeed, that's done outside of code, and outside of a config file.
So, adding 2 jobs, ok, but which one should we remove ?
We have that:
So indeed, that's done outside of code, and outside of a config file.
I did miss that part. Thanks for pointing it out.
So, adding 2 jobs, ok, but which one should we remove ?
It seems that the list already contains only the active jobs. Probably the old jobs I saw in fstat are there just because we have old data in the DB. That's fine. There's no need to remove any job IMO.
ok, so as I added 2 more jobs, I can close that bug, but as usual, feel free to reopen it if I misunderstood.
I think we should add
centos8-s390-regression
andgh-regression-on-demand-full-run
to the jobs monitored for failures in fstat.gluster.org. Probably it would also be better to remove old jobs not used any more (even from Jenkins).