-
Story
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
OCPSTRAT-554 - Improving error handling, propagation, collection, and disambiguation for users
-
-
-
MCO Sprint 242, MCO Sprint 243, MCO Sprint 244
-
0
-
0.000
We want to allow customers to customize their metrics. In order to do that, it will be easier if they were gathered in one controller for collection.
With the introduction of the state controller, a huge change will be taken place in the way that MCO reports its telemetries. Originally, the metrics are updated separately in each MCO sub-component by directly write to Prometheus label. All updated metrics need to be collected by the state controller and reported afterwards. As a result, we will need to upgrade current metric update method live in the state controller.
2023/10/04 Update :
- Message bus = eventing work collected in
MCO-894 - Done by the end of sprint 242 and demo-ed in https://drive.google.com/file/d/10Ak3Wb7x7x4HKSDqnXJtliyywG0uDQiY/view
- Implementations need to be redone due to a design change in https://issues.redhat.com/browse/MCO-751
- is blocked by
-
MCO-812 Create proper types for the machineconfiguration object in the operator/v1 group
- Closed
-
MCO-751 Design an eventing system
- Closed
-
MCO-827 Inter-pod Communication (MCO <--> state controller)
- Closed
- split from
-
MCO-134 Centralize/standardize metrics registration/handler startup and teardown
- Closed
- split to
-
MCO-829 Implement service communications for controller/daemon/operator to talk metrics to the state controller
- Closed
-
MCO-894 Update current metric update method to event messages
- Closed
- links to