Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计通过

salvo-logging齐射测井

Agent Skill

salvo-logging 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

291

周安装

12

GitHub Stars

16

下载量

95
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:salvo-logging(齐射测井)
来源仓库:https://github.com/salvo-rs/salvo-skills
仓库路径:skills/salvo-logging
安装命令:
npx skills add https://github.com/salvo-rs/salvo-skills --skill salvo-logging
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/salvo-rs/salvo-skills --skill salvo-logging

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合围绕仓库状态、代码变更或协作事项进行整理。
  • 可结合来源仓库和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围和维护状态。salvo-logging 属于开发类 Skill,可作为该场景下的辅助能力补充。
  • 注意是否会触发联网、命令执行或文件读写。

SKILL.md

Salvo Logging and Tracing

[dependencies]
salvo = { version = "0.89.3", features = ["logging"] }
tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter"] }

Logger middleware

salvo::logging::Logger emits a tracing span per request with remote_addr, version, method, path, and response status + duration. It must be installed on a Service (not a Router) so it wraps the catcher and sees the final status:

use salvo::logging::Logger;
use salvo::prelude::*;

#[tokio::main]
async fn main() {
    tracing_subscriber::fmt().init();

    let router = Router::new().get(hello);
    let service = Service::new(router).hoop(Logger::new());

    let acceptor = TcpListener::new("0.0.0.0:8080").bind().await;
    Server::new(acceptor).serve(service).await;
}

Logger::new().log_status_error(false) disables auto-logging of StatusError bodies (on by default).

Custom request logger

When Logger is not enough, write a handler that measures time around call_next:

use salvo::prelude::*;
use std::time::Instant;
use tracing::info;

#[handler]
async fn request_logger(
    req: &mut Request, depot: &mut Depot, res: &mut Response, ctrl: &mut FlowCtrl,
) {
    let start = Instant::now();
    let method = req.method().clone();
    let path = req.uri().path().to_string();

    ctrl.call_next(req, depot, res).await;

    info!(
        %method,
        %path,
        status = res.status_code.map(|s| s.as_u16()).unwrap_or(0),
        duration_ms = start.elapsed().as_millis() as u64,
        "request",
    );
}

Gotcha: inside a handler res.status_code is a Option<StatusCode> field (not a method). If the handler hasn't set it, it's None until the catcher runs.

Structured logging in handlers

use tracing::{debug, info, warn, instrument};

#[handler]
#[instrument(skip_all, fields(user_id))]
async fn get_user(req: &mut Request, res: &mut Response) {
    let user_id: u32 = req.param("id").unwrap_or(0);
    tracing::Span::current().record("user_id", user_id);

    debug!("fetching user");
    match fetch_user(user_id).await {
        Ok(user) => { info!("found"); res.render(Json(user)); }
        Err(e) => { warn!(error = %e, "not found"); res.status_code(StatusCode::NOT_FOUND); }
    }
}

Log filtering

Configure levels via RUST_LOG (e.g. RUST_LOG=info,salvo=debug,hyper=warn):

use tracing_subscriber::{EnvFilter, fmt, layer::SubscriberExt, util::SubscriberInitExt};

fn init_logging() {
    let filter = EnvFilter::try_from_default_env()
        .unwrap_or_else(|_| EnvFilter::new("info,salvo=debug,hyper=warn"));

    tracing_subscriber::registry()
        .with(filter)
        .with(fmt::layer())
        .init();
}

JSON logging

tracing_subscriber::registry()
    .with(EnvFilter::try_from_default_env().unwrap_or_else(|_| EnvFilter::new("info")))
    .with(fmt::layer().json().with_current_span(true).with_span_list(true))
    .init();

File logging with rotation

tracing-appender = "0.2"
use tracing_appender::{rolling, non_blocking};

let file_appender = rolling::daily("logs", "app.log");
let (writer, _guard) = non_blocking(file_appender);

tracing_subscriber::registry()
    .with(EnvFilter::new("info"))
    .with(fmt::layer().with_writer(writer).with_ansi(false))
    .init();
// _guard MUST be held for the process lifetime or buffered logs are dropped.

Request ID

use uuid::Uuid;

#[handler]
async fn add_request_id(
    req: &mut Request, depot: &mut Depot, res: &mut Response, ctrl: &mut FlowCtrl,
) {
    let id = req.header::<String>("x-request-id")
        .unwrap_or_else(|| Uuid::new_v4().to_string());
    depot.insert("request_id", id.clone());
    res.headers_mut().insert("x-request-id", id.parse().unwrap());

    let span = tracing::info_span!("request", request_id = %id, method = %req.method(), path = %req.uri().path());
    let _enter = span.enter();
    ctrl.call_next(req, depot, res).await;
}

Salvo also ships salvo::request_id::RequestId middleware (feature request-id) that does this automatically.

Slow request alerting

#[handler]
async fn timing(req: &mut Request, depot: &mut Depot, res: &mut Response, ctrl: &mut FlowCtrl) {
    let start = Instant::now();
    ctrl.call_next(req, depot, res).await;
    let ms = start.elapsed().as_millis();
    if ms > 1000 {
        tracing::warn!(path = %req.uri().path(), duration_ms = ms as u64, "slow request");
    }
}

OpenTelemetry

Salvo provides salvo_otel (feature otel) for trace propagation. For raw tracing-otel:

opentelemetry = "0.22"
opentelemetry-otlp = "0.15"
tracing-opentelemetry = "0.23"
let tracer = opentelemetry_otlp::new_pipeline()
    .tracing()
    .with_exporter(opentelemetry_otlp::new_exporter().tonic().with_endpoint("http://localhost:4317"))
    .install_batch(opentelemetry_sdk::runtime::Tokio)
    .unwrap();

tracing_subscriber::registry()
    .with(tracing_subscriber::fmt::layer())
    .with(tracing_opentelemetry::layer().with_tracer(tracer))
    .init();

// On shutdown:
opentelemetry::global::shutdown_tracer_provider();

Gotchas

  • Install Logger on Service, not Router — otherwise it logs before the catcher rewrites the status and body.
  • Logger requires a tracing subscriber; without one, nothing is emitted.
  • tracing-appender writers must keep their WorkerGuard alive or pending log lines are discarded at shutdown.
  • Never log request bodies or headers like Authorization / Cookie unredacted.

Related Skills

  • salvo-error-handling: Logger auto-logs StatusError bodies.
  • salvo-middleware: Logger is just a hoop.
  • salvo-testing: tracing-test crate verifies log output.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.64%
按下载量换算32

Claude

32.31%
按下载量换算31

Cursor

18.04%
按下载量换算17

Gemini CLI

10.12%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills