Closed
Description
Why is this needed?
In the PR #2194 we refactored the Metrics utility to allow bring new utilities. But it created some technical debt that must be addressed now.
Some items we need to fix:
- Cleanup the slight confusion in OOO / ProtocolFix possible mistakes in docstringsRemove old and commented codeRefactor extract* into standalone functions to reduce call graphSplit up functional and unit tests with new providers
Which area does this relate to?
Metrics
Suggestion
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (Python) TenetsShould this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Shipped
Activity
heitorlessa commentedon Aug 3, 2023
adjusting labels to prevent incorrect metrics
[-]Tech debt: Fix the metrics utility to make the code clean and uniform.[/-][+]Tech debt: Improve Metrics provider to make it more maintainable[/+]github-actions commentedon Aug 9, 2023
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
4 remaining items