give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Control Center restarted about 50 times in the last 15h    {noformat}  [<USER>lsst-bastion01 ~]$ kubectl get pods -n cp-helm-charts  NAME                                                 READY   STATUS    RESTARTS   AGE  cp-helm-charts-cp-control-center-7d9487cbd9-smg4w    1/1     Running   49         15h  {noformat}      From the logs it looks like the reason was that one of the brokers was down:    {noformat}  [main] INFO io.confluent.admin.utils.ClusterStatus - Expected 3 brokers but found only 2. Trying to query Kafka for metadata again ...  {noformat}    And that put Control Center in a state where it was indefinitely trying to rebalance the topics and then restarting    {noformat}  [2020-06-02 16:25:55,322] INFO tocheck=[Store{name=monitoring-aggregate-rekey-store, rollup=false}, Store{name=group-aggregate-store, rollup=true}, Store{name=KSTREAM-OUTERTHIS-0000000104-store, rollup=false}, Store{name=MetricsAggregateStore, rollup=false}, Store{name=TriggerEventsStore, rollup=false}, Store{name=AlertHistoryStore, rollup=false}, Store{name=MonitoringStream, rollup=true}, Store{name=KSTREAM-OUTEROTHER-0000000105-store, rollup=false}, Store{name=MonitoringMessageAggregatorWindows, rollup=true}, Store{name=MonitoringVerifierStore, rollup=false}, Store{name=MonitoringTriggerStore, rollup=false}, Store{name=TriggerActionsStore, rollup=false}, Store{name=Group, rollup=true}, Store{name=aggregatedTopicPartitionTableWindows, rollup=true}, Store{name=aggregate-topic-partition-store, rollup=false}] (io.confluent.controlcenter.streams.KafkaStreamsManager)  [2020-06-02 16:25:55,322] INFO streams in state=REBALANCING (io.confluent.controlcenter.streams.KafkaStreamsManager)  [2020-06-02 16:25:55,322] INFO tocheck=[Store{name=monitoring-aggregate-rekey-store, rollup=false}, Store{name=group-aggregate-store, rollup=true}, Store{name=KSTREAM-OUTERTHIS-0000000104-store, rollup=false}, Store{name=MetricsAggregateStore, rollup=false}, Store{name=TriggerEventsStore, rollup=false}, Store{name=AlertHistoryStore, rollup=false}, Store{name=MonitoringStream, rollup=true}, Store{name=KSTREAM-OUTEROTHER-0000000105-store, rollup=false}, Store{name=MonitoringMessageAggregatorWindows, rollup=true}, Store{name=MonitoringVerifierStore, rollup=false}, Store{name=MonitoringTriggerStore, rollup=false}, Store{name=TriggerActionsStore, rollup=false}, Store{name=Group, rollup=true}, Store{name=aggregatedTopicPartitionTableWindows, rollup=true}, Store{name=aggregate-topic-partition-store, rollup=false}] (io.confluent.controlcenter.streams.KafkaStreamsManager)  [2020-06-02 16:25:55,322] INFO streams in state=REBALANCING (io.confluent.controlcenter.streams.KafkaStreamsManager)  [2020-06-02 16:25:56,322] INFO tocheck=[Store{name=monitoring-aggregate-rekey-store, rollup=false}, Store{name=group-aggregate-store, rollup=true}, Store{name=KSTREAM-OUTERTHIS-0000  {noformat}    It was not evident from Argo CD that one of the brokers had problems and since we didn't have Control Center to monitor the cluster health it took me some time to realize the real cause of the problem.    Having problems to restart the failing broker:    {noformat}    $ kubectl logs cp-helm-charts-cp-kafka-0 -c cp-kafka-broker -n cp-helm-charts -f    [2020-06-02 16:33:46,790] INFO Opening socket connection to server cp-helm-charts-cp-zookeeper-headless/10.32.6.96:2181. Will not attempt to authenticate using SASL (unknown error) (org.apache.zookeeper.ClientCnxn)  [2020-06-02 16:33:46,790] INFO Socket connection established to cp-helm-charts-cp-zookeeper-headless/10.32.6.96:2181, initiating session (org.apache.zookeeper.ClientCnxn)  [2020-06-02 16:33:46,790] INFO Unable to read additional data from server sessionid 0x100195099430001, likely server has closed socket, closing socket connection and attempting reconnect (org.apache.zookeeper.ClientCnxn)  {noformat}    "
Answer: 3150.0