Add logging to mdtranslator

[rshewitt]

User Story

In order to provide insight into mdtranslator processing , datagov wants to add formal logging to mdtranslator.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN mdtranslator
  WHEN a log occurs
  THEN it will be present somewhere ( stdout, stderror, written to file, etc... ) \

Background

• mdtranslator doesn't use a formal logging system it just adds messages to some arrays in the final output of the program

[Any helpful contextual notes or links to artifacts/evidence, if needed]

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

[rshewitt]

new relic ruby agent supports up to 3.2.x which means i'll have to downgrade the transformation app ( source )

[rshewitt]

logs in new relic

[rshewitt]

NEW_RELIC_LICENSE_KEY isn't being set by .profile, or at least it's not returned via env in the app, for some reason and yet logs can still be processed for the transformation app ( see picture above ). digging a bit deeper i noticed the same with catalog-fetch. NEW_RELIC_LICENSE_KEY isn't being set. .profile appears to be executing because of this log. where's the license key deriving from if not via NEW_RELIC_LICENSE_KEY in the env? if i ssh into the transformation app and run source .profile NEW_RELIC_LICENSE_KEY is set properly as intended