Thanks for the response.
Let me share some more details. Our setup is standalone redis with master and slave. The monitoring will periodically (i.e. every 5 secs) query the redis server to check the health. In case of continuous monitoring failures, the slave will take over as a master.
As I mentioned, If the redis is unresponsive (busy/hung), then monitoring queries can fail. Just wondering, if we could distinguish then the failover can be avoided in case of redis busy (slow/blocking command or other operations). Even if someone ran such commands in production mistakenly.
We also monitor the slow logs, redis calls response time and other parameters (connection, eviction, etc). Actions will be taken accordingly. The slow log will have a commands history. To handle the above case, I am looking for the redis server state at that moment (if possible).