GDS Alerts
Goto: Documentation Home | Technical Structure
Alerts are small messages that GDS is able to route and process within your network. They are designed to provide quick and easy notification type events, but are not guaranteed delivery. This makes them ideal for monitoring real time conditions on remote systems, but they are not suited to guaranteed transactional requirements; that is handled by standard GDS data writes.
SendAlert.exe
| Field/Read | Field/Write | Datatype | Description |
| f2 | f2_8 | Gid | Required constant "23,1,0,0,7,0,0,0". This identifies this packet as an alert record. |
| f100 | f100 | Number | Generating Application Code (see below) |
| f101 | f101 | Number | Event code. This code is allocated by each application. |
| f102 | Name | ||
| f103 | PID of creator | ||
| f104 | Reserved for presentation | ||
| f105 | Date/Time message received at server. this is not the time the message was created. | ||
| f110 | Number 1 | ||
| f119 | Creator IP as seen by server | ||
| f120 | Text 1 | ||
| f | |||
| f |
| 12 | Gnap.dll |
| 23 | BoxFrau |
| 31 | Fpos.dll, runtime errors |
| 32 | Fpos.dll, alert trace messages |
| 33 | Fpos.dll, general message, allocated in fpos.dll |
| 34 | Fdlcom.dll |
| 38 | GDS RptProcAgent.exe |
| 39 | GDS RptCommsAgent.exe |
| 99 | SendAlert.exe, default AppCode for user created messages. |
| 204 | Meetu4 application |
| 1 | Free disk space below required minimum | F120=Drive Letter, F110=Free space in Mb |
| 2 | Watchdog timer expiry | F110=Current watchdog interval in seconds, ie approx number of seconds until next watchdog is due. |
| 3 | Memory load percentage | F110=Memory Load |