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.
What are you changing?
Having recently added and tooled a new acquisitions component in the Sticky Liveblog Ask (renamed Gutter Liveblog Ask), we now need to track the data separately. It was using the ACQUISITIONS_OTHER generic OphanComponentType and we would like to use a dedicated OphanComponentType.
Why?
This will allow us to report more easily, add monitoring and alerts in Grafana so that we can be notified if acquisitions drop below a threashold which could indicate a problem.
Related PRs:
ophan PR 6849
ophan-data-lake PR 8229