Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Activity Type:
Product / Portfolio Work
Story Points:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Link:
Secure Tempo query and ingest APIs
Git Pull Request:
https://github.com/openshift/openshift-docs/pull/88120
Intelligence Requested:
Market:

Sprint:
Tracing Sprint # 266

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

On installation page:

replace minimal TempoStack and TempoMonolithic with multi-tenant deployment on installation page
add new section for OTEL collector (mandatory for multi-tenant deployments)
The OTEL deployment should include all recommended and required components - RED metrics, k8sattributes processor

is documented by

OBSDOCS-1676 [blocker][TRACING-4847,TRACING-4649] Tempo-OTel Multitenancy documentation improvements

Closed

is duplicated by

TRACING-4829 Document a recommended deployment example

Closed

links to

openshift/openshift-docs#88120: Refactor Tempo Multitenancy section

Assignee:: Ruben Vargas Palma

Reporter:: Ruben Vargas Palma

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/09/02 3:36 AM

Updated:: 2025/08/29 9:12 PM

Resolved:: 2025/02/17 4:31 AM