Check API PRD server log and AWS monitoring stats

[logstar]

API PRD server was lagging for load time, which might need to be optimized at load balancing, according to @taylordm .

The lagging might be caused by high request rates, after MTP portal https://moleculartargets.ccdi.cancer.gov/ was publicly released, as MTP portal sends HTTP requests to API PRD server to get plots, according to @chinwallaa .

@chinwallaa suggested to check the usage stats of API PRD server, which can be estimated using API DEV server log.

@brianghig suggested to check the AWS monitoring stats to see whether the API PRD server is hitting limits on CPU, RAM, or Disk I/O.

I will check server log and AWS monitoring stats according to the suggestions of @chinwallaa and @brianghig .

cc @blackdenc

[chinwallaa]

FNL have a sandbox MTP portal [https://ppdc-otp-qa.bento-tools.org/]
and a production release: MTP portal [https://moleculartargets.ccdi.cancer.gov/]

• I believe both are leveraging our API prod server (AWS). We can check our API logs to confirm.

• FNL have plans to migrate our API stack to their own VPC. Not sure on their timeline for migration/implementation

Would be useful to see usage from their prod instance vs their sandbox instance - to help us determine and config steady state load/response