Config Info
Name ConsecutivePingsMonitor
Version 1.0

About

In order not to interfere with existing configurations, "normal" Ping messages and "consecutive" ping messages are sent to the SmartConsole with a different Category. This can be useful for alerting so that no Repetition parameters need to be set in the alarn, making the configuration a bit less painful.

How to use it

  1. Import the monitor
  2. Edit the additional parameters : you can edit the Category used for consecutive error messages (default : Consecutive Pings) , and the threshold for consecutive error warnings.
  3. And that's all !

Configuration

The following parts can be configured :

CRITICAL / WARNING / MINOR_REPETITION
Define the color of "special" consecutive messages depending on the number of consecutive failures.
SEND_REPETITION_MESSAGES
Enable/disable the sending of repetition messages - Default is 1.
Category_Repetition
The Category used when repetition messages are sent. Useful for filtering

Messages sent

Messages sent by the monitor :

Monitor - TDESODT - Ping And Consecutive Pings

General

Property Value
ClassID TCPChecker.8
Description TDESODT - Ping And Consecutive Pings
GenerateHealthEvent 2
Name TDESODT - Ping And Consecutive Pings
RedirectHealthEvent 5

 

Script - Set Health Wizard

Additional Parameters

Name Type Value
CRITICAL_REPETITION Numeric 5
WARNING_REPETITION Numeric 4
MINOR_REPETITION Numeric 3
Category_Repetition String Consecutive Pings
SEND_REPETITION_MESSAGES Numeric 1

 

Pre-Group

if VSMScriptFirstEvent: ProblemCounter = 0 

Health Rules

Criticity Code
Critical PercentPingsOK <= 5
Warning (AvgTimePings > 4500) or (PercentPingsOK < 30)
Minor (AvgTimePings > 3000) or (PercentPingsOK < 50)
Success True

 

Health Actions

Criticity Code
Critical #if Critical, increment the counter

ProblemCounter +=1

Warning #not Critical, reset the counter

ProblemCounter = 0

Minor #not Critical, reset the counter

ProblemCounter = 0

Success #not Critical, reset the counter

ProblemCounter = 0

 

Templates

Criticity Code
Critical Could not access the device: Host: &Host Host Description: &HostDescription TimeOut: &PingTimeOut Error Code: &PingLastErrorCode Description: &PingLastErrorDescription
Warning Ping - SLA (Service Level Agreement) Violation in Ping Check: Host = &Host HostDescription = &HostDescription PercentPingsOK = &PercentPingsOK NumberPings = &NumberPings NumberPingsOK: &NumberPingsOK NumberPingsError: &NumberPingsError AvgTimePings = &AvgTimePings
Minor Ping - Minor error accessing the device: Host: &Host Host Description: &HostDescription TimeOut: &PingTimeOut Error Code: &PingLastErrorCode Description: &PingLastErrorDescription
Success Ping Check executed succesfully: Host = &Host HostDescription = &HostDescription PercentPingsOK = &PercentPingsOK NumberPings = &NumberPings AvgTimePings = &AvgTimePings

 

Sent Variables

ID Variable
VAR02 Host
VAR03 HostDescription
VAR04 PercentPingsOK
VAR05 NumberPings
VAR06 AvgTimePings

 

Post-Health

if ProblemCounter > 0: #handle repetitions tpltMsg = "&ProblemCounter consecutive Ping errors accessing the device: Host: &Host Host Description: &HostDescription TimeOut: &PingTimeOut Last Error: &PingLastErrorCode Description: &PingLastErrorDescription" health = SUCCESS if ProblemCounter == int(CRITICAL_REPETITION) : health = CRITICAL elif ProblemCounter == int(WARNING_REPETITION) : health = WARNING elif ProblemCounter == int(MINOR_REPETITION) : health = MINOR msgToSend = InstantiateMessage(tpltMsg) if health !=SUCCESS and SEND_REPETITION_MESSAGES : SendMessageToConfigurator(health,msgToSend) SendMessageToSmartConsole (health, msgToSend, Variables=VariablesTemplate, EventID=GetVMCMsgIdFromHealth(health ), Category=Category_Repetition) 

Datasource - Ping DataSource

General

Property Value
ClassID TCPChecker.8
Description  
ErrorRetryTime 60
IntervalRetries 10
Kind 0
Name Ping DataSource
Retries 2
SharingKind 1
Timer 60

 

Implementation

Property Value
PingBufferSize 64
PingNoFragment false
PingNumberPings 3
PingServerDescription TDESODT
PingServerIPName TDESODT
PingTimeOut 4000
PingTTL 60
PingVersion 100

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: October 18, 2018