Atheos provides a set a logs that enable the monitoring of the overall system. The logs file includes 3 types of logs:

1. Atheos Gateway logs

Atheos Gateway logs provide traceability of the connections established with the POIs.

Example:

2020-01-30 12.00.01 I Accepted a connection from 10.0.0.1, port 65000
2020-01-30 12.00.42 I Connection closed by peer 10.0.0.1, port 65000

1.1 Error management

The following logs indicate an error.

2.2.1 TMSMessageProcessorBuildAcceptorConfigurationUpdateV06: DataSet parsing error for the POI = <POI Identifier>

Reason: The Atheos Gateway could not read the Acceptor Configuration Update sent by a POI.

2. Atheos Server logs

Atheos Servers logs provide the status of the transmission of Nexo TMS messages exchanged with the Atheos Server. The information is accessible via the UI and the API (See Applications Logs).

Example:

2020-01-30 12.00.01 Processing files for 01234567890
2020-01-30 12.00.42 Files for 01234567890 sent successfully

2.1 Error management

The following logs indicate an error.

2.1.1 Files for <ip address>:<port> were not sent successfully. Return codes=0/550

Reason: A Nexo TMS messages could not be sent to the Atheos Server. The POI Identifier could not be retrieved therefore the IP address and the port number are logged instead.

2.1.2 Undefined POI (<POI Identifier>) for <ip address>, port <port>

Reason: A POI contacted the TMS but the POI configuration was absent or the POI does not defined in the system.

2.1.3 Error reading the message header with <ip address>, port <port>: error code = 12

Reason: A communication error terminated the connection.

3. Configuration Build Logs

Configuration Build logs provide some information about the generation of POI configuration (or Acceptor Configuration Update). The information is accessible via the UI and the API (See Applications Logs).

Example:

2020-01-30 12.00.01 I Deploying POI POI00001
2020-01-30 12.00.01 I Processing control file 202001101-082123-0457ffff-ee00-427a-ad6a-c69997e5b0b0

Any questions? Contact our team via the Amadis Help Desk.