Template updates and Zabbix v4.4

HIGHLIGHTS

Changes made to the Soliant Zabbix templates:

• Updated to Zabbix v4.4 format.
• Improved how DMP files are tracked.
• Fixed occasional collection of old FileMaker Server log entries.
• Corrected monitoring of FMC processes, per @kwalex's pull request.

N.B.

• Be advised that, if you are making manual changes to items, certain types of item changes will result in the removal of previously-collected data. For example, changing an item type or unit will do this.
• The Admin API items no longer work with FileMaker Server 17, because the FMS 17 Admin API trial has expired.

DETAILS:

Changes made to the "Soliant FMS WinMacFMC" template

• Added "mode=skip" parameter to all log items, so that older log entries are skipped. Zabbix would occasionally collect older log entries, and this change will hopefully prevent that from occurring.
• Triggers that used to use the "Log - Event - Errors only" or "Log - Event - Errors & Warnings only" item now use the "Log - Event" item.
• Changed "Log - Event - Errors only" and "Log - Event - Errors & Warnings only" items to be dependent on the "Log - Event" item, so that the agent has to read Event.log only once.
• Changed "FMS DMP Timestamp" item Type from "Text" to "Numeric (unsigned)" and Units from empty to "unixtime". Added JavaScript preprocessing to convert value from text to Unix time.
• Changed "DMP file detected" trigger problem expression to consider value age in addition to value change. A problem event will now be created only if the DMP file was created within the last 24 hours. Zabbix would occasionally send notifications based on a DMP file that was created a long time ago, and this change is intended to prevent that from occurring.
• The age check will compare the DMP timestamp, which uses the host time zone, with the Zabbix server current time. Those two machines could be using different time zones, but that difference would never be more than 24 hours.
• Changed "FMS fmsadmin list clients" and "FMS fmsadmin list files" item intervals from 1m to 10m.
• Created "Log - ClientStats" item.

Changes made to multiple templates to fix occasional collection of old FileMaker Server log entries

The following changes were made, because the "log" item key occasionally incorrectly retrieved old Event.log entries, causing the associated triggers to send out false-positive notification alerts. The "eventlog" item key has a couple of quirks of its own: It only works with Windows, it seems to occasionally collect log entries twice, and the local timestamp for the collected log entries is slightly off. But this faulty behavior is much preferred to the false-positives from the "log" item key.

• Recreated the following ITEMS in the "Soliant FMS MacFMC" template in the exact same way as they existed in the "Soliant FMS WinMacFMC" template:
  • Log - Event
  • Log - Event - Errors only
  • Log - Event - Errors & Warnings only
• Disabled the following ITEMS in the "Soliant FMS WinMacFMC" template. We will probably remove these eventually if the newly created items in the "Soliant FMS MacFMC" template work well (see above).
  • (same list as above)
• Created the following ITEMS in "Soliant FMS Windows" template. These use the "eventlog" item key instead of "log". The "errors" and "errors & warnings" items were not made dependent on the first item, because preprocessing cannot filter on log severity.
  • (same list as above)
• Recreated the following TRIGGERS in the "Soliant FMS MacFMC" template in the exact same way as they existed in the "Soliant FMS WinMacFMC" template:
  • Database Server process has terminated abnormally
  • Database was not closed properly
  • Progressive backup issue
  • FMS process {{ITEM.VALUE}.regsub("^.\t([a-zA-Z ]) process .*$", "\1")} has terminated abnormally
  • FileMaker Script Engine (FMSE) process has terminated abnormally
  • Possible consistency check issue
  • Event log error
  • Event log warning
• Disabled the following TRIGGERS in the "Soliant FMS WinMacFMC" template. We will probably remove these eventually if the newly created triggers in the "Soliant FMS MacFMC" template work well (see above).
  • (same list as above)
• Created the following TRIGGERS in "Soliant FMS Windows" template. These triggers had to use different problem expressions, because the item data collected by the "eventlog" item key is formatted differently.
  • (same list as above)

Changes made to multiple templates to correct monitoring of FMC processes

Summary:

• @kwalex pointed out a problem with the "FMS Process" items (and associated triggers) in the MacFMC template. In FMC, (1) the fmscwpc, fmwipd, and fmsased processes run under the fmsase user, and (2) the fmsib process doesn't exist at all. We needed to add the fmsase user to the ps command for FMC, but that broke the command on macOS. So we ended up splitting out these items/triggers into Mac and FMC versions.

Detail:

• Changes made to "Soliant FMS MacFMC" template:
  • Disabled these items:
    • All FMS Processes
    • All FMS Processes: FMS Process CWP
    • All FMS Processes: FMS Process Data API
    • All FMS Processes: FMS Process Database Engine
    • All FMS Processes: FMS Process Progressive Backups
    • All FMS Processes: FMS Process Scripting Engine
    • All FMS Processes: FMS Process Wrapper
  • Disabled these triggers:
    • FMS process not running - Data API - macOS / FMC
    • FMS process not running - fmserver - macOS / FMC
    • FMS process not running - Progressive Backups - macOS / FMC
    • FMS process not running - Script Engine - macOS / FMC
    • FMS process not running - WPE - macOS / FMC
• Changes made to "Soliant FMS Mac" template:
  • Added these items:
    • All FMS Processes
    • All FMS Processes: FMS Process CWP
    • All FMS Processes: FMS Process Data API
    • All FMS Processes: FMS Process Database Engine
    • All FMS Processes: FMS Process Progressive Backups
    • All FMS Processes: FMS Process Scripting Engine
    • All FMS Processes: FMS Process Wrapper
  • Added these triggers:
    • FMS process not running - Data API
    • FMS process not running - fmserver
    • FMS process not running - Progressive Backups
    • FMS process not running - Script Engine
    • FMS process not running - WPE
• Changes made to "Soliant FMS FMC" template – did not add item & trigger for Progressive Backups since that process doesn't run on FMC:
  • Added these items:
    • All FMS Processes
    • All FMS Processes: FMS Process CWP
    • All FMS Processes: FMS Process Data API
    • All FMS Processes: FMS Process Database Engine
    • All FMS Processes: FMS Process Scripting Engine
    • All FMS Processes: FMS Process Wrapper
  • Added these triggers:
    • FMS process not running - Data API
    • FMS process not running - fmserver
    • FMS process not running - Script Engine
    • FMS process not running - WPE

Initial release

Initial release that includes Zabbix templates to monitor FileMaker Server for all three platforms. Also includes two scripts (Python and PowerShell) used by the Zabbix agent as a custom UserParameter and a Notepad++ language file for syntax color-coding of Zabbix agent configuration files.