Skip to main content

About the Bravura Security Fabric Log

The Logging Service (idmlogsvc) maintains a log of Bravura Security Fabric program execution. This includes web modules, services, exit programs, plugins, connectors, and command-line programs. By default the log is stored in a text file, idmsuite.log , within the Logs directory. This directory is rotated nightly; rotated logs are named in the following way:

  1. Current: <instance>

  2. Most recent for specific date, except the current log: <instance> . <yyyy> - <mm> - <dd>

  3. Log rotated more than once for a specific date: <instance> . <yyyy> - <mm> - <dd> - <hhmmss> . <SerialNo> .

For example, if the instance is ExampleCo, logs are named:

ExampleCo 
ExampleCo.2016-02-28
ExampleCo.2016-02-28-134020.0
ExampleCo.2016-02-28-114020.0
ExampleCo.2016-02-27   
ExampleCo.2016-02-26   
ExampleCo.2016-02-25

In the above example, the log was rotated 3 times in 2016-02-28 and the directories are in a most recent sequence order.

Log entries are, in general, composed of multiple lines or messages written in the format:

<date> <time> - [<lsid>] <program> [<process ID>,<thread ID>] <level>: [<range>] <message text> 

where:

lsid

is the logging session ID. Certain programs, such as web modules, include a session ID in their log entries. All lines with the same logging session ID belong to the same event.

level

is the level or severity of the message. This can be one of: Error, Warning, Notice, Info, Debug, or Verbose.

range

is the range of characters from the log message included in the log entry. This is shown only when long log messages are spread between multiple log entries. Since each log entry includes 500 characters of the log message, the range for the first entry is [0 .. 499] .

See also:

  • Scheduling Maintenance to learn how to control the rotatelog job that is responsible for rotating the log file directory.

  • Logging Service to learn how to change log service parameters for logging, including the log file name and location, and the logging level. This section also shows you how to rotate the log using the idmlogsvc-rotatelog <N> command.

Collecting logs for troubleshooting

Access the Bravura Security Fabric product log

  1. Log in to the Front-end (PSF) as superuser.

  2. Open File Explorer.

  3. Navigate to C:\Program Files\Bravura Security\Bravura Security Fabric\Logs.

  4. For the most current log, open the default directory. Otherwise, open the desired dated default directory.

    • You will see idmsuite.log - this is the main Bravura Security Fabric log.

    • If email is configured and emails have been sent in the system, you will also see a mail directory - this is where emails go when MAIL SEND METHOD includes the FILE value.

    • If idtrack is being used and auto-discovery has run, you will also see idtrack_workfile_<date>.log - this includes a list of requests made by the automation system via idtrack.

  5. To view the main log, right-click on the idmsuite.log file, select Open with... and choose adesired viewer.

  6. Save the file to the desired location.

Logs from replicated nodes

Logs differ across nodes in a replicated instance.

To collect those logs on a single server, run the following from the instance's util folder:

updinst.exe -getlogs

Ensure you have enough space to store the logs.

To collect Bravura Security Fabric logs from other locations, use the logutil command.

See also

In this section: