1.3.0-beta1

Features

• This release brings the -beta1 version of Distributed Tracing for iOS apps ⭐. From now, you'll be able to send traces to Datadog and let us visualise the timings of your code execution. If you're using Datadog instrumentation on backend, this also includes full-stack trace propagation.

Instantiate DDTracer:

import Datadog
import OpenTracing

Global.sharedTracer = DDTracer.initialize(
    configuration: DDTracer.Configuration(
        sendNetworkInfo: true
    )
)

and start instrumenting your code:

let span = Global.sharedTracer.startSpan(operationName: "something I measure")
// do something you want to measure ...
// ... then, when the operation is finished:
span.finish()

Read more in iOS Trace Collection guide.

Improvements

• typealias DDLogger = Datadog.Logger is introduced, to help avoiding compiler ambiguity in projects defining their own Logger class (#143), solves #127 and #142 (thanks @krzysztofzablocki , @amyslies)

1.2.2

Bug Fixes

• Fixes the problem with logs being occasionally malformed when seen at app.datadoghq.com (#133)

1.2.1

Bug Fixes

• Fixed ISO8601DateFormatter crash on iOS 11.0 and iOS 11.1 - the milliseconds precision won't be available on iOS 11.0 and iOS 11.1 till next regular release (#129), solves #126 (thanks @lgaches, @Britton-Earnin)

1.2.0

Features

• The serviceName default value is changed to app bundle identifier + can be customized globally (#102)

Bug Fixes

• Fixed family of NWPathMonitor crashes (#110), solves #110, #70 (thanks @LeffelMania, @00FA9A, @jegnux)

Improvements

• Milliseconds precision for logs (#96), solves #95 (thanks @flobories)
• Improved logs delivery for app extensions (#84), solves #52 (thanks @lmramirez)

Other Changes

• The in-build source value was changed from mobile to ios (#111)
• Package.swift is updated to link the SDK as dynamic framework (#82)

---

Upgrade Steps

Datadog.Configuration builder now requires the environment value to be passed along with clientToken:

Datadog.Configuration
    .builderUsing(clientToken: "<client-token>", environment: "<environment>")

See details

What can I use the environment for?

This will enable you to filter data from different environments (staging | production | ...) by using env: filter on app.datadoghq.com. If you don't have diversed environments, "production" might be a good default.

Eventual Breaking Changes in Dashboards and Pipelines

If any of your app.datadoghq.com dashboards or pipelines depends on service or source attribute, you may need to update them.

See details

New default value for service attribute

If you were not using .set(serviceName:) to explicitly set the service for Logger.builder the default value of "ios" was used. In 1.2.0, this default is changed to application bundle identifier. If your dashboards depend on "ios" this might break.

To make it compatible, use either the .set(serviceName:) on individual Logger.builder or set the default service name for all loggers in Datadog.Configuration.builderUsing(...).set(serviceName: "...").

New default value for source attribute

We changed the value of source attribute from mobile to ios. If any of your dashboards or pipelines depends on this, please update them accordingly.

1.1.0

🐛 #80 : missing required module fix
⏲️ #65 : Syncing logs time with server

1.0.2

🐞 Fix "'module.modulemap' should be inside the 'include' directory" Carthage error, fixes #71

1.0.1

🐞 Fix "device out of memory" crash, fixes #58

1.0.0

🚀 1.0.0 release of the logging feature.

Datadog.initialize(...)

let logger = Logger.builder.build()
logger.info("Hello from 1.0.0 👋")

1.0.0-beta3

• 🚀 Add iOS 11 support #53
• ↘️ Drop macOS/Catalyst support #55

1.0.0-beta2

• 🚀 Add Carthage support #39
• 🐞 Crash when logging a debug level event via Logger #47