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
Copy file name to clipboardExpand all lines: README.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,13 +23,23 @@ The client jar is distributed via Maven central, and can be downloaded [from Mav
23
23
24
24
### Unix Domain Socket support
25
25
26
-
As an alternative to UDP, Agent v6 can receive metrics via a UNIX Socket (on Linux only). This library supports transmission via this protocol. To use it, pass the socket path as a hostname, and `0` as port.
26
+
As an alternative to UDP, Agent v6 can receive metrics via a UNIX Socket (on Linux only). This library supports transmission via this protocol. To use it
27
+
use the `address()` method of the builder and pass the path to the socket with the `unix://` prefix:
By default, all exceptions are ignored, mimicking UDP behaviour. When using Unix Sockets, transmission errors trigger exceptions you can choose to handle by passing a `StatsDClientErrorHandler`:
29
36
30
37
- Connection error because of an invalid/missing socket triggers a `java.io.IOException: No such file or directory`.
31
38
- If DogStatsD's reception buffer were to fill up and the non blocking client is used, the send times out after 100ms and throw either a `java.io.IOException: No buffer space available` or a `java.io.IOException: Resource temporarily unavailable`.
32
39
40
+
The default UDS transport is using `SOCK_DATAGRAM` sockets. We also have experimental support for `SOCK_STREAM` sockets which can
41
+
be enabled by using the `unixstream://` instead of `unix://`. This is not recommended for production use at this time.
42
+
33
43
## Configuration
34
44
35
45
Once your DogStatsD client is installed, instantiate it in your code:
0 commit comments