Log Files

Install Log Files

When installed with the integrated installer, the log for the Configuration Hub portion of the install is named ConfigHubInstaller.log. This log appears in the C:\Users\Admin\AppData\Local\Temp folder and can be used to troubleshoot any issues that occur during install.

Configuration Hub Log Files

By default, the logs for Configuration Hub are saved to the following locations: C:\Program Files\GE\ConfigurationHub\Web\logs, and C:\Program Files\GE\ConfigurationHub\Logs.

IGS Log File

For IGS, the log file named igs-browse-config.log is located in the C:\Program Files (x86)\GE\iFIX\LOCAL folder, by default.

Historian Log Files

For Historian, the logs are stored in the default install path. This path can be the default: C:\Proficy Historian Data, or another custom path as specified during the Historian installation.

iFIX Log Files

For iFIX, the associated logs are in C:\Program Files (x86)\GE]iFIX\LOCAL\Logs folder, by default. The names of these files are:


Log Name	Description
ifix_auth_service.log	iFIX authentication service log file.
ifix_config_service.log	iFIX OPCUA Config Service log file.
ifix_confighub_facade_service.log	iFIX ConfigHub Facade service log file.
ifix_model_editor_service.log	Model editor service log file.
ifix_model_service.log	iFIX model service which is used for publishing model information to iFIX.
ifix_tag_service.log	iFIX tag service log file.
ifix_tag_validators.log	iFIX tag validator log file.
igs-browse-config.log	IGS browsing log file.

The following list are the .json files located in the iFIX LOCAL directory that are associated with the log files in the previous table:

ifix_auth_service.json
ifix_config.service.json
ifix_confighub_facade_service.json
ifix_model_service.json
ifix_tag_service.json
ifix_tag_validators.json
igs-browse-config.json

Each of these .json files have an entry called "level" that accepts various values in lower case to capture greater detail of information. iFIX must be restarted after any modification of any of the levels in the json files.

Important: If you change any of the logging levels for the ,json files, after you've finished capturing the logs, be sure to set the level back to the default of "info". Otherwise, leaving the log at a level of "info" can impact performance.

Example of Modified .json File for Logging

Below is an example of the ifix_auth_service.json file. Note that the "level" is currently set to "info." This value can be changed to any of the values in the following list. Note, that all values set for the level must be lower case.

{
            "AccessTokenExpiryInterval": 1800,
            "RefreshTokenExpiryInterval": 86400,
            "port": "4857",
            "secure" : true,
            "Clientid" : "admin",
            "ClientSecret" : "admin",
            "log" : 
              {
              "enable": true,
              "name" : "ifix_auth_service.log",
              "level": "info",
              "max-size": 5242880,
              "max-files": 3,
              "flush-seconds": 10
              }
            }

The log level goes from off to trace. The default level is "info". The recommendation is to set the level to "trace" when troubleshooting the logs. After changed, iFIX will need to be restarted. The log files are located in the iFix\LOCAL\Logs directory.

Important: After you've finished capturing the logs, be sure to set the level back to the default of "info". Otherwise, leaving the log at a level of "info" can impact performance.

Error Logging Levels for iFIX .json Files

Acceptable entries for "level" are listed below:

off – To disable logging for the REST service.
critical – For this value the REST services do not have any messages implemented. This setting will output log messages for critical level only.
error – This level captures any error logs. This setting will output log messages for critical and error levels.
warning – Some warning messages are implemented in the REST. This setting will output log messages for critical, error, and warning levels.
info – This is the default value set in the JSON files. This setting will output log messages for critical, error, warning, and info levels.
debug – This setting will output log messages for critical, error, warning , info, and debug levels.
trace – This log level will output every log message implemented in the REST service. This setting will output log messages for critical, error, warning , info , debug, and trace levels.