Ga naar hoofdinhoud

VBScript Event Monitor Reference Guide

Overview​

The VBScript Event Monitor is a scripting event monitor by PIM+ that enables integration of custom VBScript actions into the monitoring, scheduling, and alerting engine. Scripts can range from simple to complex, directing PIM+ to generate specific statuses, event texts, and graph data points.

Use Cases​

  • Custom Scripting: Utilize VBScript to write custom scripts for targeted monitoring activities.

Monitoring Options​

Script​

  • Script Input: Insert your VBScript into the designated text area within the event monitor settings. The script executes on the PIM+ system, incorporating necessary network communication features.

Tokens​

  • Available Tokens: Utilize tokens replaced dynamically during script execution:
    • %%devicename%% - Device name being monitored.
    • %%displayname%% - Display name of the device.
    • %%devicegroup%% - Group name of the device.

Output Requirements​

  • Standard Output Format: Script output guides the event monitor's actions:
    • Success(devicename)=Custom message - Indicates successful monitoring with a custom message.
    • Example: Success(www.pim+.com)=Successfully verified page content on the website.

Multi-Line Output​

  • Extended Output: Scripts can output detailed multi-line text using tokens to format event text:
    • Example: Success(www.pim+.com)=The following website checks succeeded: Verified response time. Check page content.

Status Levels​

  • Event Statuses: Scripts can trigger various status levels:
    • Success(hostname)=All checks completed successfully.
    • Info(hostname)=You might want to look at this.
    • Warning(hostname)=Something went a little bit wrong.
    • Error(hostname)=Something went very wrong.
    • Critical(hostname)=OMG, the server is on fire.

Authentication and Security​

  • Execution Context: The script runs on PIM+'s console or a remote node. Scripts accessing network devices need appropriate credentials.

Data Points​

  • The data points generated by any scripting event monitor depend on the custom monitoring action it performs.