Skip to content
Riversoft STCP Gemini Rename
Audit

Monitoring and audit

Where messages are stored

DestinationModeContentLevel limit
Instance log databaseDatabaseRule and run messages, together with the transfers. Viewed in the Riversoft® Console Portal.Instance Log.Verbose
Text logLocal fileThe same messages, in a file in the applLogDir directory.Log.Verbose in cfgInstance
Standard error (stderr)BothRun messages, for whoever triggered the command. Can be written to a file with -errfile.applDebug

Each message has a code (MSGnnnn), described in Message codes, and is recorded with the rule source user (SourceUser), which makes it easy to filter a partner’s events in the Portal.

Level of detail

Each message has a level and is recorded only when its level is lower than or equal to the destination limit. The levels of the rule messages are set in the routing (LogLevelOnSuccess, LogLevelOnWarning, LogLevelOnInfo and LogLevelOnError). See Message levels.

Examples:

  • To also record time and size warnings, set LogLevelOnWarning to a value lower than or equal to the instance Log.Verbose.

  • To diagnose a problem on the command line, temporarily raise applDebug and use -errfile:

    stcpren -db -rules INBOUND -errfile /tmp/stcpren-debug.log /mailbox/IN/NOTES.TXT

    Set applDebug back to its previous value after the diagnosis.

What to monitor

IndicatorHow to monitor
Files with no ruleMSG7003 messages. They indicate files left at the source.
Copy and backup failuresMSG7007 and MSG7019 messages, usually caused by permissions, disk space or an existing destination.
External command failuresMSG7011 and MSG7012 messages.
Files piling up at the sourceNumber of files in the scanned directory. A pile-up indicates rules with no match or runs that are not happening.
Startup failuresExit code 4 and message MSG7942.
License validityEnd date given in MSG7909.

Audit

  • In the database mode, messages are stored in the instance log database, with date and time, user, rule and file, and follow the retention set for that database.
  • In the local file mode, include the applLogDir directory in the server backup and log rotation routine.
  • Routings exported with -export serve as a record of the rules in use at each point in time.
OperationTroubleshooting