Viewing All Logs

if there are any problems with the configdb, such as email issues or workflow errors, they are reported in the logs review the logs to determine the underlying issue and to help resolve it setting the log level docid\ lp86baszapn6jr6tmeix1viewing the logs docid\ lp86baszapn6jr6tmeix1 setting the log level you can set the amount and detail of information in the logs by adjusting the log level you can do this by going to the logging configuration workspace see the online help configuring the logs all the logs related to the app domain will be stored in the following locations configurable logs in the step 4 of the system configuration wizard, enter the file location in the log file location all the configurable logs pertaining to configuration wizard and appserver will be stored in this location non configurable logs these are logs that depend on the parameters specified in the nlog config file or other appdomain for example, in the escalationservice appdomain , go to the path heat software\heat\escalationservice , check the nlog config file where the configuration of logs is done in the target node with the name logfile as shown in the image below for all other appdomains listed below, the logs will be available in the following format c \ism\logs\esclationssvc\ actionservice centralconfiguration emailservice escalationservice frssurveyproxy frssurvey opsconsole integrationserver messagequeue inboundwebservice loggingservice matricsserver workflowservice assetprocessor discoprocessor imreadonlydataservice ivanticlouddataprocessor taskprocessor webservices agenttaskws viewing the logs follow these steps to view all of the logs associated with the configdb log in to the configdb from the workspace selector bar, select all logs the system displays the logsall workspace with the following information field description log entry id a unique id for this log entry log time the time at which the log entry was originally created on the server log db time the time when the log was uploaded into the database client ip address the ip address of the service that generated the log, such as the workflow server subsystem id the subsystem of the service that generated the log (each module has predefined subsystems for example, for the email server, polling is a subsystem ) login id the login id for the user who experienced the log event tenant id the tenant instance that is experiencing the log event error code the category of the error an example is "trigger not found" current role the role assigned to the user if the error is generated by a user if the error is generated by the system, this field is empty host name the machine that is reporting the error thread name internal thread id not applicable double click any log entry to view the log details to refresh the data, click refresh non configurable logs that is logs that depend on the parameters specified in the nlog config file are stored in the following path heat software\heat\escalationservice