There are two likely explanations for this.
- OpsCenter stores some of the information on the cluster being monitored (by default). Depending on the replication strategy and replication factor of the OpsCenter keyspace, the timestamp in question may have been in a partition managed by the down node.
- Something to do with the restart may have temporarily disrupted the agent component that monitors and stores the information resulting in that information not being captured.
1 seems most likely given that the blue node metrics resume while the orange node metrics suggest the orange node is still down. If 1 is the case, then the data will be delivered to the orange node (via hinted handoffs) and become available once that node finishes rebooting. The graph should show the updated values after that, although refreshing the UI may be required. More nodes would make this kind of failure less likely, and a higher RF would make it very unlikely (practically impossible).
If time and refreshing the UI do not resolve the gap, then 2 is the most likely culprit and could be indicative of a bug in the metric recording mechanism. It would be worthwhile reporting it as such.