The template included uses active checks. Your zabbix agent must be configured for active checks otherwise the server won't receive any data.
Description
This template is designed to automatically interpret the latest created minidumps (after a BSOD restart) using windows debugger and send you the report over email via zabbix actions.
The report will usually give you an explanation for the BSOD, the driver that caused it and the stack trace.
Usage
Download the archive, extract the XML template, import it into the frontend and link the hosts to it. This template uses trapper items, so make sure you have them enabled on your zabbix server (enabled by default).
Copy the vbs scripts to your zabbix agent folder and configure the following line in your zabbix_agentd.conf file, replacing the path in the UserParameter with your zabbix agent installation path, restart the agent.
Make 2 folders in you zabbix agent installation path: windbg64 and windbg32.
Go to microsoft.com, download and install Windows Debugger, both the 32bit and the 64bit versions. There was a good time when the debugger was a small standalone package of 15MB available for download. Now it's only available as part of the windows SDK and you need to download the whole crap to install just the debugger (use the windows 7 sdk if you can).
I managed to salvage a copy of the 64bit standalone package at: http://www.filefactory.com/file/5q72...6_11_1_404_msi
The debugger should install in something like "Program Files\Debugging Tools for Windows (x64)" for the 64bit version and in "Program Files (x86)\Debugging Tools for Windows" for the 32bit version. Go ahead and copy contents of those folders to the windbg64 and windbg32 folders, each for their respective bitness. You should now have kd.exe in each of the windbg64 and windbg32 folders.
You can distribute these folders to you zabbix hosts without having to install the windows debugger on each of them.
Gotchas
The bugcheck triggers send an alert containing information on the most recent minidumo analisys. For these to show up in the alert make sure you include the following macros in the alert message:
Eventlog info: {ITEM.LASTVALUE}
The template contains 2 triggers that check that autorestart is enabled after a BSOD and that the memory dump type for the host is a minidump.
Description
This template is designed to automatically interpret the latest created minidumps (after a BSOD restart) using windows debugger and send you the report over email via zabbix actions.
The report will usually give you an explanation for the BSOD, the driver that caused it and the stack trace.
Usage
Download the archive, extract the XML template, import it into the frontend and link the hosts to it. This template uses trapper items, so make sure you have them enabled on your zabbix server (enabled by default).
Copy the vbs scripts to your zabbix agent folder and configure the following line in your zabbix_agentd.conf file, replacing the path in the UserParameter with your zabbix agent installation path, restart the agent.
Code:
#bugcheck UserParameter = bugcheck[*],cscript "C:\Program Files\Zabbix agent\zabbix_win_bugcheck.vbs" //Nologo "$1"
Go to microsoft.com, download and install Windows Debugger, both the 32bit and the 64bit versions. There was a good time when the debugger was a small standalone package of 15MB available for download. Now it's only available as part of the windows SDK and you need to download the whole crap to install just the debugger (use the windows 7 sdk if you can).
I managed to salvage a copy of the 64bit standalone package at: http://www.filefactory.com/file/5q72...6_11_1_404_msi
The debugger should install in something like "Program Files\Debugging Tools for Windows (x64)" for the 64bit version and in "Program Files (x86)\Debugging Tools for Windows" for the 32bit version. Go ahead and copy contents of those folders to the windbg64 and windbg32 folders, each for their respective bitness. You should now have kd.exe in each of the windbg64 and windbg32 folders.
You can distribute these folders to you zabbix hosts without having to install the windows debugger on each of them.
Gotchas
The bugcheck triggers send an alert containing information on the most recent minidumo analisys. For these to show up in the alert make sure you include the following macros in the alert message:
Eventlog info: {ITEM.LASTVALUE}
The template contains 2 triggers that check that autorestart is enabled after a BSOD and that the memory dump type for the host is a minidump.