EventLogger

EventLogger is one of the RET servers like GID.admin, GID.logs, GID.rates, ... which is configured to listen
message from various servers for statistic, monitoring and audit purpose.

Functionality
The EventLogger concurrently receives events from mutiple sources, local or remote.
There are Java/C++ APIs that allow other application to send events to the EventLogger
No password protection is required. Main reason is speed.
Events are defined by integer codes which imply a severity level, message format and list of
parameters e.g.

Event code: 1002

Severity: Information
Message: XXX on YYY - Connected to resource ZZZ
Parameters: XXX, YYY and ZZZ

Where
XXX is process
YYY is host
ZZZ is resource

Events received can be processed in multiple ways e.g. saved into files, sent as email, inserted into
database.

1
EventLogger

Event Format

Events sent to the event logger are a comma separated list of values:

LOGEVENTV,<value1>,<value2>,<value3>,...,<valueN>

where
The value1 is the event ID, normally a number
The value2 is the process name that sent the event
The value3 is the name of the host that sent the event
all other values are specific to the event to send

Installation
The binary files for event Logger locate at:
Sparc version : https://transactions.thomsonreuters.com/gr.aspx?Component=31
X86 version : https://transactions.thomsonreuters.com/gr.aspx?Component=14718
Get the up-to-date EventLogger message files from : https://transactions.thomsonreuters.com/
gr.aspx?Component=14637
extract to data folder in the system environment

systemRoot
|-- data
| |-- DBMessages.txt
| |-- DeviceMessages.txt
| |-- EchoFX.RICS.dat
| |-- EchoMM.RICS.dat
| |-- EchoMM.SPECIFICDATES.dat
| |-- EmailMessages.txt
| |-- EnsignMessages.txt
| |-- LOMS_maker_message_mapping.dat
| |-- StatMessages.txt
| |-- TivoliMessages.txt
| |-- appendix_a
| |-- calendar.dat
| |-- enumtype.def
| |-- factory.om_data.xml
| |-- factory.private_data.xml
| `-- reuters_dde_profile_ssl.dat

2
EventLogger

Download default EventLogger.ini from BizzBuzz here:https://transactions.thomsonreuters.com/

gr.aspx?Component=2047
the event logger is easy to install, in order to logging, at least, event into database, just change
the parameter under the following sections:
registry
GID.eventlogger
It is good pratice that resource name should be exactly GID.eventlogger as default logger
name in almost server is GID.eventlogger
Changing logger name to special other value, we have to make change the parameter:
LOGGER in server config file either e.g GID.orders

[server]
LOGGER=GID.eventlogger

DBLogger (supply db username/password)

########################################################################################
#
# Filename: EventLogger.ini
#
# PURPOSE Configure the EventLogger server
#
#######################################################################################

[registry]
REGISTRY_DETAILS=HOST:172.23.11.175,TYPE:SOCK_ROBUST,PORT:8888

[GID.eventlogger]
RESOURCE_DETAILS=HOST:172.23.11.175,TYPE:SOCK_ROBUST,PORT:14016
RESOURCE_NAME=GID.eventlogger

[EventLogger]
LoggerType=DBLogger
LoggerType=EnsignCommandPost
LoggerType=Tivoli

[DBLogger]
MessageFile=../data/DBMessages.txt
DefaultErrorID=MQ_DefaultErrorID
DATABASE=oracle10g

3
EventLogger

USERNAME=ball_ret35
PASSWORD=ball_ret35
PASSWORD_ENCRYPTED=FALSE
NumDBInterfaces=1

[EmailLogger]
MessageFile=../data/EmailMessages.txt
Name=EmailLogger
Server=mel1.m-systems.com
Port=25
Subject=EventMessage
Period=1
Email=guava,al.lines@reuters.com,,CRITICAL

[EnsignCommandPost]
MessageFile=../data/EnsignMessages.txt
LoggerFile=../log/EventLogger.log
DefaultErrorID=MQ_DefaultErrorID

[StatsLogger]
MessageFile=../data/StatMessages.txt
Name=StatLogger
Server=mel1.m-systems.com
Port=25

[Tivoli]
MessageFile=../data/TivoliMessages.txt
LoggerFile=../log/TivoliEventLogger.log
DefaultErrorID=MQ_DefaultErrorID

[MessageHandler]
ReportMessageNotFound=0

[DBWriter]
LogErrorsToDB=0

4
EventLogger

Event Logger Message Files

Message customization files for different supported database logging devices.
The suite of files are automatically generated by the EventLogger Library.
Please use the same version with your EventLogger.

RET version lower than 3.4

https://transactions.thomsonreuters.com/asp/intranet/filebase/editcomponent.aspx?uid=255

RET version more than 3.4

https://transactions.thomsonreuters.com/asp/intranet/filebase/editcomponent.aspx?uid=11648

Compatibility Matrix
List the compatibility dependency here.

Component version Require component Recommended version

version
RET3.4 and prior 2.xx.0 3.4.287.1.xxx Latest version
RET3.5 3.5.711.1.xxx Same as RET version Latest version

Related Links
Error in EventLogger
Errors in the Eventlogger (ASPLogger logs)
How to get rid of the Log-in messages in the system log RET3.4 SP3
Enable Admin Audit log
How to Configure Email Events
Event data on database for audit

Message Glossary

5
EventLogger

the attachment is sample of event code generated by MsgsFileTool v3.5.711.1.1256