Client Logs The BigFix Client writes its current activity in to a log file with the current date as the file name, in the following format: 'yearmonthday.log'. If the size of an active log exceeds 512K on a particular day, it is backed up (in a.bkg file) and a new log is created.

Every time the log hits the size limit, the backup action overwrites the existing backup. Both active and backup logs are deleted after ten days.

Default locations The default locations of the BigFix Client logs are as follows:. Windows: C: Program Files (x86) BigFix Enterprise BES Client BESData Global Logs. Unix/Linux: /var/opt/BESClient/BESData/Global/Logs. Mac: /Library/Application Support/Bigfix/BES Agent/BESData/Global/Logs Section 2. Updating log settings To modify the number of days that you can retain the client logs or the log size limit, use the following client settings.

Xshell free download for mac. BESClientLogDays The maximum of number of days you can retain the client log files. Type: Numeric Version: 5.1 Platform: All MinNumeric: 1 MaxNumeric: 366 Default: 10 Requires Client Restart: NO BESClientLogMaxSize The maximum size of a log file in bytes. When the size exceeds this limit, the log is renamed as 'currentdate'.bkg (unless this file already exists) and then another log is created for the rest of the day.

Type: Numeric Version: 7.0 Platform: All MinNumeric: 0 MaxNumeric: maxuint32 Default: 512000 Requires Client Restart: NO Note: It's recommended that you leave the values of the settings at their defaults unless there is a compelling reason to modify them. Collecting the logs Use one of the following methods to collect the client logs: Method 1: Connect to the endpoint machine remotely, compress and copy the logs directory, and transfer or FTP it to a network file share. Gather client diagnostics data. For details, see. Client Debug Logging You can activate client debug logging (also called extended message (EMsg) logging) on a client to verbosely trace every operation that a client performs. Make sure you always set it to the maximum detail level, which is 10000.

Relevance Sum Of Sizes Of Bigfix Client Downloads For Mac Mac

Enabling/disabling client debug logging Use one of the following methods to enable/disable client debug logging: Method 1: Take action on the following tasks in the BES Support site: Task # 157: BES Client Setting: Enable Debug Logging (specify 10000 as the debug detail level) Task # 196: BES Client Setting: Disable Debug Logging Method 2: Create or remove the following custom client settings through the BigFix Console. To create a setting, select the computer(s) right-click click 'Edit Computer Settings'. BESClientEMsgDetail Enables the BigFix Client debug log level that provides extended information about the BigFix Client activity. Set the value to 10000. BESClientEMsgFile The full path to the file (including the file name) to which you want to write the extended messages. For example:.

Windows: C: Program Files (x86) BigFix Enterprise BES Client besclientdebug.log. Unix/Linux: /var/opt/BESClient/besclientdebug.log. Mac: /Library/Application Support/Bigfix/BES Agent/besclientdebug.log Note: For this to work, you must set BESClientEMsgDetail to a value greater than 0. BESClientEMsgEvalLog Enables the EMsg (debug) logging of content identifiers prior to relevance evaluation.

Relevance Sum Of Sizes Of Bigfix Client Downloads For Machines

Set it to 1 to enable the setting. This setting is useful, for example, in identifying problematic relevance expressions. Method 3: Connect to the endpoint machine remotely, and create or remove debug logging settings as follows. Client Usage Profiler The client usage profiler logs the time spent on evaluating content.

It highlights the pieces of content that consume most of a client's time during its evaluation cycle. After the usage profiler is enabled, the Client tracks the top 100 activities that take the longest time and stores them in files (in the client directory) with the following naming convention 'usageprofiler.txt.xxxx' Section 1. Enabling/disabling the client usage profiler Method 1: Take action on the following tasks in the BES Support site: Task # 361: TROUBLESHOOTING: Enable BES Client Usage Profiler Task # 418: TROUBLESHOOTING: Disable BES Client Usage Profiler Method 2: Create the following custom client settings through the BigFix Console or remove them, as applicable. To create a setting, select the computer(s) right-click click 'Edit Computer Settings'. BESClientResourceTrackingMaxFiles Set to 24 (24 hours of tracking). BESClientResourceTrackingCount Set to 100. BESClientResourceTrackingCycleSeconds Set to 3600.

BESClientResourceTrackingFile Windows: Set to C: Program Files (x86) BigFix Enterprise BES Client usageprofiler.txt Unix/Linux: Set to /var/opt/BESClient/usageprofiler.txt Mac: Set to /Library/Application Support/BigFix/BES Agent/usageprofiler.txt Method 3: Connect to the endpoint machine remotely, and create or remove client usage profiler settings as follows. Client Dump Files When a client process stops or crashes on a Windows endpoint, are generated. You can use these files in determining why the agent stopped or crashed. Dump files are output to the client's BES Client directory on the endpoint. For example, C: Program Files (x86) BigFix Enterprise BES Client BESClient.dmp.

To collect the client dump files, use one of the following methods: Method 1: Connect to the endpoint machine remotely, compress and copy the dump files, and transfer or FTP it to a network file share. Gather client diagnostics data.

For details, see.

Client Objects These Inspectors retrieve information about the application containing the relevance evaluator. Client The client object allows access to properties of the client application hosting the relevance evaluation, typically a BigFix program. In addition, the client maintains a collection of settings with both name and value properties that are inspectable using the client object. These Inspectors share properties of application types, such as version and size.

Creation Methods Declaration Description Platforms ( ) Returns the client object corresponding to the BigFix application evaluating the current relevance expression. This is equivalent to the file system object of the BigFix Client executable. Example: pathname of parent folder of client - Returns the pathname corresponding to the folder containing the BigFix Client executable.