[
https://issues.apache.org/jira/browse/CAUSEWAY-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066726#comment-18066726
]
Andi Huber commented on CAUSEWAY-3975:
--------------------------------------
We'll be using `spring-boot-starter-opentelemetry`.
See blog: [https://spring.io/blog/2025/11/18/opentelemetry-with-spring-boot]
To quickly get started one needs a backend, that can receive telemetry data.
Like e.g. dockerized _Jaeger_:
```
docker run --rm --name jaeger \
-p 16686:16686 \
-p 4317:4317 \
-p 4318:4318 \
-p 5778:5778 \
-p 9411:9411 \
cr.jaegertracing.io/jaegertracing/jaeger:2.16.0
```
See also https://www.jaegertracing.io/docs/2.16/getting-started/
To connect your App with the telemetry data backend, _Spring_ needs to know
where to send telemetry data to, this is done via configuration.
Something like:
```
management:
tracing:
sampling:
probability: '1.0'
otlp:
tracing:
endpoint: http://MY_ENDPOINT:4318/v1/traces
```
> Open Telemetry Integration
> --------------------------
>
> Key: CAUSEWAY-3975
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3975
> Project: Causeway
> Issue Type: New Feature
> Components: Core, Viewer Wicket
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 4.0.0
>
>
> There might be n+1 issues with Wicket Viewer, when rendering table contents
> or Select Dropdown content. Ideally we would query the persistence store only
> as little as absolutely required. Which suggests that it would be helpful to
> have some critical probing points within the framework where we allow for
> collecting profiling data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
