-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
Management Fabric Signal Monitor Enablement
-
Quality / Stability / Reliability
-
False
-
-
False
-
Unset
-
In Progress
-
CRCPLAN-385 - Management Fabric | Business and Operational Metric Collection
-
25% To Do, 25% In Progress, 50% 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
Description of what we're building, the end goal and how we'll go about it.
This epic covers the stories required to put the signal monitor process into effect for the management fabric. This includes any functional aspects for debugging such as means to accessing to data in production.
Acceptance Criteria
- The management fabric signal monitor process is documented (see CIR-004)
- Sufficient production data access is in place and can be leveraged by management fabric engineers
- A general troubleshooting/responsibilities doc has been created for signal monitoring
- Expected tasks, helpful links, how to access databases in prod, how to access spicedb in prod, etc.
- This doc does not need to be exhaustive from the start, we can iterate and add as we find gaps post-implementation
- All Kessel teams have a signal monitoring rotation and automation (e.g. PagerDuty) in place
- The signal monitoring process for all Kessel teams has been kicked off
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | N | |
ADR Required?
|
N | |
Testing plans
|
N | |
Known dependencies?
|
N |
Open Questions
Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.