Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indicators should print their name and version information on start #1702

Closed
krivard opened this issue Sep 28, 2022 · 1 comment · Fixed by #1736
Closed

Indicators should print their name and version information on start #1702

krivard opened this issue Sep 28, 2022 · 1 comment · Fixed by #1736
Assignees
Labels
enhancement refactor Long-term projects to revise existing machinery

Comments

@krivard
Copy link
Contributor

krivard commented Sep 28, 2022

One of the common failure modes of our production system is "hey, this widget was supposed to have been updated, but seems to be running old code". To help make this problem easier & quicker to diagnose, we should modify each indicator so that when it starts up, it prints its name and some kind of version information.

Version information could be:

  • repo version (this is available in .bumpversion.cfg but probably doesn't survive our deployment mechanism)
  • indicator version (which we currently don't track, but maybe we should? it would probably live in setup.py (claims_hosp example))
  • gitref (not visible in deployed code but we could make jenkins write it down)
  • build date (another thing jenkins would have to do)
@krivard
Copy link
Contributor Author

krivard commented Nov 11, 2022

Assigning Mitch to this -- work with @korlaxxalrok to figure out how to store/deploy versioning information with Jenkins, then go through each indicator and add a log line at the start of run_module.

  • usafacts
  • jhu
  • dsew_community_profile
  • google_symptoms - will need auth keys to run locally (ask Luke)
  • hhs_hosp
  • nchs_mortality
  • quidel_covidtest - will need auth keys

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement refactor Long-term projects to revise existing machinery
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants