Open sethdarragile6 opened 7 months ago
per my discussion with @mchae-nava though the logging that we currently have here was meant to be temporary, we should consider adding more "long-term logging" and/or metrics (and perhaps even error handling?) in this area, so that more permanent monitoring/dashboarding can be left behind. This could either just be done within the context of THIS ticket, or maybe split off into another story
Issue Description
Once the
disability_compensation_remove_pciu
flag has been turned on, and the success of the change has been verified, the flag (and the logging) can be safely removed.Tasks
disability_compensation_remove_pciu
from va_526ez.rb, such that it only callsinitialize_vets360_contact_info
form_profile_spec.rb
pertaining to the flag, as well as now-old PCIU-related functionalityAcceptance Criteria
[ ] Adding more "long-term logging(statsD instead of rails logging)" and/or metrics (and perhaps even error handling?) in this area, so that more permanent monitoring/dashboarding can be left behind
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)