The Alephant Broker is used by Newbeat which is using an updated CloudWatch logger (the CloudWatch logger now has an updated interface).
Solution
We need to modify Alephant Broker to use the latest Alephant Logger (as that's what the updated Alephant CloudWatch Logger uses). Then update the metric calls to match the new interface.
Release Plan
I believe this will be a patch release rather than a minor or major.
Existing projects will need their Gemfiles updated at some point soon to point to the older version of the broker (as I don't believe we anchor gems to specific versions in all projects), so when older projects get deployed they just go ahead and grab the latest version of the broker gem which will use a different logger than probably expected.
darnould
commented
9 years ago
Problem
The Alephant Broker is used by Newbeat which is using an updated CloudWatch logger (the CloudWatch logger now has an updated interface).
Solution
We need to modify Alephant Broker to use the latest Alephant Logger (as that's what the updated Alephant CloudWatch Logger uses). Then update the
metriccalls to match the new interface.Release Plan
I believe this will be a patch release rather than a minor or major.
Existing projects will need their Gemfiles updated at some point soon to point to the older version of the broker (as I don't believe we anchor gems to specific versions in all projects), so when older projects get deployed they just go ahead and grab the latest version of the broker gem which will use a different logger than probably expected.