Using the Logs Tab
You can view domain, application service, and user activity log events in the Logs tab of the Administrator tool. When you view log events in the Logs tab, the Log Manager displays the generated log event files in the log directory. When an error message appears in the Administrator tool, the error provides a link to the Logs tab.
You can use the Logs tab to perform the following tasks:
- •View log events and the Administrator tool operational errors. View log events for the domain, an application service, or user activity.
- •Filter log event results. After you display the log events, you can display log events that match filter criteria.
- •Configure columns. Configure the columns you want the Logs tab to display.
- •Save log events. You can save log events in XML, text, and binary format.
- •Purge log events. You can manually purge log events.
- •Copy log event rows. You can copy log event rows.
Viewing Log Events
To view log events in the Logs tab of the Administrator tool, select the Domain, Service, or User Activity view. Next, configure the filter options. You can filter log events based on attributes such as log type, domain function category, application service type, application service name, user, message code, activity code, timestamp, and severity level. The available options depend on whether you choose to view domain, application service, or user activity log events.
To view more information about a log event, click the log event in the search results.
You can view logs to get more information about errors that you receive while working in the Administrator tool.
1. In the Administrator Tool, click the Logs tab.
2. In the contents panel, select Domain, Service, or User Activity view.
3. Configure the filter criteria to view a specific type of log event.
The following table lists the query options:
Log Type | Option | Description |
|---|
Domain | Category | Category of domain service you want to view. |
Service | Service Type | Application service you want to view. |
Service | Service Name | Name of the application service for which you want to view log events. You can choose a single application service name or all application services. |
Domain, Service | Severity | The Log Manager returns log events with this severity level. |
User Activity | User | User name for the Administrator tool user. |
User Activity | Security Domain | Security domain to which the user belongs. |
Domain, Service, User Activity | Timestamp | Date range for the log events that you want to view. You can choose the following options: |
Domain, Service | Thread | Filter criteria for text that appears in the thread data. You can use wildcards (*) in this text field. |
Domain, Service | Message Code | Filter criteria for text that appears in the message code. You can also use wildcards (*) in this text field. |
Domain, Service | Message | Filter criteria for text that appears in the message. You can also use wildcards (*) in this text field. |
Domain, Service | Node | Name of the node for which you want to view log events. |
Domain, Service | Process | Process identification number for the Windows or UNIX service process that generated the log event. You can use the process identification number to identify log events from a process when an application service runs multiple processes on the same node. |
User Activity | Activity Code | Filter criteria for text that appears in the activity code. You can also use wildcards (*) in this text field. |
User Activity | Activity | Filter criteria for text that appears in the activity. You can also use wildcards (*) in this text field. |
4. Click the Filter button.
The Log Manager retrieves the log events and displays them in the Logs tab with the most recent log events first.
5. Click the Reset Filter button to view a different set of log events.
Tip: To search for logs related to an error or fatal log event, note the timestamp of the log event. Then, reset the filter and use a custom filter to search for log events during the timestamp of the event.
Configuring Log Columns
You can configure the Logs tab to display the following columns:
- •Category
- •Service Type
- •Service Name
- •Severity
- •User
- •Security Domain
- •Timestamp
- •Thread
- •Message Code
- •Message
- •Node
- •Process
- •Activity Code
- •Activity
Note: The columns appear based on the query options that you choose. For example, when you display a service type, the service name appears in the Logs tab.
1. In the Administrator Tool, click the Logs tab.
2. Select the Domain, Service, or User Activity view.
3. To add a column, right-click a column name, select Columns, and then the name of the column you want to add.
4. To remove a column, right-click a column name, select Columns, and then clear the checkmark next to the name of the column you want to remove.
5. To move a column, select the column name, and then drag it to the location where you want it to appear.
The Log Manager updates the Logs tab columns with your selections.
Saving Log Events
You can save the log events that you filter and view in the Log Viewer. When you save log events, the Log Manager saves whatever logs that you are viewing based on the filter criteria. To save log events to a file, click Save Logs on the Log Actions menu.
The Log Manager does not delete the log events when you save them. The Administrator Tool prompts you to save or open the saved log events file.
Optionally, you can use the infacmd isp GetLog command to retrieve log events.
The format you choose to save log events to depends on how you plan to use the exported log events file:
- •XML file. Use XML format if you want to analyze the log events in an external tool that uses XML or if you want to use XML tools, such as XSLT.
- •Text file. Use a text file if you want to analyze the log events in a text editor.
- •Binary file. Use binary format to back up the log events in binary format. You might need to use this format to send log events to Informatica Global Customer Support.
Exporting Log Events
You can export the log events to an XML, text, or binary file. To export log events to a file, click Export Logs on the Log Actions menu.
When you export log events, you can choose which logs you want to save. When you choose Service logs, you can export logs for a particular service type. You can choose the sort order of the log events in the export file.
The Log Manager does not delete the log events when you export them. The Administrator tool prompts you to save or open the exported log events file.
Optionally, you can use the infacmd GetLog command to retrieve log events.
The format you choose to export log events depends on how you plan to use the exported log events file:
- •XML file. Use XML format if you want to analyze the log events in an external tool that uses XML or if you want to use XML tools, such as XSLT.
- •Text file. Use a text file if you want to analyze the log events in a text editor.
- •Binary file. Use binary format to back up the log events in binary format. You might need to use this format to send log events to Informatica Global Customer Support.
The following table describes the export log options for each log type:
Option | Log Type | Description |
|---|
Type | Domain, Service, User Activity | Type of logs you want to export. |
Service Type | Service | Type of application service for which to export log events. You can also export log events for all service types. |
Export Entries | Domain, Service, User Activity | Date range of log events you want to export. You can select the following options: - - All Entries. Exports all log events.
- - Before Date. Exports log events that occurred before this date.
Use the yyyy-mm-dd format when you enter a date. Optionally, you can use the calendar to choose the date. To use the calendar, click the date field. |
Export logs in descending chronological order | Domain, Service, User Activity | Exports log events starting with the most recent log events. |
XML Format
When you export log events to an XML file, the Log Manager exports each log event as a separate element in the XML file. The following example shows an excerpt from a log events XML file:
<log xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:common="http://www.informatica.com/pcsf/common" xmlns:metadata="http://www.informatica.com/pcsf/metadata" xmlns:domainservice="http://www.informatica.com/pcsf/domainservice" xmlns:logservice="http://www.informatica.com/pcsf/logservice" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<logEvent xsi:type="logservice:LogEvent" objVersion="1.0.0" timestamp="1129098642698" severity="3" messageCode="AUTHEN_USER_LOGIN_SUCCEEDED" message="User Admin successfully logged in." user="Admin" stacktrace="" service="authenticationservice" serviceType="PCSF" clientNode="sapphire" pid="0" threadName="http-8080-Processor24" context="" />
<logEvent xsi:type="logservice:LogEvent" objVersion="1.0.0" timestamp="1129098517000" severity="3" messageCode="LM_36854" message="Connected to node [garnet] on outbound connection [id = 2]." user="" stacktrace="" service="Copper" serviceType="IS" clientNode="sapphire" pid="4484" threadName="4528" context="" />
Text Format
When you export log events to a text file, the Log Manager exports the log events in Information and Content Exchange (ICE) Protocol. The following example shows an excerpt from a log events text file:
2006-02-27 12:29:41 : INFO : (2628 | 2768) : (IS | Copper) : sapphire : LM_36522 : Started process [pid = 2852] for task instance Session task instance [s_DP_m_DP_AP_T_DISTRIBUTORS4]:Executor - Master.
2006-02-27 12:29:41 : INFO : (2628 | 2760) : (IS | Copper) : sapphire : CMN_1053 : Starting process [Session task instance [s_DP_m_DP_AP_T_DISTRIBUTORS4]:Executor - Master].
2006-02-27 12:29:36 : INFO : (2628 | 2760) : (IS | Copper) : sapphire : LM_36522 : Started process [pid = 2632] for task instance Session task instance [s_DP_m_DP_AP_T_DISTRIBUTORS4]:Preparer.
2006-02-27 12:29:35 : INFO : (2628 | 2760) : (IS | Copper) : sapphire : CMN_1053 : Starting process [Session task instance [s_DP_m_DP_AP_T_DISTRIBUTORS4]:Preparer].
Binary Format
When you export log events to a binary file, the Log Manager exports the log events to a file that Informatica Global Customer Support can import. You cannot view the file unless you convert it to text. You can use the infacmd ConvertLogFile command to convert binary log files to text files, XML files, or readable text on the screen.
Viewing Administrator Tool Log Errors
If you receive an error while starting, updating, or removing services in the Administrator tool, an error message in the contents panel of the service provides a link to the Logs tab. Click the link in the error message to access detail information about the error in the Logs tab.