chore: Use stackable-telemetry here if you wanted.

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
ci-cd

Research direction

Start with the linked pull-request discussion and inspect the Rust GitHub Action code that contains the shown Tracing builder. Determine the intended use of stackable-telemetry from that discussion; done means the action uses the agreed telemetry setup and its existing checks still pass.

Written by the indexing model from the issue text.

Description

We could use stackable-telemetry here if you wanted.

let _tracing_guard = Tracing::builder()
    .service_name("interu")
    .with_console_output(
        Settings::builder()
            .with_environment_variable("LOG_LEVEL")
            .with_default_level(tracing_subscriber::filter::LevelFilter::INFO)
            .enabled(true)
            .build()
    )
    .build()
    .init()?;

Originally posted by @NickLarsenNZ in https://github.com/stackabletech/actions/pull/26#discussion_r1889118537

Dominant language
Rust
Stars
0
Forks
0
Avg merge
2d 5h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/actions

All issues in stackabletech/actions

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.