Page tree

Versions Compared

Key

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

...


Event Description

Details

Severity/Demand


FIXEdge lifecycle events


1

Application is being to be started and the log system is initialized

FIXEdge generates AppStarting event

Minor

2

Properties are loaded and sessions are run

FIXEdge generates AppStarted event

Minor

3

All components of the application were started

Detect application start moment

FIXEdge generates AppReady event

Major

4

Application is crashed

Some crashes can't be captured

FIXEdge generates AppFailed event

Critical 

5

Signal SIGINT or SITERM is detected

Detect manual termination of the process with signals SIGINT and SIGTERM 

FIXEdge generates AppSigTermDetected event

Major

6

Application is being to shut down (stop sessions / destroy objects)

FIXEdge generates AppShutdown event

Minor

7

All work is done, stopped as planned

Detect graceful termination of FIXEdge

FIXEdge generates AppComplete event

Major


Other important events that can be found in the logs and worth to be monitored


8

The gap in sequence numbers and Resend request from FIXEdge


Major

9

Validation errors


Minor

10

Session level rejects


Minor

11

Mass disconnections

Simultaneously disconnection of multiple sessions.

Critical

12

Any other errors and warnings


Minor

13

Any FATAL record.


Critical

14

License is expired


Critical

Integration with Windows Events Log and Linux Syslog

FIXEdge raises events in the Windows Events Log or writes information about critical failures to Syslog in Linux if the other ways of logging is not available.

For example:

  1. FIXEdge initialization failed.
  2. Logging is not permitted
  3. Logging is failed due to not enough space.

FIXICC Monitoring and management

...