A thin wrapper over libhoney-java. Use this to send events to Honeycomb.
Require this namespace as honeycomb and then use it like this:
; Initialise this library (honeycomb/init {:data-set "Your Honeycomb dataset" :write-key "Your Honeycomb API key"})
; Send an event (honeycomb/with-event {:initial :data} {} ... do your stuff ... (honeycomb/add-to-event :more "event data") ... do more of your stuff ...)
A thin wrapper over libhoney-java. Use this to send events to Honeycomb. Require this namespace as honeycomb and then use it like this: ; Initialise this library (honeycomb/init {:data-set "Your Honeycomb dataset" :write-key "Your Honeycomb API key"}) ; Send an event (honeycomb/with-event {:initial :data} {} ... do your stuff ... (honeycomb/add-to-event :more "event data") ... do more of your stuff ...)
Fields are the data that are sent as part of an event.
Events are just maps, where the keys are either keywords or strings and the values may be anything. Since clj-honeycomb wraps the Java Honeycomb SDK, we must transform some of the values from Clojure types into more Java-friendly types where possible.
Only the ->ValueSupplier function in this namespace should be considered part of the public API for clj-honeycomb.
Fields are the data that are sent as part of an event. Events are just maps, where the keys are either keywords or strings and the values may be anything. Since clj-honeycomb wraps the Java Honeycomb SDK, we must transform some of the values from Clojure types into more Java-friendly types where possible. Only the ->ValueSupplier function in this namespace should be considered part of the public API for clj-honeycomb.
No vars found in this namespace.
Functions to make it easier to test code that uses clj-honeycomb.
Functions to make it easier to test code that uses clj-honeycomb.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close