Logs are available for each process. They are written to <DATADIR>\run\<PROCESS NAME>\log.log and can be displayed from Administration Console > Logs.
A global log file gathering all process logs is written to <DATADIR>\run\global.log.
How to Find Errors?
Search for ERROR and WARN to detect errors in logs.
How to Change the Log Level?
Use the Min level field to filter the log level displayed in Administration Console > Logs:
Recommendation: Use the INFO level for production environment.
Change Log Location
You may want to move the logs to another partition than the data so that a full filesystem or heavy logging does not impact the rest of the product functions.
1. Edit the file <DATADIR>/bin/ngstart.env.
2. Update the value of the NGRUNDIR variable.
Your original ngstart.env is as follows:
... NGRUNDIR=C:\CloudView\data\run ...
3. Restart the product.
Rotate and Purge Logs
You can set log parameters in the API Console to manage the thresholds and rotation behavior.
Set Log Rotation and Purge
1. In the API Console, select Manage.
2. Set the log rotation and purge parameters:
a. Select MAMI master.
b. Under Configuration, select the setLoggingConfig method.
c. Edit the parameters:
logRotationMaxSizeKB
Rotate log files when bigger than the specified number of kilobytes.
logPurgeMaxSizeKB
Purge log files when their total size is above the specified number.
logExpirationDays
Purge log files when older than the specified number of days.
logRotationCronExpression
Trigger log rotation with a custom cron expression.
3. Click Save.
4. Click Apply to apply the parameters.
Set Log Rotation Per Host
The logs are rotated by default every 24 hours using a cron expression. You can specify rotate the process log files manually using the RotateLog method at a different frequency.
1. In the API Console, click Manage.
2. Set the log rotation and purge parameters:
a. Select MAMI master.
b. Under Operation, select the rotateLog method and edit it.
c. Click Send.
The log files are archived. See the use cases below.
By default, the rotateLog message is the following.
