skywalking-rust

KO | EN

gitlite — search

#python #typescript #llm #linux #docker #nodejs #windows #cli #kubernetes #vue #awesome-list #pytorch #mcp #ios

skywalking-rust

(★ 82)

Apache SkyWalking Rust Agent

skywalking-rust Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Apache SkyWalking Rust Agent
==========

[![Twitter Follow](https://img.shields.io/twitter/follow/asfskywalking.svg?style=for-the-badge&label=Follow&logo=twitter)](https://twitter.com/AsfSkyWalking)

[![Crates](https://img.shields.io/badge/skywalking-crates.io-blue)](https://crates.io/crates/skywalking)
![CI](https://github.com/apache/skywalking-rust/workflows/CI/badge.svg?branch=master)

[**SkyWalking**](https://github.com/apache/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.

# Concepts

All concepts are from the official SkyWalking definitions.

## Tracing

### Span

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

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.

## Logging

### LogRecord

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

## Metrics

### Meter

- **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.

## Management

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:

| Key                      | Value                          |
| ------------------------ | ------------------------------ |
| hostname                 | The hostname of os.            |
| ipv4 (probably multiple) | The ipv4 addresses of network. |
| language                 | rust                           |
| OS Name                  | Linux / 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.

# Example

```rust, no_run
use skywalking::{
    logging::{logger::Logger, record::{LogRecord, RecordType}},
    reporter::grpc::GrpcReporter,
    trace::tracer::Tracer,
    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.
            logger.log(
                LogRecord::new()
                    .add_tag("level", "INFO")
                    .with_tracing_context(&ctx)
                    .with_span(&span2)
                    .record_type(RecordType::Text)
                    .content("Something...")
            );

// 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(
        Counter::new("instance_trace_count")
            .add_label("region", "us-west")
            .add_label("az", "az-1"),
    );

metricer.boot().await;

counter.increment(10.);
}

#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
    // Connect to skywalking oap server.
    let reporter = GrpcReporter::connect("http://0.0.0.0:11800").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
        .reporting()
        .await
        .with_graceful_shutdown(async move {
            signal::ctrl_c().await.expect("failed to listen for event");
        })
        .spawn();

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

handle_metric(metricer).await;

handle_request(tracer, logger).await;

handle.await?;

Ok(())
}
```

# Advanced APIs

## Async Span APIs

`Span::prepare_for_async` designed for async use cases.
When tags, logs, and attributes (including end time) of the span need to be set in another
thread or coroutine.

`TracingContext::wait` wait for all `AsyncSpan` finished.

```rust
use skywalking::{
    trace::tracer::Tracer,
    trace::span::HandleSpanObject,
};

async fn handle(tracer: Tracer) {
    let mut ctx = tracer.create_trace_context();

{
        let span = ctx.create_entry_span("op1");

// Create AsyncSpan and drop span.
        // Internally, span will occupy the position of finalized span stack.
        let mut async_span = span.prepare_for_async();

// Start async route, catch async_span with `move` keyword.
        tokio::spawn(async move {

async_span.add_tag("foo", "bar");

// Something...

// async_span will drop here, submit modifications to finalized spans stack.
        });
    }

// Wait for all `AsyncSpan` finished.
    ctx.wait();
}
```

# Advanced Reporter

The advanced report provides an alternative way to submit the agent collected data to the backend.

## kafka reporter

The Kafka reporter plugin support report traces, metrics, logs, instance properties to Kafka cluster.

Make sure the feature `kafka-reporter` is enabled.

```rust
#[cfg(feature = "kafka-reporter")]
mod example {
    use skywalking::reporter::Report;
    use skywalking::reporter::kafka::{KafkaReportBuilder, KafkaReporter, ClientConfig};

async fn do_something(reporter: &impl Report) {
        // ....
    }

async fn foo() {
        let mut client_config = ClientConfig::new();
        client_config
            .set("bootstrap.servers", "broker:9092")
            .set("message.timeout.ms", "6000");

let (reporter, reporting) = KafkaReportBuilder::new(client_config).build().await.unwrap();
        let handle = reporting.spawn();

do_something(&reporter);

handle.await.unwrap();
    }
}
```

# How to compile?

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

```shell
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.

## NOTICE

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:

```shell
   sudo apt install protobuf-compiler
   ```

For MacOS:

```shell
   brew install protobuf
   ```

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

```shell
   cargo add skywalking --features vendored
   ```

3. Build from [source](https://github.com/protocolbuffers/protobuf). If `protc` isn't install inside $PATH, the env value `PROTOC` should be set.

```shell
   PROTOC=/the/path/of/protoc
   ```

For details, please refer to [prost-build:sourcing-protoc](https://docs.rs/prost-build/latest/prost_build/index.html#sourcing-protoc).

# Release

The SkyWalking committer(PMC included) could follow [this doc](https://github.com/apache/skywalking-rust/blob/master/Release-guide.md) to release an official version.

# License

Apache 2.0

skywalking-rust

skywalking-rust Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

skywalking-rust

skywalking-rust Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README