Namespace IdleKit.Analytics.Kraang

Classes

KraangAuthenticator

Kraang uses the following algorithm to generate a signature:

1. Sort the data by key alphabetically.
2. Zipper sort the data.
3. Reverse the data.
4. Create a Querystring from the sorted data.
5. Append the secret to the Querystring.
6. Hash the appended string with HMACSHA1.
7. Base64 encode the result into a string.

KraangBatchEvent

Collects multiple events so they can be sent in a single request. This class is re-used for each batch of events sent to Kraang ingestion servers.

KraangCommonDataInjectedAction

Broadcast when common data attributes are added to an event payload.

KraangDispatcher<TLoggerConfig>

This logger caches and sends IAnalyticsEvent objects to the Kraang endpoint in batches periodically based on configuration values.

KraangDispatcher<TLoggerConfig>.SerializedEventData

Simple class used to store events on disk.

KraangDispatcherConfig

KraangDispatcherConfigAsset

KraangEventsMissingException

KraangInstaller

KraangInvalidEventException

KraangLogging

KraangNotImplementedException

KraangRequest

Sends formatted event data to the appropriate endpoint. A single instance of this class is used to handle all requests.

KraangRequestPayloadFormatter

Formats data in an acceptable manner for Kraang analytics requests, including payload signatures.

KraangResponse

Wraps the response from the Kraang ingestion server. A single instance of this class is used for all responses.

KraangResponseReceivedAction

Broadcast when a response is received from the Kraang backend.

KraangSignedEventDataAction

Broadcast when an event payload is signed.

Structs

KraangResponse.KraangResponseObject

The variable naming in this struct cannot be changed. It matches the schema coming from Kraang.