Viewing with log files
The LogConfig utility is installed in the <Track-It! install location>\Tools folder. When you run the utility, you must select the default options for the Information level of logging for components. For more information, see To troubleshoot issues by using the LogConfig utility.
You can set the log level to any of the following option:
- Fatal
- Error
- Warning
- Information
- Debug
- Trace
Depending on the component usage, the Trace option generates the maximum data. The individual files per component are created under the <Track-It! install location>\Logs folder. The size of files that are generated per component on daily basis does not exceed 10-MB.
The format of the log file name is text_yyyy-mm-dd.log, where:
- text relates to the component
- yyyy-mm-dd is the date of creation of the log file.
The following table lists the component details:
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
| Group | Component | Log file name | Log file details | When to check the log file |
|---|---|---|---|---|
| Modules | Asset Management | AssetManagement_yyyy-mm-dd.log | This component is used for asset records. All the updates related to asset records from the Technician portal and Business Rules are processed by this component. | If you encounter a problem while saving or updating the asset records, then enable the logs for this component. The following components work in conjunction with the Asset Management component:
|
| Assignments | NAMLogicWorkOrder_yyyy-mm-dd.log | This component is used for the assignment records. All assignment record related updates such as Technician portal, business rules, Self Service, are processed by this component. | If there is a discrepancy of the data for assignment save or update, enable logs for this component. The following components that work in conjunction with the Ticket component:
| |
| Attachments | NAMLogicAttach/SDEAttach_yyyy-mm-dd.log | This component is used for the attachment records linked to various other records. | If there is an issue with adding or fetching an attachment record from various modules, enable logs for this component. | |
| Change Management | ChangeManagement_yyyy-mm-dd.log | This component is used for change request records. All the updates related to change request records from the Technician portal, Business Rules, and Self Service are processed by this component. | If you encounter a problem while saving or updating the change request records, then enable the logs for this component. The following components work in conjunction with the Change Management component:
| |
| Due Date Calculation | NAMCalcDueDate_yyyy-mm-dd.log | This component is used to calculate the due date for a ticket or assignment based on various factors, such as Priority, Work Schedule, Time Zone difference, Assigned to Technicians’ availability, and so on. | If the due date is not properly calculated, enable logs for this component. | |
| Purchase Management | PurchaseManagement_yyyy-mm-dd.log | This component is used for purchase order records. All the updates related to purchase order records from the Technician portal and Business Rules are processed by this component. | If you encounter a problem while saving or updating the purchase order records, then enable the logs for this component. The following components work in conjunction with the Purchase Management component:
| |
| Start/Stop Clock | StopTheClock_yyyy-mm-dd.log | This component is used to pause or restart the time for the ticket or assignment records. This feature is particularly useful when the resolution is dependent on external factors and we do not know when an SLA is breached. | If the clock is not pushed after you restart the clock, the due date or the change of status is not activated, the start/stop clock (based on the status record) is not activated, enable logs for this component. | |
| Ticket | LogicHelpdesk_yyyy-mm-dd.log | This component is used for the ticket records. All ticket record related updates, such as Technician portal, business rules, Self Service, are processed from this component. | If there is a discrepancy of the data for ticket save or update, enable logs for this component. The following components that work in conjunction with the Ticket component:
| |
| Interfaces | Service Desk Self Service | ServiceDesk/SelfService_yyyy-mm-dd.log | These components are used for the Technician portal and Self Service. | If there are any unhandled exceptions thrown, enable logs for these components and examine the details for the issue. Sometimes, these issues might result in defects. |
| Web API | WebApi_yyyy-mm-dd.log | This component is used for the Track-It! Mobile App. All the operations performed by using the Track-It! Mobile App are processed by this component. | If you encounter a problem while using the Track-It! Mobile App, then enable the logs for this component. | |
| Email and Schedulers | Business Rules | NAMMbl_yyyy-mm-dd.log | As the name indicates, this component is responsible to process all the business rules defined in the application. This is controlled by the “TrackIt Job Processor - TrackItBR” Windows Service. When this service is stopped, no jobs would be processed. Please note that this service is known to be CPU intensive in case of systems which have a large number of BRs defined and an active servicedesk. | By default, the Informational level of logging for this component is enabled. This log contains all the data that is processed during a business rule event. When a job fails (other than notifications), this log file contains the information about the failure. |
| Exchange Web Service | EwsMailListener_yyyy-mm-dd.log | This component fetches emails from the incoming mailbox configured with the Exchange Web Service (EWS) access. | If no emails are processed from the configured mailbox (EWS), you need to enable the trace for this component. Another recommendation is to enable the Enable Email Event Logging on the Track-It! Server setting in the Email Monitor Settings section of the configuration. | |
| Imap (2020 Release 03) | MGCImap_yyyy-mm-dd.log | This component fetches emails from the incoming mailbox configured with the IMAP access. | If no emails are processed from the configured mailbox (IMAP), you must enable the trace for this component or enable the Enable Email Event Logging on the Track-It! Server setting in the Email Monitor Settings section of the configuration. | |
| Notification | NAMLogicNotification_yyyy-mm-dd.log | This component is used to listen to the mailbox configured in the Incoming email section. This is controlled by the TrackIt Mail Processor - TrackItBR Windows Service. When this service is stopped, no emails are processed. This component works in conjunction with the business rules to accomplish the tasks related to emails. | By default, the Informational level of logging for this component is enabled. This log contains all the data that is processed during the notification event. When notifications fail, this log file contains the information about the failure. | |
| Pop3 | MGCPop3_yyyy-mm-dd.log | This component fetches emails from the incoming mailbox configured with the POP3 access. | If no emails are processed from the configured mailbox (POP3), you need to enable the trace for this component. Another recommendation is to have the Enable Email Event Logging on the Track-It! Server setting is enabled in the Email Monitor Settings section of the configuration. | |
| Service Management | ServiceManagement_yyyy-mm-dd.log | This component is used for the background processing of tasks, such as Asset Synchronization, Scheduled Reports, and so on. This is similar to the monitor infrastructure that we have in Track-It! version 11.4. To ensure that this component works, the Track-It! application must be active in the IIS process. | If there are issues related to asset sync, scheduled report related issues, enable logging for this component. | |
| Smtp | MGCSmtp_yyyy-mm-dd.log | This component is sends out emails from within the application. | If no emails are received from Track-It! application (even from the Notification through BRs), enable Debug and Trace logs to examine the cause of the failure. | |
| Login and Infrastructure | FeatureInfo | MGCFetureInfo_yyyy-mm-dd.log | This component contains the key mapping of the licensed features. If this fails, or has issues, the product cannot function because there would be no detail about the license entitlements. | If you observe any license related issues, enable the information/debug level of Tracing. If you still cannot troubleshoot the issue, enable the trace level and examine the logs. |
| Form Generator | NAMHTMLProvider_yyyy-mm-dd.log | This component is used to render the module forms. (Ticket/Assignment/Solution) to the disk as HTML files. You can access these files while working on the respective records. | If you observes issues or cannot access any forms of the module or the configuration section (Technician/Requestors), enable the information/debug level of Tracing. If you still cannot troubleshoot the issue, enable the trace level and examine the logs. | |
| Metadata | NAMMetadata_yyyy-mm-dd.log | This component is the heart of the application and contains all the necessary information about the basic configuration details. You can activate only one instance of this component for Technician and Self Service. After first login on each portal, after a server restart, IISRESET, this component is loaded and is stays in memory until the application is live. Generally, this component does not give any errors, unless there is a database connectivity issue, database is corrupt (manual updates of the internal Track-It! database tables) or any other dependent component is failing. | If you observe a failure mentioning MetaData Init failed error occurs, enable information/debug level of tracing. If you still cannot troubleshoot the issue, enable the trace level and examine the logs. | |
Server Control Service Control | NAMServerControl/NAMServiceControl_yyyy-mm-dd.log | If there is a change in the configuration section, these components are used to communicate to the connected application servers. These components issue a HTTP request internally, and generally known to work seamlessly. | There will be no visual indicators of whether these HTTP call(s) failed. In addition to the log files, errors are logged in the Windows Event viewer with the source as the component name. | |
| User Track | MGCUserTrack_yyyy-mm-dd.log | This component keeps track of the technician logins. Based on the license type of the technician, the login attempts are handled. This component also keeps the check on session activeness and ends the inactive user sessions. | If you observe issues while logging in or prompted repeatedly to override the already logged in session, enable information/debug level of Tracing. If you still cannot troubleshoot the issue, enable the trace level and examine the logs. | |
| Views | MGCQuickViews_yyyy-mm-dd.log | This component maintains all the workspace views. All the views that are available out-of-the-box and customer created would be handled by this component. This component also provides the count for rendering the Dashboard views. | If you observe issues while loading Dashboard views or any of the workspace views, enable information/debug level of Tracing. If you still cannot troubleshoot the issue, enable the trace level and examine the logs. |
Comments
Log in or register to comment.