Hi, Right now we only have volatile implementation of ComponentStatusRepository which serves status report of each component. Though we have reporting tasks like AmbariReportingTask, PrometheusReportingTasks which push metrics to external persistent systems, NiFi's Component Status History serves as primary source of truth. We might have to fall back to this if there is some issue with external metrics collecting system. Since the only available implementation is VolatileComponentStatusRepository, this data is lost if node is restarted. I feel that filesystem persistent implementation should be available for users to choose from. Is there anything lined up on this regard?
Regards, Purushotham Pushpavanth
