Releases: awslabs/aws-embedded-metrics-java
Releases · awslabs/aws-embedded-metrics-java
v4.2.0
06 Aug 20:45
Compare
Sorry, something went wrong.
No results found
What's Changed
Allow STDOUT overrides for AgentBasedEnvironments #147
Full Changelog : v4.1.3...v4.2.0
v4.1.3
02 Jan 17:32
Compare
Sorry, something went wrong.
No results found
v4.1.2
29 Nov 18:29
Compare
Sorry, something went wrong.
No results found
What's Changed
Change validation exceptions to unchecked exceptions in #141
Full Changelog : v4.1.1...v4.1.2
v4.1.1
09 Mar 23:38
Compare
Sorry, something went wrong.
No results found
What's Changed
Update vulnerable dependencies in #137
Add documentation for EMF auto-detection in #133
Full Changelog : v4.1.0...v4.1.1
v4.1.0
24 Jan 22:38
Compare
Sorry, something went wrong.
No results found
v4.0.3
14 Oct 13:45
Compare
Sorry, something went wrong.
No results found
What's Changed
Fix for context copying is disabling default dimensions in #128
Fixes for Java downgrade to 1.8 in #128
Full Changelog : v4.0.2...v4.0.3
v4.0.2
07 Oct 19:17
Compare
Sorry, something went wrong.
No results found
What's Changed
Fix: InvalidDimensionException when running on ECS Fargate with fluent-bit in #126
Full Changelog : v4.0.1...v4.0.2
v4.0.1
07 Oct 18:58
Compare
Sorry, something went wrong.
No results found
v4.0.0
18 Sep 17:44
Compare
Sorry, something went wrong.
No results found
What's Changed
Introduced thread-safety changes, concurrency tests, benchmarking in #111
Add validation for dimensions, metrics, namespace and timestamp in #119
Add support to clear custom dimensions in #105
Prevent duplicate dimensions in #88 . Thank you @aaronlna !
Fix: add logic for replacing colon in log group name in #110
Change DimensionSetExceededException to a checked exception in #122
Full Changelog : v3.1.0...v4.0.0
v2.0.0
03 Aug 22:36
Compare
Sorry, something went wrong.
No results found
Support for 30 dimensions per dimension set. If more than 30 dimensions are given then DimensionSetExceededException
will be thrown #106
Updates to README #97
Fix TCP client seeing "already connected" error when resending message after an exception #94