replace Rails logging with StatsD metrics for diagnostic codes #20272
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.
Summary
Rails.logger.info
calls inlog_hyphenated_diagnostic_codes
withStatsD.increment
to avoid logging sensitive diagnostic codes. The new metrics include diagnostic code, diagnostic code type, and hyphenated diagnostic code as tags.Related issue(s)
Testing done
Rails.logger.info
.StatsD.increment
is now used to record metrics, and updated tests to ensure that the correct metrics and tags are being sent.What areas of the site does it impact?
log_hyphenated_diagnostic_codes
method in theMaxRatingAnnotator
class, which handles processing diagnostic codes for rated disabilities.Acceptance criteria
StatsD.increment
calls.