Ad Widget

Collapse

RAM full / Agent down - No notification

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • hoffCM
    Junior Member
    • May 2022
    • 3

    #1

    RAM full / Agent down - No notification

    Hi Guys
    We use Zabbix for a few servers for monitoring, and everything works fine, but with one Windows Server we always run into issues.

    What happens is:
    -> On some point RAM/Memory is full (less than 1MB available)
    -> ZBX Agent turns "RED"

    I don't know what happens first, but those two things happen. What caused the memory issue is another topic, but my problem is that i don't get any notification. I could understand if the Agent dies because of not enough memory, but shouldn't i not get at least a message that the Agent is not responding on the Server?

    As it is now this scenario above happens and we don't get any more data into Zabbix but we only learn about it when we realize that the server doesn't work properly anymore, but not through Zabbix.

    As you see on the image below we should get an info because of our configured trigger when this happens...

    Thanks!!!!

    Click image for larger version

Name:	2022-05-16_10-37-54.png
Views:	189
Size:	21.2 KB
ID:	444634
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1782

    #2
    Add an agent.ping item to your Windows servers (/templates), and then use nodata() to trigger a problem then the agent does not communicate with the server/proxy anymore.

    Example trigger (in Zabbix 5.4/6.0 syntax):

    nodata(/Template-OS-Windows-noservices/agent.ping,{$T_ZABBIXAGENT_TIMEOUT})=1

    where I have the template-level macro {$T_ZABBIXAGENT_TIMEOUT} by default set to 2m (can then be overridden in the hosts if needed).

    Markku

    Comment

    • hoffCM
      Junior Member
      • May 2022
      • 3

      #3
      Thanks Markku!!!!

      Comment

      Working...