When troubleshooting an issue, most likely Support will ask at some stage to provide a combined log while reproducing the reported scenario.
The main reason is to be able to have in one single file all the activity being performed with all the complete operations which will make it easier to analyze.
The most common combined logs are API, SQL and Filter but in reality it can be done with any type of logs.

Legacy ID:KA365939

Below are the steps to create a combined log.
The example will be based on a Windows platform and the same methodology applies to any other platforms.
For this example and as mentioned above we will use the most common combined logging being requested by Support.

Enabling the logs

1- Go to AR System Administration > AR System Administration Console

          


2- Select System General Server Information:

          


3- In the Server Information form select the Log Files tab:

          



4- Enable all the logging type files which will be part of the combined log. In this case as an example the API, Filter and SQL are selected:
          
          


5- Name the log for all type of logging types to be the same log file name. This way all the data captured for these logging type will be inserted in the same file.
The name of the log can be anything as always that it is easy to identify when collecting it from the logs directory.

          



6- Once the logs have been enabled and the same log filename added to them, press Apply and then OK to enable the logging to start. 

          

Note: It is recommended to have the logs enabled only when troubleshooting a possible problem. Logs can grow very big and very fast.
Please check this article:
Remedy - Server - How to set the log file size in Remedy

7- Once the required scenario or the purpose of enabling the logs has been done, disable the logs by removing the check from the checkbox marked and pressing Apply and then OK again the logging will stop.

8- To check the file, go to the DB folder:
    - (Windows)  .....\BMC Software\ARSystem\Arserver\Db
    - (Unix, Linux) .../bmc/ARSystem/db

Locate the log:




There are other options such Log per Thread where each thread has its own log file, appended with the Thread ID.
This can reduce serialization of Java threads and ensures each thread has dedicated access to a file, which reduces any impact on performance by removing this potential bottleneck.
You can select the type of logging that fits your needs and if you are working with Support, you will be informed which type of logging is required so you can follow their steps.

More information can be found in the available documentation
ARS 9.0.x: Setting Log Files options: https://docs.bmc.com/docs/display/ars9000/Setting+log+files+options
ARS 9.1.x: Setting Log Files options: https://docs.bmc.com/docs/display/public/ars91/Setting+log+files+options

Related Information
Remedy - Server - How to enable AR Server logs in the ar.cfg / ar.conf file