Skip to main content

Logging Service (idmlogsvc)

The Logging Service (idmlogsvc) manages logging sessions for a particular instance. It captures event messages from Bravura Security Fabric program execution, and writes them to the configured log file (idmsuite.log by default).

The Logging Service also has the ability to write to the Windows event logs.

If the Bravura Security Fabric server runs out of disk space, the Logging Service stops logging until there is at least 10 MB of disk space available, then it begins logging again.

Dependencies / requirements

The Logging Service must start before all other application binaries or services, before IIS, at the same time the OS starts up, and stop after all product services including IIS (so it doesn't miss logging entries). This is because there are other binaries, triggered by IIS or manually whose log events must be captured. The services configuration is in the Windows registry and it writes directly to disk, so it does not need the Database Service (iddb) to be running.

Configuration

The service is automatically installed and started on the Bravura Security Fabric server during setup. You can modify the following parameters related to this service on the Service information page (Manage the system> Maintenance> Services> Logging Service (idmlogsvc) ).

You can update the idmlogsvc parameters without having to restart the Logging Service; however, the service’s event tracing needs to be restarted for the configuration changes to take effect.

See psdebug to see how the service options can be overridden.

Table 1. idmlogsvc service options

Option

Description

Name of the log file

The name of the Bravura Security Fabric log file. The default is idmsuite.log .

The file is created in the directory defined by the PSTempDir setting. This is normally <Program Files path>\Bravura Security\Bravura Security Fabric\Logs\<instance> . When the service starts, Bravura Security Fabric creates the directory if it does not already exist.

Default level for log messages

The default logging level. It can be set to:

  • No debugging

  • Default debugging

  • Full debugging

Enabled extended log levels

The default extended level. It can be set to none, one or more of:

  • Runtime performance messages – All binary and script performance are recorded.

  • Ajax runtime performance messages – All Ajax requests, including the function name, transid, duration, and user are recorded.

  • Stored procedure runtime performance messages – The performance of stored procedures, called by binaries, is recorded.

  • Local workstation service runtime performance messages

  • Replication runtime performance messages



Command-line options for idmlogsvc are listed below:

Table 2. idmlogsvc service command-line options

Argument

Description

-h

Displays usage information.

-server

Run the service in server mode.

-start

Starts the service.

-stop

Stops the server/service

The following can be set only if the service is running:

-trace-start

Starts tracing the logging information.

-trace-stop

Stops tracing the logging information.

-trace-restart

Restarts tracing the logging information.

-rotatelog <N>

Rotate the log folder for at most <N> rounds. See Log directory rotation .

-config -logfile <filename>

Set the log file name.

-config -level <level>

Set the default logging level.

It can be set to:

  • 0 No debugging

  • 4 Default debugging

  • 6 Full debugging

-config -extlevel <[level name]>

Set extended log levels.

It can be set to none, one or more of:

  • perf Runtime performance messages – All binary and script performance are recorded

  • perf_sproc Stored procedure runtime performance messages – The performance of stored procedures, called by binaries, is recorded.

  • perf_lws Local workstation service runtime performance messages

  • perf_replication Replication runtime performance messages

  • perf_ajax Ajax runtime performance messages – All Ajax requests, including the function name, transid, duration, and user are recorded.

-config -bufsize <N>

Set the size of the session buffers.

-config -bufmax<N>

Set the maximum number of buffers.



In this section: