Bump to 0.6.0. (#56)

2 files changed
tree: 560f5856971bc3123dab7dda6aa4ae0e5eba98d8
  1. .github/
  2. dist-material/
  3. e2e/
  4. examples/
  5. src/
  6. tests/
  7. .asf.yaml
  8. .dockerignore
  9. .gitignore
  10. .gitmodules
  11. .rustfmt.toml
  12. build.rs
  13. Cargo.toml
  14. docker-compose.dev.yml
  15. docker-compose.e2e.yml
  17. NOTICE
  18. README.md
  19. Release-guide.md
  20. requirements.txt
  21. rust-toolchain.toml

Apache SkyWalking Rust Agent

Twitter Follow

Crates CI

SkyWalking Rust Agent provides observability capability for Rust App and Library, including tracing, metrics, topology map for distributed system and alert. It uses SkyWalking native formats and core concepts to keep best compatibility and performance.


All concepts are from the official SkyWalking definitions.



Span is an important and common concept in distributed tracing system. Learn Span from Google Dapper Paper. For better performance, we extend the span into 3 kinds.

  1. EntrySpan EntrySpan represents a service provider, also the endpoint of server side. As an APM system, we are targeting the application servers. So almost all the services and MQ-consumer are EntrySpan(s).
  2. LocalSpan LocalSpan represents a normal Java method, which does not relate to remote service, neither a MQ producer/consumer nor a service(e.g. HTTP service) provider/consumer.
  3. ExitSpan ExitSpan represents a client of service or MQ-producer, as named as LeafSpan at early age of SkyWalking. e.g. accessing DB by JDBC, reading Redis/Memcached are cataloged an ExitSpan.

Tag and Log are similar attributes of the span.

  • Tag is a key:value pair to indicate the attribute with a string value.
  • Log is heavier than tag, with one timestamp and multiple key:value pairs. Log represents an event, typically an error happens.


TracingContext is the context of the tracing process. Span should only be created through context, and be archived into the context after the span finished.



LogRecord is the simple builder for the LogData, which is the Log format of Skywalking.



  • Counter API represents a single monotonically increasing counter which automatically collects data and reports to the backend.
  • Gauge API represents a single numerical value.
  • Histogram API represents a summary sample observations with customized buckets.


Reporting the extra information of the instance.

Report instance properties

The method insert_os_info of skywalking::management::instance::Properties will insert the predefined os info. In addition, you can use insert, update, and remove to customize your instance information.

The predefined os info:

hostnameThe hostname of os.
ipv4 (probably multiple)The ipv4 addresses of network.
OS NameLinux / Windows / Mac OS X
Process No.The ID of Process.

Keep alive

Keep the instance alive in the backend analysis. Only recommend to do separate keepAlive report when no trace and metrics needs to be reported. Otherwise, it is duplicated.


use skywalking::{
    logging::{logger::Logger, record::{LogRecord, RecordType}},
    metrics::{meter::Counter, metricer::Metricer},
use std::error::Error;
use tokio::signal;

async fn handle_request(tracer: Tracer, logger: Logger) {
    let mut ctx = tracer.create_trace_context();

        // Generate an Entry Span when a request is received.
        // An Entry Span is generated only once per context.
        // Assign a variable name to guard the span not to be dropped immediately.
        let _span = ctx.create_entry_span("op1");

        // Something...

            // Generates an Exit Span when executing an RPC.
            let span2 = ctx.create_exit_span("op2", "remote_peer");

            // Something...

            // Do logging.
                    .add_tag("level", "INFO")

            // Auto close span2 when dropped.

        // Auto close span when dropped.

    // Auto report ctx when dropped.

async fn handle_metric(mut metricer: Metricer) {
    let counter = metricer.register(
            .add_label("region", "us-west")
            .add_label("az", "az-1"),



async fn main() -> Result<(), Box<dyn Error>> {
    // Connect to skywalking oap server.
    let reporter = GrpcReporter::connect("").await?;
    // Optional authentication, based on backend setting.
    let reporter = reporter.with_authentication("<TOKEN>");

    // Spawn the reporting in background, with listening the graceful shutdown signal.
    let handle = reporter
        .with_graceful_shutdown(async move {
            signal::ctrl_c().await.expect("failed to listen for event");

    let tracer = Tracer::new("service", "instance", reporter.clone());
    let logger = Logger::new("service", "instance", reporter.clone());
    let metricer = Metricer::new("service", "instance", reporter);


    handle_request(tracer, logger).await;



How to compile?

If you have skywalking-(VERSION).crate, you can unpack it with the way as follows:

tar -xvzf skywalking-(VERSION).crate

Using cargo build generates a library. If you'd like to verify the behavior, we recommend to use cargo run --example simple_trace_report which outputs executable, then run it.


This crate automatically generates protobuf related code, which requires protoc before compile.

Please choose one of the ways to install protoc.

  1. Using your OS package manager.

    For Debian-base system:

    sudo apt install protobuf-compiler

    For MacOS:

    brew install protobuf
  2. Auto compile protoc in the crate build script, just by adding the feature vendored in the Cargo.toml:

    cargo add skywalking --features vendored
  3. Build from source. If protc isn't install inside $PATH, the env value PROTOC should be set.


For details, please refer to prost-build:sourcing-protoc.


The SkyWalking committer(PMC included) could follow this doc to release an official version.


Apache 2.0