-
Epic
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
None
-
ACM: support Tempo in MCOA
-
1
-
False
-
None
-
False
-
Not Selected
-
To Do
-
100% To Do, 0% In Progress, 0% Done
Currently, ACM users are required to send all traces to a central location, which may not be suitable for all use cases. To address this, we need to provide flexibility in trace storage, allowing users to retain a subset of their traces locally within spoke clusters. This enhancement involves integrating Tempo, a distributed tracing backend, with the MCOA (Multicluster Observability Addon).
User story
As an ACM user, I want the option to store selected traces locally in my spoke clusters using Tempo, so that I can manage data locality according to my operational or regulatory requirements.
Acceptance Criteria
- Users can configure the storage of traces either centrally, locally, or both, using a clear and simple configuration interface.
- Ensure that traces stored locally are accessible and manageable similar to those sent to the central storage.
- relates to
-
ACM-12063 Multi-signal Observability Storage, Collection and Query Support in ACM
- New