Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently, the lifecycle of many components, including the MetricsReporter is tied to the container lifecycle. Due to this, StreamProcessor/JobCoordinator will need to manage their own metrics registry and reporters.
In order to unify the stack, the ideal place for metricsReporter lifecycle will be in the user-facing apis - LocalContainerRunner & LocalApplicationRunner. Every component will simply register its metrics to the reporter dynamically. Iiuc, the MetricsReporter can implement a ReadableMetricsRegistryListener interface to register metrics dynamically.
Attachments
Issue Links
- depends upon
-
SAMZA-1153 Metrics should be added for ZK based JobCoordinator
- In Progress
- is related to
-
SAMZA-1276 SamzaContainer does not take into account the custom metrics reporter passed by streamprocessor
- Resolved