Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments. Click here to view the documentation for the current version.

Contents of the logs

BMC MyIT provides logging capabilities to help resolve application issues. For most log files, the format of the content is as follows:
TIME| THREAD | LEVEL| COMPONENT| MESSAGE

The following log files are available:

Log fileLocationDescription
ITSMServerConfigureXMLTask.log<InstallDir>/Smart_IT_MyIT/Logs/Installer log. Contains information about the import of data to the BMC Remedy ITSM server.
 mongod.log
  • If MongoDB is installed on the BMC MyIT server:
    <InstallDir>/Smart_IT_MyIT/Logs/
  • In a production environment, located on the MongoDB server

MongoDB logs. MongoDB is the social database. Check this file to:

  • Track database-level errors, if any.
  • Track any replication issues (if MongoDB is deployed in a replica set).
  • Track slow queries.

myit_smartit_patch_install_log.txt

  • Windows: %TEMP%/
  • Linux: \tmp\

Patch Installer logs. Check this file for exceptions if the installation is:

  • Completed with warnings
  • Failed with error

If any DEF import failure exceptions are logged, check the RIK log files.

myit_smartit_install_log.txt

  • Windows: %TEMP%/
  • Linux: \tmp\

Installer logs. Check this file for exceptions if the installation is:

  • Completed with warnings
  • Failed with error

If any DEF import failure exceptions are logged, check the RIK log files.

RikStatement.html<InstallDir>/Smart_IT_MyIT/Logs/Remedy component installer logs. Check this file for details if any DEF import failure exceptions are logged in the BMC MyIT installer or patch installer logs. The log is displayed as an HTML report.
RikStatement.log<InstallDir>/Smart_IT_MyIT/Logs/Remedy component installer logs. Check this file for details if any DEF import failure exceptions are logged in the BMC MyIT installer or patch installer logs.
RikStatement_apps.log<InstallDir>/Smart_IT_MyIT/Logs/Remedy component installer logs. Check this file for a summary report of the total number of DEF imports that passsed, failed, and skipped during BMC MyIT installation. The details are provided in RikStatement.log and RikStatement.html
social.log-<date><InstallDir>/Smart_IT_MyIT/Logs/

Social logs. This file contains the complete social service logging.

SRMServerInitTask.log<InstallDir>/Smart_IT_MyIT/Logs/ 
ux.<timeStamp>.part.n.log<InstallDir>/Smart_IT_MyIT/Logs/yyyy-mm-weekn

Primary Tomcat log file. Events for BMC MyIT are logged in this file. To download a sample file with all log levels set to debug, see MyIT Tomcat Logging in the BMC Support Knowledge Base. To configure the logging levels, see Configuring logs.

This file is saved at regular intervals defined within the logback.xml file. It contains data related to back-end calls and their duration. When the maximum defined log file size is reached, a new log file is created, and the n counter in the log file name is incremented to n+1.

ux.log<InstallDir>/Smart_IT_MyIT/Logs/This is the current version of ux.<timeStamp>.part.n.log. The time stamp and part are added when the file is saved, and a new ux.log is started.
ux-error.log<InstallDir>/Smart_IT_MyIT/Logs/

Tomcat error log file. All errors are logged to this file.

ux-metadata.log<InstallDir>/Smart_IT_MyIT/Logs/Log of the metadata load process. Contains metadata-related errors and statistics.
ux-pref.log <InstallDir>/Smart_IT_MyIT/Logs/

Additional Tomcat log file created if log type selected is Performance.

ux-sysinfo.log<InstallDir>/Smart_IT_MyIT/Logs/Provider startup log. Check this log file for provider failures, such as integration issues.
ux-test.log<InstallDir>/Smart_IT_MyIT/Logs/Log for the  Health Check utility.

Related topics

Configuring logs

Deploying MongoDB as a replica set

List of providers

Was this page helpful? Yes No Submitting... Thank you

Comments