Integrates custom actions into your monitoring configuration using JavaScript.
The Javascript Event Monitor is one of FrameFlow's scripting event monitors that lets you integrate custom monitoring actions into our monitoring, scheduling and alerting engine. Scripts can be as simple or complex as you choose. They can tell FrameFlow not only what status and event text to generate, but also generate graph data points which will populate graphs throughout the FrameFlow interface.
This event monitor provides the following options:
Use this option to get alerts if FrameFlow could not contact the selected device.
Use this option to get alerts when CPU usage exceeds the thresholds that you specify.
Use this option to set alerting thresholds based on the number of files found in the directory.
Use this option to get alerts about systems whose disk or partition space is running low. In the option to ignore specified drives, use the following format: "deviceName(C)" (without the quotes). You can use the * character to match multiple devices or drives. For example, use "devicename(*)" to ignore all drives on a device. Use "x*(D)" to ignore the D: drive on all devices whose names start with x. To specify multiple drives to ignore, separate them with commas, for example, "device1(G), device2(F)".
Use this option to generate alerts based on how much physical memory is in use on each network device.
Use this option to alert based on the observed ping response time for the device.
This option lets you generate alerts based on the total bandwidth rate for the device. This rate is the sum of all incoming and outgoing bandwidth on all interfaces.
This option lets you generate alerts based on the combined outgoing bandwidth rate of all interfaces.
This option lets you generate alerts based on the combined incoming bandwidth rate of all interfaces.
The default port number of SSH connections is 22. If your servers are using a non-standard port, you can specify it here.
Your script will run on the FrameFlow main console (or on the remote node in a multi-site configuration). If the script accesses other network devices, it will require credentials with sufficient rights to perform its task.
The data points generated by any scripting event monitor depend on the custom monitoring action it performs.
To view the tutorial for this event monitor, click here.
Add a comment