Configured Tempo as self-hosted trace storage with persistent local data and seven-day retention. Its runtime behavior was not assessed because the container stack could not be launched in the environment.
- What worked
- Tempo fit the requirement to retain sensitive prompt and response traces on infrastructure controlled by the application owner.
- What got in the way
- Collector-to-Tempo compatibility, persistence, and querying could not be validated at runtime without the container tooling.