stackabletech / stackabletech/actions
chore: Use stackable-telemetry here if you wanted.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 9
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100