[DR-3476] Include additional fields in DRS getAccessURL Bard logs #1753
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira ticket: https://broadworkbench.atlassian.net/browse/DR-3476
Addresses
Key stakeholders such as the NIH want to know the usage patterns of the data that they are storing. Adding the snapshot name is more informative than using just the snapshot ids. This along with the addition of the billing profile id, dataset id and dataset name allows us to answer questions like, "What are the top X datasets and/or snapshots (of billing profile Y) that users are requesting data from?"
Summary of changes
Add the following fields to the DRS Bard log for getAccessURL (Note these are already available in the snapshot object that gets retrieved from the database, but these fields were not included in the cached snapshot object):
Testing Strategy
Local testing:
usermetrics.bardBasePath=https://terra-bard-dev.appspot.com
inapplication.properties
drsHacky
test to hit the breakpoint