JWQL currently has a table on the Dashboard that displays the status of the various monitor runs. This table keys off the log files. If the log indicates success, the entry in the dashboard table is green. If it does not, the entry is red. However, this does not distinguish at all between monitor runs where nothing happens (because there is not enough data) and runs where the full monitor does run.
Emily Wislowski also pointed out that having the status table on e.g. the instrument main pages might make it more visible.
Ideas for an update:
Move the table to the instrument pages. Note that the table would be identical for all instruments though, since the monitors typically loop over instruments during a single run.
Rather than (or in addition to) looking for the "SUCCESS" text in the log files, query the databases for each monitor. Find the most recent date where the monitor ran. But also find the most recent date when the monitor completed all of its analysis and updated the databases.
Point 2 has the added advantage of importing all of the monitor models, which may be helpful in making sure Django sees all of the models and picks up on any changes that will require new migrations.
Issue JWQL-191 was created on JIRA by Bryan Hilbert:
JWQL currently has a table on the Dashboard that displays the status of the various monitor runs. This table keys off the log files. If the log indicates success, the entry in the dashboard table is green. If it does not, the entry is red. However, this does not distinguish at all between monitor runs where nothing happens (because there is not enough data) and runs where the full monitor does run.
Emily Wislowski also pointed out that having the status table on e.g. the instrument main pages might make it more visible.
Ideas for an update:
Move the table to the instrument pages. Note that the table would be identical for all instruments though, since the monitors typically loop over instruments during a single run.
Rather than (or in addition to) looking for the "SUCCESS" text in the log files, query the databases for each monitor. Find the most recent date where the monitor ran. But also find the most recent date when the monitor completed all of its analysis and updated the databases.
Point 2 has the added advantage of importing all of the monitor models, which may be helpful in making sure Django sees all of the models and picks up on any changes that will require new migrations.