webcompat / webcompat-metrics-server

Server in charge of delivering different data to the webcompat-metrics-client
Mozilla Public License 2.0
6 stars 5 forks source link

Adds a script for just generating logs to see if the scheduler is working #66

Closed karlcow closed 5 years ago

karlcow commented 6 years ago

Let's try to deploy a script on staging and check the logs.

karlcow commented 6 years ago

So I deployed this on staging to check how the scheduler is working https://github.com/webcompat/webcompat-metrics-server/blob/866114a21b3e1140a64e2ed47d8acc3fab99cfb3/bin/job_diagnosis.py

And it worked…

2018-11-07T07:44:13.377530+00:00 app[api]: Starting process with command `python bin/job_diagnosis.py` by user scheduler@addons.heroku.com

2018-11-07T07:44:18.318112+00:00 heroku[scheduler.2717]: Starting process with command `python bin/job_diagnosis.py`

2018-11-07T07:44:19.038993+00:00 heroku[scheduler.2717]: State changed from starting to up

2018-11-07T07:44:22.093852+00:00 heroku[scheduler.2717]: State changed from up to complete

2018-11-07T07:44:22.080683+00:00 heroku[scheduler.2717]: Process exited with status 0

2018-11-07T07:44:21.971712+00:00 app[scheduler.2717]: 2018-11-07T07:44:20Z 168
karlcow commented 6 years ago

I will let it run for now only on a daily basis. Then next steps will be to populate the DB.

karlcow commented 5 years ago

This is has been solved in #64