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
This release brings a few new features, performance improvements, but also one backwards-incompatible change.
10
+
11
+
Again, all credit for the improvements goes to our fantastic contributors!
12
+
13
+
### Complete list of changes
14
+
15
+
This version is compatible with Telemetry.Metrics v0.6.0, meaning that you can use 2-arity measurement functions, accepting both event measurements and metadata.
16
+
17
+
It's also tested for compatibility with Elixir 1.11.
18
+
19
+
Among various improvements, this release also brings one backwards-incompatible change in DataDog formatter, which fixes the previous, incorrect behaviour.
20
+
Previously, the sum metric updates would be translated to gauge increments/decrements on the DataDog side.
21
+
However, DataDog doesn't support relative changes of gauge's value, and so the reported metric would show only the last measurement sent by the reporter.
22
+
The current version correctly sends sum updates as relative changes to the DataDog counter, which results in correct metric values on the DataDog side.
23
+
24
+
#### Added
25
+
26
+
- Send metrics to Unix Domain Sockets via `:socket_path` option. (#37 by @kamilkowalski)
27
+
- Open multiple sockets to send metrics through via `:pool_size` option. (#41 by @epilgrim)
28
+
- Dynamically resolve configured hostname to avoid DNS lookup on every metric update. (#48 by @haljin)
29
+
30
+
#### Changed
31
+
32
+
- Allow empty and non-existent tag values in published events. (#49)
33
+
- Send sum metric updates with DataDog formatter as relative counter changes instead of relative gauge changes. (#47)
34
+
35
+
#### Fixed
36
+
37
+
- Prevent port leak by explicitly closing the failing socket. (#40 by @kamilkowalski)
0 commit comments