Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

Following are all currently supported events explained with their included data and formats. Events are widely used internally as well as within extension like the Data Exporter.

Events are triggered by the monitoring process and can then lead to further actions, such as exporting the event information into an external file.

Data Types

All rows are of data type "string", except:

NameData Type
timestampUNIX timestamp
start_timeUNIX timestamp
end_timeUNIX timestamp
triesinteger, possible values: number of tries
notification_numberinteger, possible values: number of sent notifications
is_fixedinteger, possible values: 0, 1
is_persistentinteger, possible values: 0, 1
triggered_byinteger, possible values: downtime_id
durationinteger, possible values: duration in seconds

NOTE: The 'host_name' and/or 'service_name' are the unique identifiers for each event and the events are related to each other through this id. Except for 'CONFIG CHANGE' which has no relation to any other event.

Events

The different possible event types with examples are listed below.

SERVICE_ALERTRows:

SERVICE_ALERT

Filename: service_alert.csv

::
Rowstimestamphost_nameaddressservice_namestatustypetriesoutputperfdatadowntime

hostgroup_name

 

Data typeUNIX timestampstringstringstringstringstringintegerstringstringinteger

string

 

Example1334580082azeti-VRH01192.168.120.10perf_trendWARNINGSOFT1(numeric growth: 0.979 gallons) in the last 60 minutes for service: Agent_based_CPU_Checkdiff=6.18654421367486gallons;5;11;1everyhost

HOST_ALERT

Filename: host_alert.csv

:::
Rowstimestamphost_nameaddressstatustypetriesoutputperfdatadowntime

hostgroup_name

 

Data typeUNIX timestampstringstringstringstringstringintegerstringinteger

string

 

Example1336099678Plugin_Development192.168.120.18WARNINGSOFT1OK - 192.168.120.18 responds to ICMP. Packet 1, rta 19.330mspkt=1;;0;2 rta=19.330;1000.000;2000.000;;1everyhost

HOST_NOTIFICATION

Rows:

Filename: host_notification.csv

::
Rowstimestamphost_namecontact_namestatustypenotification_numberoutput

script_name

 

Data typeUNIX timestampstringstringstringstringintegerstring

string

 

Example1327593012Linksys-Routerdevtest@azeti.netDOWNPROBLEM397HOST IS DOWN RIGHT NOWhost-notify-by-email

SERVICE_NOTIFICATION

Rows:

Filename: service_notification.csv

::
Rowstimestamphost_namecontact_nameservice_namestatustypenotification_numberoutput

script_name

 

Data typeUNIX timestampstringstringstringstringintegerstringstring

string

 

Example1327593012vCenter01devtest@azeti.netAgent_based_Memory_CheckCRITICALPROBLEM143azeti Agent - ERROR: Wrong passwordhost-notify-by-email

ADMIN_NOTIFICATION

:::
Rowstimestamphost_namecontact_namesubject

output

 

Data typeUNIX timestampstringstringstring

string

 

Example1327680443192.168.96.24devtest@azeti.netExtension/Plugin Problem - Sonarplex 192.168.96.24License for Addon check_azetiplugin_esx_perf not available or expired

CONFIG_CHANGE

:::
Rowstimestampconfig_nameitem_namechange_type

contact_name

 

Data typeUNIX timestampstringstringstring

string

 

Example1327680619servicePing_Performance_Checkdeletedadmin@192.168.96.226

ACKNOWLEDGE_SVC_PROBLEM

:::
Rowstimestamphost_nameservice_nameis_stickynotification_numberis_persistantcomment_author

output

 

Data typeUNIX timestampstringstringintegerintegerintegerstring

string

 

Example1327683838vCenter01Agent_based_Memory_Check211AdministratorThresholds should be adjusted. Maintenance.

ACKNOWLEDGE_HOST_PROBLEM

:::
Rowstimestamphost_nameis_stickynotification_numberis_persistantcomment_author

output

 

Data typeUNIX timestampstringintegerintegerintegerstring

string

 

Example13276838383Com-Switch211AdministratorThe device is down due to a power supply failure, it is currently in repair.

REMOVE_SVC_ACKNOWLEDGEMENT

:::
Rowstimestamphost_name

service_name

 

Data typeUNIX timestampstring

string

 

Example1327662720vCenter01Agent_based_Memory_Check

REMOVE_HOST_ACKNOWLEDGEMENT

:::
Rowstimestamp

host_name

 

Data typeUNIX timestamp

string

 

Example1327662720vCenter01

SCHEDULE_AND_PROPAGATE_TRIGGERED_HOST_DOWNTIME

:::
Rowstimestamphost_namestart_timeend_timeis_fixedtriggered_bydurationcomment_author

comment_data

 

Data typeUNIX timestampstringUNIX timestampUNIX timestampintegerintegerintegerstring

string

 

Example1327680894vCenter011327680870133286847010†7200AdministratorHost is down for maintenance. Agent isn't running as well.

SCHEDULE_AND_PROPAGATE_HOST_DOWNTIME

:::
Rowstimestamphost_namestart_timeend_timeis_fixedtriggered_bydurationcomment_author

comment_data

 

Data typeUNIX timestampstringUNIX timestampUNIX timestampintegerintegerintegerstring

string

 

Example13275931663Com-Switch13275931501327600350113600AdministratorSomething went wrong with the DSL Link.

SCHEDULE_HOST_DOWNTIME

:::
Rowstimestamphost_namestart_timeend_timeis_fixedtriggered_bydurationcomment_author

comment_data

 

Data typeUNIX timestampstringUNIX timestampUNIX timestampintegerintegerintegerstring

string

 

Example13276638513Com-Switch1327663848132767104810†7200AdministratorOS upgrade, scheduled maintenance.

SCHEDULE_SVC_DOWNTIME

:::
Rowstimestamphost_namestart_timeend_timeis_fixedtriggered_bydurationcomment_author

comment_data

 

Data typeUNIX timestampstringUNIX timestampUNIX timestampintegerintegerintegerstring

string

 

Example13276627863Com-Switch132766277713276699770†0†7200AdministratorService downtime due to reconfiguration of device.
Note
NOTE: Unfortunately

Unfortunately there is currently a bug about the 'donwtime_id' field for the 'DEL ...' events. The id is not passed within the 'SCHEDULE ...' events, therefore the deletion of a downtime cannot easily be connected to a scheduling. This will be fixed in the future.

DEL_HOST_DOWNTIME

:::
Rowstimestamp

downtime_id

 

Data typeUNIX timestamp

integer

 

Example132766401915

DEL_SVC_DOWNTIME

:::
Rowstimestamp

downtime_id

 

Data typeUNIX timestamp

integer

 

Example13276629522