Misleading 'Is Agent Running' and 'Agent Jobs' statuses.

[JoeVizcaino]

From a previous discussion, I understand you use SQLAgent - Generic Refresher to test if SQL Agent Service is online.
If SQLAgent - Generic Refresher is not present in sys.dm_exec_sessions, DBADash reports it as not running and Agent Jobs also as not running.

I am looking at two servers right now in that state. However, the Agent is in fact running, and the jobs are firing at the scheduled time, all with no issues. No entries in SQL/Agent logs (I know the fix is to restart the Agent Service).

My question (and suggestion) is how do you determine the Agent Jobs state of Not Running? And, if the SQLAgent - Generic Refresher is not present, maybe do an additional step to check the actual state of the Agent Service. If the agent is running, I feel the alert should be yellow, a warning that a possible issue might be in play, not that the agent is not running (which is false). A hung state for the Generic Refresher does not a true indication of jobs not running and/or the agent is not running.

maybe I am going about this the wrong way, I feel the agent jobs status should not be tied to Is agent running at least not without actually checking.