# Peloton License Manager

# Introduction

Open iT supports Peloton usage reporting by collecting log files and converting them to Open iT format.

An Open iT client is installed on your license server for this collection. The data collector monitors and gathers the license usage history logs from the license manager every 5 minutes. Once the logs are collected, the data collection process triggers and the logs are passed to the data preprocessor. After the data is preprocessed, it is transferred to the Core Server for further storage, completing the history logs collection and processing.

Log File Parsing Workflow

Log File Parsing Workflow

This will produce the following aggregated data types used for historical reporting:

Record Log Data:

Event Log Data:

The following sections will guide you in setting up the necessary configuration to collect and send the required data to the server.

# Requirements

  • An Open iT Client connected to an Open iT Server or a coexistent Open iT setup
  • License server administrative rights
  • Full path to the debug log file

# Configuring Log File Collection

These are the required steps to configure collection of Peloton log files.

  1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and back up the logfilecollector-peloton.xml file.

  2. Open a command prompt with Administrator level privileges.

  3. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd C:\Program Files\OpeniT\Core\bin

  4. Once in the directory, set the location of the Peloton log files, run the command:

    Command Syntax
     openit_confinit -c "logfilecollector-peloton.logfilecollector.source.dir=<peloton_log_dir>"

    where <peloton_log_dir> is the location of the Peloton log files.

    Example
     openit_confinit -c "logfilecollector-peloton.logfilecollector.source.dir=C:\ProgramData\Peloton"
     2013.05.29 08:48:49	jdoe	KUL-00004395	logon	1	3.0.4065.23355	5788DF44196040A088E102596E8D1EC7	00:00:00	
 2013.05.29 09:20:48	jdoe 	KUL-00004491	logon	2	3.0.4065.23355	96E921F5B2214D759DB50D6C901E91A1	00:00:00	
 2013.05.29 09:20:59	jdoe 	KUL-00004491	logoff	1	3.0.4065.23355	96E921F5B2214D759DB50D6C901E91A1	00:00:10	
 2013.05.29 09:43:08	jdoe	KUL-00004395	logoff	0	3.0.4065.23355	5788DF44196040A088E102596E8D1EC7	00:54:20	
 2013.05.29 10:07:26	jdoe	BJAYCOCK	logon	1	3.0.4065.23355	92C036CE371D4CC4A23B6178653F6A4E	00:00:00	
 2013.05.29 10:09:37	jdoe	BJAYCOCK	logoff	0	3.0.4065.23355	92C036CE371D4CC4A23B6178653F6A4E	00:02:14	
 2013.05.29 10:17:35	jdoe	KUL-00004828	logon	1	3.0.4065.23355	D25A4C03ED8F452EA06A74F623357E43	00:00:00	
 2013.05.29 10:18:37	jdoe	KUL-00004828	logoff	0	3.0.4065.23355	D25A4C03ED8F452EA06A74F623357E43	00:01:02	
 2013.05.29 10:32:52	jdoe 	KUL-00001376	logon	1	3.0.4065.23355	605D2848099D40CC81D34BC7D6164229	00:00:00	
 2013.05.29 16:35:52	jdoe	KUL-00001376	logoff	3	3.0.4065.23355	7EC6B1BE9BF546F9909998332A772A10	00:00:00	Timed-out session found in net file and removed. Session logged on 2013.05.30 17:54:21. Time-out set to 8.0hrs.
 2013.05.29 16:36:12	jdoe	KUL-00001376	logoff	1	3.0.4065.23355	3DC12839F66047B68F0557290CBC7CCD	00:00:00	Session not found in net file during logoff.
 2013.05.29 16:40:26	jdoe	KUL-00001376	logon	1	3.0.4065.23355	605D2848099D40CC81D34BC7D6164229	00:00:00	
 2013.05.29 16:55:20	jdoe	KUL-00001376	logoff	1	3.0.4065.23355	605D2848099D40CC81D34BC7D6164229	05:49:54	Removed orphaned session found in net file.
 2013.05.29 17:49:55	jdoe	KUL-00004287	note	5	3.0.4065.23355	06C9ECB834A54D9E8BB40636D33C8C66	00:00:00	User denied license because all network licenses in use.

  5. Update the configuration file, run the command:

    Command Syntax
     openit_confbuilder --client

    Make sure no errors are encountered.

Refer to the Peloton Log File Collection Configuration table to learn more about Peloton configuration in logfilecollector-peloton.xml.

Object Name Accepted Value Description
source.dir DirName (e.g., C:\ProgramData\Peloton) Location of the Peloton log files.
source.pattern String (i.e., *.log*) The glob pattern identifying source files in the source directory.
source.seen String (collect, ignore, or tail) Seen files are the previously collected source files.
  • collect - Specify this option to collect from the start each time.
  • ignore - Specify this option to skip collecting from the same file again.
  • tail - Specify this option to continue collection from the end of the file last time (i.e., collect the ones added since last time).
source.cmplines Integer (e.g., 6, 10, 20) This is required if the value of source.seen is tail. This is the number of lines compared to source files collected before to determine where to start the collection.

Note: If this number is too low, you can end up with an incorrect position, and duplicate data may be in the log files. Usually, it is better to have a few lines more than strictly necessary than even a single line too little.
target.dir DirName (i,e., ${OpeniT.directories.temp}/LogFileCollector) This is the location of the directory containing the collected log data.
target.module String (i.e., license) The target type of module (in general).
target.datatype String (i.e., peloton) The specific type of target data.
target.interval Timespan (e.g., P30S, P5M, P1D) The span of time between collector runs.
target.rotation-size Integer (e.g., 6, 10, 20) The log file rotates if it goes beyond the number (in mb) defined.
target.rotation-glob String (e.g., *) The glob pattern to match before the log file rotates.
Peloton Log File Collection Configuration

  1. Go to the Components directory, which is by default in /var/opt/openit/etc/Components, and back up the logfilecollector-peloton.xml file.

  2. Go to the bin directory, which is by default in /opt/openit/bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd /opt/openit/bin

  3. Once in the directory, set the location of the Peloton log files, run the command:

    Command Syntax
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "logfilecollector-peloton.logfilecollector.source.dir=<peloton_log_dir>"

    where <peloton_log_dir> is the location of the Peloton log files.

    Example
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "logfilecollector-peloton.logfilecollector.source.dir=/root/peloton/logs"
     2013.05.29 08:48:49	jdoe	KUL-00004395	logon	1	3.0.4065.23355	5788DF44196040A088E102596E8D1EC7	00:00:00	
 2013.05.29 09:20:48	jdoe 	KUL-00004491	logon	2	3.0.4065.23355	96E921F5B2214D759DB50D6C901E91A1	00:00:00	
 2013.05.29 09:20:59	jdoe 	KUL-00004491	logoff	1	3.0.4065.23355	96E921F5B2214D759DB50D6C901E91A1	00:00:10	
 2013.05.29 09:43:08	jdoe	KUL-00004395	logoff	0	3.0.4065.23355	5788DF44196040A088E102596E8D1EC7	00:54:20	
 2013.05.29 10:07:26	jdoe	BJAYCOCK	logon	1	3.0.4065.23355	92C036CE371D4CC4A23B6178653F6A4E	00:00:00	
 2013.05.29 10:09:37	jdoe	BJAYCOCK	logoff	0	3.0.4065.23355	92C036CE371D4CC4A23B6178653F6A4E	00:02:14	
 2013.05.29 10:17:35	jdoe	KUL-00004828	logon	1	3.0.4065.23355	D25A4C03ED8F452EA06A74F623357E43	00:00:00	
 2013.05.29 10:18:37	jdoe	KUL-00004828	logoff	0	3.0.4065.23355	D25A4C03ED8F452EA06A74F623357E43	00:01:02	
 2013.05.29 10:32:52	jdoe 	KUL-00001376	logon	1	3.0.4065.23355	605D2848099D40CC81D34BC7D6164229	00:00:00	
 2013.05.29 16:35:52	jdoe	KUL-00001376	logoff	3	3.0.4065.23355	7EC6B1BE9BF546F9909998332A772A10	00:00:00	Timed-out session found in net file and removed. Session logged on 2013.05.30 17:54:21. Time-out set to 8.0hrs.
 2013.05.29 16:36:12	jdoe	KUL-00001376	logoff	1	3.0.4065.23355	3DC12839F66047B68F0557290CBC7CCD	00:00:00	Session not found in net file during logoff.
 2013.05.29 16:40:26	jdoe	KUL-00001376	logon	1	3.0.4065.23355	605D2848099D40CC81D34BC7D6164229	00:00:00	
 2013.05.29 16:55:20	jdoe	KUL-00001376	logoff	1	3.0.4065.23355	605D2848099D40CC81D34BC7D6164229	05:49:54	Removed orphaned session found in net file.
 2013.05.29 17:49:55	jdoe	KUL-00004287	note	5	3.0.4065.23355	06C9ECB834A54D9E8BB40636D33C8C66	00:00:00	User denied license because all network licenses in use.

  4. Update the configuration file, run the command:

    Command Syntax
     ./openit_confbuilder --client

    Make sure no errors are encountered.

Refer to the Peloton Log File Collection Configuration table to learn more about Peloton configuration in logfilecollector-peloton.xml.

Object Name Accepted Value Description
source.dir DirName (e.g., /root/peloton/logs) Location of the Peloton log files.
source.pattern String (i.e., *.log) The glob pattern identifying source files in the source directory.
source.seen String (collect, ignore, or tail) Seen files are the previously collected source files.
  • collect - Specify this option to collect from the start each time.
  • ignore - Specify this option to skip collecting from the same file again.
  • tail - Specify this option to continue collection from the end of the file last time (i.e., collect the ones added since last time).
source.cmplines Integer (e.g., 6, 10, 20) This is required if the value of source.seen is tail. This is the number of lines compared to source files collected before to determine where to start the collection.

Note: If this number is too low, you can end up with an incorrect position, and duplicate data may be in the log files. Usually, it is better to have a few lines more than strictly necessary than even a single line too little.
target.dir DirName (i.e., ${OpeniT.directories.temp}/LogFileCollector) This is the directory location containing the collected log data.
target.module String (i.e., license) The target type of module (in general).
target.datatype String (i.e., peloton) The specific type of target data.
target.interval Timespan (e.g., P30S, P5M, P1D) The span of time between collector runs.
target.rotation-size Integer (e.g., 6, 10, 20) The log file rotates if it goes beyond the number (in mb) defined.
target.rotation-glob String (e.g., *) The glob pattern to match before the log file rotates.
Peloton Log File Collection Configuration

# Activating Log Data Collection

These are the required steps to activate collection of Peloton log data.

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd C:\Program Files\OpeniT\Core\bin

  3. Once in the directory, activate the collection of Peloton log data, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.collect_peloton_licenselogs.general.active=true"

  1. Go to the bin directory, which is by default in /opt/openit/bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd /opt/openit/bin

  2. Once in the directory, activate the collection of Peloton log data, run the command:

    Command Syntax
     ./openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.collect_peloton_licenselogs.general.active=true"

The collection runs every 5 minutes by default. To configure the intervals, locate the instances attribute under collect_peloton_licenselogs, preprocess_peloton_licenselogs-records, or transfer_peloton_licenselogs in the same file and configure the attributes.

Refer to the Peloton Log Job Scheduler Instances Configuration table to learn the attributes used to configure Peloton data collection and transfer.

Attribute Name Accepted Value Description
max-instances Uint (e.g., 5, 8, 9) The number of instances allowed to run at the same time.
max-handling String (end-oldest, end-all-old, or end-new) The action done upon reaching the maximum number of instances:
  • end-oldest - Specify this option to stop/kill the oldest instance and start a new one.
  • end-all-old - Specify this option to stop/kill all running instances before starting the new one.
  • end-new - Specify this option to prevent a new instance from starting.
end-timeout Timespan (e.g., P30S, P5M, P1H) The maximum waiting time before terminating a running instance.
quarantine Timespan (e.g., P30S, P5M, P1H) The waiting time before starting a new instance after a previous one.
Peloton Log Job Scheduler Instances Configuration

# Deactivating Record Log Data Collection

Turning on log data collection automatically aggregates record and event log data. If you want to collect event log data only, follow these steps.

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd C:\Program Files\OpeniT\Core\bin

  3. Once in the directory, deactivate the collection of record log data, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.preprocess_peloton_licenselogs-records.general.active=false"

  4. Change the handling of event logs, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.preprocess_peloton_licenselogs-events.operations.arguments=--srcdir \"${OpeniT.directories.temp}/LogFileCollector\" --srcpattern raw-peloton-license-LogFileCollector*.data --srcfilehandling rename --trgdir \"${OpeniT.directories.temp}/LogParserPeloton\" --module license --datatype event --resolution PT1H --matchobjects \"${OpeniT.directories.conf}/matchobjects-event-peloton.oconf\" --type event --disable-statlogging"

  5. Change the data transfer schedule, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.transfer_peloton_licenselogs.scheduling.start-triggers.trigger#1.job-name=preprocess_peloton_licenselogs-events"

  1. Go to the bin directory, which is by default in /opt/openit/bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd /opt/openit/bin

  2. Once in the directory, deactivate the collection of record log data, run the command:

    Command Syntax
     ./openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.preprocess_peloton_licenselogs-records.general.active=false"

  3. Change the handling of event logs, run the command:

    Command Syntax
     ./openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.preprocess_peloton_licenselogs-events.operations.arguments=--srcdir \"${OpeniT.directories.temp}/LogFileCollector\" --srcpattern raw-peloton-license-LogFileCollector*.data --srcfilehandling rename --trgdir \"${OpeniT.directories.temp}/LogParserPeloton\" --module license --datatype event --resolution PT1H --matchobjects \"${OpeniT.directories.conf}/matchobjects-event-peloton.oconf\" --type event --disable-statlogging"

  4. Change the data transfer schedule, run the command:

    Command Syntax
     ./openit_oconfinit -u "collect_license_peloton-logs.root.scheduler.jobs.transfer_peloton_licenselogs.scheduling.start-triggers.trigger#1.job-name=preprocess_peloton_licenselogs-events"

# Verifying Log Data Collection

After configuration, you can verify that the data is collected by following these steps:

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd C:\Program Files\OpeniT\Core\bin

  3. Run the command:

    Command Syntax
     openit_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-peloton.conf"

  4. Verify that there are *.data files created in the LogFileCollector directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp\LogFileCollector.

  1. Go to the bin directory, which is by default in /opt/openit/bin, run the command:

    Command Syntax
     cd $BIN_DIR
    Example
     cd /opt/openit/bin

  2. Run the command:

    Command Syntax
     ./openit_logfilecollector -c "/var/opt/openit/etc/logfilecollector-peloton.conf"

  3. Verify that there are *.data files created in the LogFileCollector directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp\LogFileCollector.

# Next Steps?

   Renaming Vendor License    Renaming Features    Create and Add Report    License Monitor

Powered by Open iT ® Open iT Docs All rights reserved.

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close