立即与支持人员聊天
与支持团队交流

Identity Manager 8.1.4 - Process Monitoring and Troubleshooting Guide

About this guide Monitoring handling of processes Support for error localization in One Identity Manager Configuring logs in One Identity Manager One Identity Manager configuration files

LOGServiceChangeEventLog

To record One Identity Manager Service messages in the server's event log, modify the EventLogLogWriter module in the One Identity Manager Service's configuration file. To view the event log, you can use the results display in the Microsoft Management Console, for example.

Table 20: EventLogLogWriter parameters

Parameters

Description

EventLog

Name of the event log to which the messages are written. The messages are written to the application log with Application as the default value.

NOTE: If more than one One Identity Manager Service write event logs on a server, make sure that the first eight letters in the log name are unique on the server.

LogSeverity

Severity levels of the logged messages.

Permitted values are:

  • Info: All messages are written to the event log. The event log quickly becomes large and confusing.

  • Warning: Only warnings and exception errors are written to the event log (default).

  • Serious: Only exception messages are written to the event log.

EventID

The ID of the messages written to the event log.

Category

The category of the messages written to the event log.

Source

The name of the source of the messages written to the event log.

Process handling error can also be written to a server’s result log. For this purpose, use the LogComponent process component.

For more detailed information about configuring the One Identity Manager Service, see the One Identity Manager Configuration Guide.

Related topics

HTTPLogPlugins log file

If the HTTPLogPlugin plug-in is configured in the One Identity Manager Service configuration file, a log file is generated with the HTTP queries of the One Identity Manager Service. The file is written in Apache HTTP Server Combined Log Format.

Example entry

172.19.2.18 - - [03/Feb/2005:14:55:48 +0100] "GET /resources/JobService.css HTTP/1.x" OK - "http://<server name>:<port>/status/LogWriter/Config""Mozilla/5.0 (Windows; U; 5.1; en-US; rv:1.7.5) Gecko/20041108Firefox/1.0"

Table 21: Meaning of each entry
Entry Meaning

172.19.2.18

IP address that sent the request.

-

Client user name using IDENT protocol (RFC 1413)-

-

User name of the client according to HTTP authentication.

[03/Feb/2005:14:55:48 +0100]

Time that the request is processed on the server

GET /resources/JobService.css HTTP/1.x

Request

OK

Status code-

-

Size of data sent back to the browser

"http://<server name>:<port>/status/LogWriter/Config"

URL from which the page can be accessed

"Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108Firefox/1.0"

Browser name

For more detailed information about configuring the One Identity Manager Service, see the One Identity Manager Configuration Guide.

Output of extended return values from individual process components

Table 22: Configuration parameter for outputting extended return values
Configuration parameter Effect when set
Common | Jobservice | DoReturnOutput The entire output of the parameter is written to the One Identity Manager Service log file when a error occurs in the case of process task that supply an extended return value.

Individual process components have process tasks with parameters that supply extended return values (OUT).

The entire output of the parameter is written to the One Identity Manager Service log file when a error occurs. For example, the output text of the listed commands or programs can be returned when you run a command or a program using the CommandComponent process component.

To log return values

  • In the Designer, enable the Common | Jobservice | DoReturnOutput configuration parameter.
Related topics

Configuring notification behavior for DBQueue Processor initialization

If errors occur during initialization of the DBQueue Processor, messages are written to the application log. You can use the results display in the Microsoft Management Console, for example, to view the application log.

Use the QBM | DBServerAgent | CreateNotification configuration parameter to configure in which cases error messages are written to the application log. In the Designer, you can modify the configuration parameter as required.

Permitted values are:

  • 0: No logging.

  • 1: Only success messages are logged.

  • 2: Only error messages are logged.

  • 3: All messages are logged.

For more detailed information about the DBQueue Processor, see the One Identity Manager Configuration Guide.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级