⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Is the demo/http app ready to export tracing to OTEL_EXPORTER_OTLP_ENDPOINT? #256

@brightzheng100

Description

@brightzheng100

Describe the bug

The current demo/http app may not be ready to make it end-to-end yet, I guess, as there is no role for otel CLI to play with.

So, based on my understanding, I've updated the procedure to compile it with otel involved, but nothing has happened: no tracing at least based on my observation.

Environment

  • OS: iOS, Linux
  • Go Version:
$ go version
go version go1.25.5 darwin/arm64
  • Version: latest in main branch, as of 6 Jan 2026.

To Reproduce

  1. To compile it with otel CLI, for both of my testing envs:

For Server:

env GOOS=darwin GOARCH=arm64 otel go build -o server-darwin-arm64 .
env GOOS=linux GOARCH=arm64 otel go build -o server-linux-arm64 .

For Client:

env GOOS=darwin GOARCH=arm64 otel go build -o client-darwin-arm64 .
env GOOS=linux GOARCH=arm64 otel go build -o client-linux-arm64 .

Then run it with OTEL_EXPORTER_OTLP_ENDPOINT exported for collecting the tracing:

export OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4318"

But, nothing had happened: no tracing was observed based on my experiments.

Expected behavior

Tracing should be observed and collected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions