Page Comparison

...

1. Check that services are up and running

   1. Confirm Mozart, Tosca, and ARIA Products pages are all accessible.

   2. Confirm jobs are being processed by reviewing the job status in Mozart and the queue status in RabbitMQ

   3. Confirm there are no stale queues in RabbitMQ or stale jobs in Mozart.

2. Review Slack alert messages

   1. Resolve the alerts defined in the messages.

3. Review failed jobs

   1. Investigate cause of failure. Resolve if possible, or contact relevant PGE developer for assistance.

4. Generate product accountability reports

   1. Generate the AOI reports over the recently-processed AOI’s to assess status of processing campaigns .and update the AOI Processing Plan

5. Reporting

   1. Notify customers of processing updates

   2. Update any appropriate Jira tickets

6. Review AWS

   1. Ensure there are no runaway EC2 instances in ASG

      1. terminate stale EC2 instances

   2. Verify that the AWS Billing Daily Cost View is at expected levels

   3. update the Cost AWS In tab in the AOI Processing Plan with newest costs

Weekly Items

1. Review and update AOI Processing Plan

   1. update with customers per AOI of possible cleanup of unneeded SLC and other intermediate files (e.g. S1-SLCP, S1-COD, S1-LAR, S1-DPM)

2. Reduce storage costs by purging SLCs data from AWS S3 and on Pleiades

   1. Assess AOIs that are end-dating soon

   2. Purge SLS SLC in AOI’s region (SLCs in both AWS S3 and on Pleiades)

   3. Purge intermediate datasets S1-SLCP, S1-COD, S1-LAR for no longer needed urgent response areas. (mostly in AWS S3)

3. Clean up trigger rules in Tosca

   1. check stakeholders for their AOI relevant trigger rules

   2. Delete any trigger rules for AOIs that have finished

   3. Deactivate trigger rules if you want to reference parameters in the future