Skip to content

Add --enable-otel CLI flag for OpenTelemetry configuration#80

Open
Dominik1999 wants to merge 2 commits intonextfrom
dominik1999-claude/otel-config
Open

Add --enable-otel CLI flag for OpenTelemetry configuration#80
Dominik1999 wants to merge 2 commits intonextfrom
dominik1999-claude/otel-config

Conversation

@Dominik1999
Copy link
Copy Markdown
Contributor

Summary

  • Added --enable-otel CLI flag backed by MIDEN_TLNODE_ENABLE_OTEL env var
  • Added --otel-endpoint CLI flag backed by MIDEN_TLNODE_OTEL_ENDPOINT env var
  • Enabled clap env feature for env var backing
  • Replaced TracingConfig::from_env() with explicit TracingConfig::new() constructor
  • Updated docker-compose env vars to match new naming

Test plan

  • make test passes (13/13)
  • make lint passes
  • --help shows new flags
  • Docker compose uses new env var names

🤖 Generated with Claude Code

Closes #40

- Add --enable-otel flag backed by MIDEN_TLNODE_ENABLE_OTEL env var
- Add --otel-endpoint flag backed by MIDEN_TLNODE_OTEL_ENDPOINT env var
- Enable clap "env" feature for env var backing
- Replace TracingConfig::from_env() with explicit TracingConfig::new()
- Update docker-compose env vars to match new naming

Closes #40

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Dominik1999 Dominik1999 added this to the Release v0.4.0 milestone Apr 23, 2026
- Update rand 0.9.2 -> 0.9.4 to fix RUSTSEC-2026-0097 (unsoundness in
  ThreadRng reseeding with custom loggers)
- Add MPL-2.0 and LGPL-3.0-or-later to deny.toml license allow list
  (required by pubgrub, version-ranges, priority-queue via upstream
  miden-assembly -> miden-package-registry)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Dominik1999 Dominik1999 marked this pull request as ready for review April 23, 2026 07:57
Copy link
Copy Markdown
Contributor

@WiktorStarczewski WiktorStarczewski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just want to flag one thing, we have to be ok with LGPL-3-or-later in statically linked transitive deps in our published binaries. I think it's ok, but maybe worth a quick thought.

LGPL-3 static linking in Rust is legally ambiguous. The LGPL-3 "linking exception" was
▎ drafted around dynamic linking; Rust crates compile into the final binary as static
▎ linkage. Static-linking an LGPL-3 crate into a distributed binary (we publish to
▎ crates.io, and transport.miden.io is served from a Docker image built from this repo) can plausibly trigger LGPL-3 obligations — source provision alongside the distributed binary,
▎ license-notice inclusion in LICENSE / about screens, whatever else the license requires.
▎ There's no definitive Rust-community consensus on this; different projects land in
▎ different places (Mozilla's Servo forbids it, Bevy allows it, some crates explicitly
▎ re-license their static-linked LGPL deps).

@Dominik1999 Dominik1999 changed the base branch from main to next April 23, 2026 16:38
@Dominik1999
Copy link
Copy Markdown
Contributor Author

Don't merge yet! We need to check LGPL-3 license compatibility with MIT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OpenTelemetry configuration

3 participants