Configuring Normalization Engine logging
The Normalization Engine provides logging information in different areas.All types have different contexts and can occur simultaneously.
For example, BMC Atrium CMDB has three datasets (A,B, and C) configured for normalization. The logging details of these datasets are as follows:
- Dataset A is normalized once a week as a batch job, so its logging information is saved to the NE.datasetA.<nnn>.log file.
- Dataset B is normalized in continuous mode, and its logging data is saved to the neContinuous.log file.
- Dataset C is configured for weekly batch normalization using the Normalization API, so it has more detailed logging information about the API events in the neApi.log file.
Logging details for different types of normalization jobs are summarized in the table below:
|Job Type||Log File Location||Default Log Level||Notes|
|Batch normalization||<AtriumCore_install>\logs\neJob.<dataSetId>.<jobID>.log||Information||The job ID is available in the Normalization console.|
|Normalization API||<AtriumCore_install>\logs\neApi.log||Warning||If discovery products use normalization APIs, use this log file to diagnose problems. This log file contains information for inline normalization.|
To configure Normalization Engine logging
- In the Normalization console, click Edit Configuration.
In the System Configuration tab, for each type of logging (Batch, API, and Continuous), click on Click to launch Plugin Server Configuration (Select Normalization Engine).
A Plugin Server Configuration form opens in a window. From the Plugin Server Instance drop-down list, select plugin server with port number 9555.
Click Plugin Configuration tab to view the configured shared plugins.
Click Plugin Server Configuration tab and modify the following settings:
Field Action Enable Plugin Log Select True to enable logging for the plugin server.
Select the log level option based on what type of information you want to save in the log file. For more information about log levels, see Understanding Log Levels.
This defines the path on the server where the log file is saved.
Maximum Log File Size
When the log file reaches the file size limit, it is renamed and a new log file is created. The older files are not automatically deleted. For example, if the log file is named nePluginServer.log, the older files are named nePluginServer.log.1 and nePluginServer.log.2.
Log History Specify a value to keep a history of number of log files to be maintained as a backup.
The modified settings are not applied to current normalization jobs, but future jobs use the modified values.