Library Moduleswift-distributed-tracing 1.2.0Tracing

    Tracing

    A Distributed Tracing API for Swift.

    index.md
    import Tracing

    Module information

    Declarations
    178
    Symbols
    227

    Coverage

    44.4 percent of the declarations in Tracing are fully documented39.3 percent of the declarations in Tracing are indirectly documented16.3 percent of the declarations in Tracing are completely undocumented

    Declarations

    6.7 percent of the declarations in Tracing are global functions or variables1.7 percent of the declarations in Tracing are operators24.2 percent of the declarations in Tracing are initializers, type members, or enum cases37.1 percent of the declarations in Tracing are instance members1.7 percent of the declarations in Tracing are instance subscripts3.9 percent of the declarations in Tracing are protocols12.4 percent of the declarations in Tracing are protocol requirements3.4 percent of the declarations in Tracing are default implementations6.7 percent of the declarations in Tracing are structures2.2 percent of the declarations in Tracing are typealiases

    Interfaces

    98.3 percent of the declarations in Tracing are unrestricted1.7 percent of the declarations in Tracing are underscored
    Module stats and coverage details

    Overview

    This is a collection of Swift libraries enabling the instrumentation of server side applications using tools such as tracers. Our goal is to provide a common foundation that allows to freely choose how to instrument systems with minimal changes to your actual code.

    While Swift Distributed Tracing allows building all kinds of instruments, which can co-exist in applications transparently, its primary use is instrumenting multithreaded and distributed systems with distributed traces.

    Quickstart Guides

    We provide a number of guides aimed at getting started with tracing your systems, and have prepared them from three “angles”:

    1. Trace Your Application, for Application developers who create server-side applications,

    2. Instrument Your Library or Framework, for Library/Framework developers who provide building blocks to create these applications,

    3. Implement a Tracer, for Instrument developers who provide tools to collect distributed metadata about your application.

    If unsure where to start, we recommend starting at the first guide and continue reading until satisfied, as the subsequent guides dive deeper into patterns and details of instrumenting systems and building instruments yourself.

    Guides