Events log (history)

The history model is used to maintain a log of the received checks results.

The Alignak backend stores all the checks results it receives to keep a full log of the system checks results.

../_images/log_history.png
Properties
Property Type Required Default Relation
_realm
objectid     realm
_sub_realm
boolean   True  
_users_read
objectid list     user
Concerned host identifier
objectid     host
Concerned host name
string      
Relate log chek result (if any)
objectid     logcheckresult
message
History event message
string      
schema_version
integer   1  
Concerned service identifier
objectid     service
Concerned service name
string      
History event type
string True check.result  
Concerned user identifier
objectid     user
Concerned user name
string      

host: ! Will be removed in a future version

host_name: The backend stores the host name. This allows to keep an information about the concerned host even if it has been deleted from the backend.

logcheckresult: This relation is only valid if the event type is a check result

service: ! Will be removed in a future version

service_name: The backend stores the service name. This allows to keep an information about the concerned service even if it has been deleted from the backend.

type:

Allowed values: [‘webui.comment’, ‘check.result’, ‘check.request’, ‘check.requested’, ‘ack.add’, ‘ack.processed’, ‘ack.delete’, ‘downtime.add’, ‘downtime.processed’, ‘downtime.delete’, ‘monitoring.external_command’, ‘monitoring.timeperiod_transition’, ‘monitoring.alert’, ‘monitoring.event_handler’, ‘monitoring.flapping_start’, ‘monitoring.flapping_stop’, ‘monitoring.downtime_start’, ‘monitoring.downtime_cancelled’, ‘monitoring.downtime_end’, ‘monitoring.acknowledge’, ‘monitoring.notification’]

user: ! Will be removed in a future version

user_name: The backend stores the user name. This allows to keep an information about the concerned user even if it has been deleted from the backend.