You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally middy version 2.x provides an implementation of a middleware for cloudwatch-metrics (Embedded metric format), link: https://github.com/middyjs/middy/tree/main/packages/cloudwatch-metrics But given that middy version 1.x is incompatible with middy version 2.x , the middleware for cloudwatch-metrics (Embedded metric format) cannot be used together with dazn-power-tools. I have writtten some test cases , here: https://github.com/niko-achilles/cloudwatchMetrics-lambda-power-tools that proves this fact and came to conclusion that i needed to create a middy version 1.x cloudwatch-metrics midddleware (Embedded metric format) in order to use it with dazn-power-tools. That also mean that for the libraries - i.e http client , in order to support cloudwatch-metrics (Embedded metric format) a re-implementation is needed .
Any plans about supporting cloudwatch-metrics (Embedded metric format) as middy middleware with dazn-power-tools ?
This is a Feature Proposal
Description
CloudWatch just announced a native format for tracking custom metrics through CloudWatch Logs: https://aws.amazon.com/about-aws/whats-new/2019/11/amazon-cloudwatch-launches-embedded-metric-format/
Maybe it's time to let you choose how you want to record those custom metrics from our libraries - i.e. the http client
The text was updated successfully, but these errors were encountered: