-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
Tracing capabilities to Management Fabric
-
Quality / Stability / Reliability
-
False
-
-
False
-
Unset
-
To Do
-
CRCPLAN-325 - Management Fabric | Kessel Service GA Requirements (SRE, Security, etc.)
-
100% To Do, 0% In Progress, 0% Done
-
-
Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.
Summary and goal
For better observability and debugging, we'd benefit from tracing capabilities within Management Fabric components (and for the whole HCC when running in that environment).
The use of Dynatrace may/should help us there.
It is not a hard requirement to go to production, but would be beneficial if we can add tracing support at some point
Acceptance Criteria
- We're able to follow a trace from the Public API though the stack (including databases)
- We're able to know the time spent in each part of the stack
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | Y | We may depend on Dynatrace usage, ideally the trace would start from the web browser when in use. |
ADR Required?
|
Y / N | Possibly |
Testing plans
|
N | |
Known dependencies?
|
Y / N |
Open Questions
Would Dynatrace make this easy ?
Return On Investment, largely depend on how much time we'd need to have tracing in place.