Croway opened a new pull request, #192: URL: https://github.com/apache/camel-spring-boot-examples/pull/192
Reworks the `genai-observability` example: - **Observability stack via Camel CLI**: `docker-compose.yml`/`prometheus.yml` replaced by `camel infra run observability` (Camel JBang 4.22+). The bundled Prometheus scrapes the app at `host.docker.internal:9876/observe/metrics` (the `camel-observability-services-starter` management port), which the previous compose config did not. - **Spring Boot 4 startup fixes**: `langchain4j-ollama-spring-boot-starter` is incompatible with Spring Boot 4 (langchain4j/langchain4j#6236) - replaced with plain `langchain4j-ollama` and explicit `ChatModel` beans; added the missing `camel-yaml-dsl-starter`. - **Working trace export**: Micrometer Tracing + OTel bridge (`spring-boot-micrometer-tracing-opentelemetry`, `micrometer-tracing-bridge-otel`, `opentelemetry-exporter-otlp`), so Camel route spans and the `gen_ai.*` observation spans land in the same VictoriaTraces trace. The previous `otel.exporter.otlp.*` properties were not read by anything (see CAMEL-24570 for making that silent fallback visible). - **Two models, per-model observability**: two routes call two small Ollama models so every metric/span carries a distinct `gen_ai.request.model`. - **Perses GenAI dashboard**: `perses-genai-dashboard.json` + README instructions to create it via the Perses API (`/projects/camel_genai/dashboards/overview`), with screenshots and a short guide to reading the panels (e.g. the thinking model's ~2K output tokens per call vs a few dozen for llama3.2). Verified end-to-end on the live stack: metrics scraped by Prometheus, per-model series on the dashboard, `gen_ai` spans in VictoriaTraces for both models. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
