[PR] Add the otlp-trace feature: a second music-application copy traced with OpenTelemetry [skywalking-showcase]

["wankai123 (via GitHub)" <gi...@apache.org>]

wankai123 opened a new pull request, #306:
URL: https://github.com/apache/skywalking-showcase/pull/306

   ### Add the `otlp-trace` feature: a second copy of the music application traced with OpenTelemetry
   
   A second copy of the music application runs beside the SkyWalking-agent one, built from the agentless images. The Java, Node.js and Python services are instrumented at start by the OpenTelemetry Operator's auto-instrumentation images (copied in by an init container, switched on through `JAVA_TOOL_OPTIONS`, `NODE_OPTIONS`, `PYTHONPATH`), the APISIX frontend by its built-in `opentelemetry` plugin, and the same Selenium load generator drives the page, so the traces start at `frontend`. Every span goes over OTLP/HTTP to the OpenTelemetry Collector, which delivers it to the OAP twice: natively as OTLP (stored natively since apache/skywalking#14096) and converted to Zipkin, so Grafana Tempo serves the same traces at `/otlp` and `/zipkin`. The copy has its own docker network and Kubernetes namespace (`otel-services`) because the services address each other by fixed hostnames. The `grafana` feature provisions the `OTLPTraceQL` datasource and the `OTLP Trace` dashboard. The Go `rating` ser
 vice has no runtime instrumentation and the page carries no browser agent; both are documented in the feature table.
   
   **Images.** OAP moves to the master image with native OTLP trace storage and the TraceQL fixes (apache/skywalking#14096, apache/skywalking#14099); the Tempo API, the Zipkin receiver and the Zipkin query are enabled in both compose bases. The UI moves to the current Horizon image, configured through its `HORIZON_*` settings in compose and its Tempo API endpoint on Kubernetes.
   
   **Also in this PR.**
   - `docker-compose.flink-monitor.yaml` merges with the base files like every other feature (shared `sw` network, no private OAP and BanyanDB, the shared collector image variables, Flink web UI on host 8082 since 8081 is the SkyWalking UI).
   - Agentless Dockerfile fixes: the frontend still bundled the browser agent (Vite's entry is `index.jsx`), the recommendation service does not run on `python:3` (3.14), the rating service had `go build`'s flag order wrong.
   - The app and recommendation services forward W3C trace context (`traceparent`, `tracestate`) so a mesh or OTLP trace survives their hops; the agentless app's B3 loop iterated indices instead of names.
   - The `sample-services` frontend and ActiveMQ no longer OOM: APISIX sized its workers by the node's CPUs (`worker_processes: 2` now), and ActiveMQ's 128m heap did not fit 256Mi under emulation (512Mi now).
   
   **Verified** on a local kind cluster with `cluster,banyandb,asz,otlp-trace,grafana`: `frontend | /homepage` traces spanning frontend, app, gateway, recommendation and songs on both `/otlp` and `/zipkin`; Grafana Explore returns 200 on the traces and spans tables for both datasources and the service dropdowns list the five services; the docker layout validated through `docker compose config` with the Makefile's environment. The `-agentless` images on ghcr keep their old behaviour until CI rebuilds them from the fixed Dockerfiles.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Add the otlp-trace feature: a second music-application copy traced with OpenTelemetry [skywalking-showcase]

["wankai123 (via GitHub)" <gi...@apache.org>]

wankai123 merged PR #306:
URL: https://github.com/apache/skywalking-showcase/pull/306


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org