search

Chemical-Curation / chemcurator_django

Backend services for chemical curation
https://api.chemreg.epa.gov
MIT License
1 stars 0 forks source link

error message on resolver api problems #287

Open cmgrulke opened 3 years ago

cmgrulke commented 3 years ago

As a curator I want crud api to not error when the resolver is not available and instead inform some IT person to fix it So that I am not worried that the data isn't stored properly in the CRUD database

A curator doesn't understand the error message returned from the django API when there is a problem with the resolver api accepting the new data for indexing. The message really doesn't indicate the need for the user to do anything, only that someone (not the curator) needs to check why the Resolver API is not accepting data that is deemed acceptable by the CRUD API and perform a sync/reindexing.

Acceptance Criteria: If the resolver is failing to receive indexing data, the user does not receive an error message as they need a created response if the data is stored in the CRUD database If the resolver is failing to receive indexing data, someone is notified in IT to investigate the error (email to ccte_sa@epa.gov?)

Add Health Check (Docker feature) in each docker container. Documentation can be found to know about this Health Check.

jtumkur commented 3 years ago

Post the substance to django. If substance is stored - error message for internal sever error. Your substance is good. And then problem is having on the Resolver api is not there. Store the transactions and run the Sync command. More information from Dave to follow. Put the Health Check on Resolver. If Health check on all containers would be good start for getting alert.

michael-barbour commented 3 years ago

This is the docker-compose file from the wiki.

https://github.com/Chemical-Curation/chemcurator_django/wiki/Deploying-with-Docker#docker-composeyaml