-
Notifications
You must be signed in to change notification settings - Fork 5
node events
Thomas Hirsch edited this page Jun 14, 2016
·
1 revision
The basic format of the event MONROE.META.NODE.EVENT follows the following syntax:
''MONROE.META.NODE.EVENT <JSON>''
With the JSON dictionary containing these fields:
- EventType
- Timestamp
- SequenceNumber
- DataId
- DataVersion
It accepts a number of JSON dictionaries on stdin, and will send one event message per line of input to the metadata exporter. All of the above field, but the EventType, will be added by the metadata exporter.
The following messages and events are implemented in the MONROE nodes:
EventType | Meaning | Extra keys |
---|---|---|
Watchdog.Failed | The system watchdog detected an error symptom | message |
Watchdog.Repaired | The system watchdog resolved the issue | message |
Watchdog.Status | Periodic status messages from the watchdog | message |
Maintenance.Start | An interactive login on the node is registered | user |
Maintenance.Stop | The interactive login session is closed | user |
System.Halt | System halt is requested | |
Scheduling.Started | The node starts to query the scheduling server |
The following messages and events are requested (work in progress, consider these examples):
EventType | Meaning | Extra keys |
---|---|---|
Scheduling.Stopped | The node stops to query the scheduling server, no new experiments are scheduled | |
Scheduling.Aborted | All running experiments are about to be stopped, the node is in maintenance mode |