Skip to content

Commit

Permalink
Bringing over Swift edits to Kotlin
Browse files Browse the repository at this point in the history
  • Loading branch information
MichaelGHSeg authored Nov 14, 2024
1 parent 30b94f0 commit c356537
Showing 1 changed file with 4 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -202,11 +202,12 @@ Analytics-Kotlin is built with extensibility in mind. Use the tools list below t
> If you are using the Analytics Android (Classic) SDK, you can find [the documentation here](/docs/connections/sources/catalog/libraries/mobile/android). Many of the features available in the Analytics Kotlin SDK are not available in the Analytics Android (Classic) SDK.

## Telemetry
Telemetry data related to the configuration and usage of the Analytics-Kotlin SDK is collected and sent to Segment by default. This includes some basic configuration information, plugins and event types used, and basic error information. Segment downsamples the data to minimize traffic and doesn't collect any personally identifiable information (PII) or event data.
The Analytics-Kotlin SDK collects telemetry data on configuration and usage by default. This includes basic information on SDK setup, plugins and event types used, and basic error details. Segment downsamples the data to minimize traffic and doesn't collect any personally identifiable information (PII) or event data.
You can disable telemetry at any time by setting `Telemetry.shared.enable = false`.
You can disable telemetry at any time by setting `Telemetry.enable = false`.
When internal errors or errors from plugins occur, the write key may be included with error data to help Segment identify the issue(s). You can disable this by setting `Telemetry.sendWriteKeyOnError = false`.
When internal errors or errors from plugins occur, the writekey may be included with the error data to help customers track down problems. You can disable this by setting `Telemetry.sendWriteKeyOnError = false`.
## Timestamps in Kotlin
Due to efficiency updates made to Segment's Kotlin library, Segment now adds the `sentAt` timestamp to an event when the batch is complete and initially tried to the Segment API. This can impact the value of the `timestamp` field calculated by Segment if users are operating in an offline mode. More details on this change can be seen in Segment's [timestamp documentation](/docs/connections/spec/common/#sentat).

0 comments on commit c356537

Please sign in to comment.