Closed lukey-luke closed 3 months ago
Megan: Is this ticket related to our mentioning the gaps in logging or something else? Could you provide more details on why this needs to be prioritized urgently? Can you help us understand if this task can be included in Sprint Y, or does it need to be prioritized for the next sprint? Your insights will help us allocate resources effectively. Thank you! New Anneliese LaTempa (OOO 6/17-6/20) 2 minutes ago Something else. We discovered while testing today we want to include the claim id so we can distinguish between single and multi contention claims in our monitoring. If our stakeholders decide we need this level of monitoring for release, we could potentially not meet our target release date. If the next two sprints are full we wouldn't be able to release before the end of June.
@lukey-luke @tyler-spangler6 Please confirm what environment you want this deployed to.
update: this logging update has been deployed up to the prod-test
environment. We plan to deploy to the production
environment ~1pm ET on 6/20.
@lukey-luke this has been done. i'll close this issue at the end of the day unless concerns are raised. thanks!
Requesting Team
Contention Classification
Related product/initiative
No response
Problem/Need
Updates to logging covered in this PR HERE will enable the contention classification team to better make use of the logs on datadog dashboards.
Why?
It will enable the contention classification team to better make use of the logs on datadog dashboards.
Acceptance criteria
develop
is deployed for the cc-app containerPriority
The CC team needs this 6/20 and can reach out to Luke or Tyler to get it done.
Target timeline
No response
Context and documentation
No response