Skip to main content

TurboFloat Server

Introduction​

Open iT supports TurboFloat usage reporting starting Open iT version 10.2.570.

note

Tested and verified with TurboFloat Server 4.3.0.0.

An Open iT Core 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


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

warning

Apply the configurations in the Open iT Core Client.

Requirements​

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

Specifying TurboFloat Log File Path and Pattern​

These are the steps to specify the path to the TurboFloat 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-turbofloat.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 TurboFloat log files, run the command:

    Command Syntax
    openit_confinit -c "logfilecollector-turbofloat.logfilecollector.source.dir=<turbofloat_log_dir>"

    where <turbofloat_log_dir> is the location of the TurboFloat log files, which is usually next to the TurboFloat Server executable.

    Example
    openit_confinit -c "logfilecollector-turbofloat.logfilecollector.source.dir=C:\Program Files\TurboFloat"
    Sample Log File Content
    time:time|event_type:string|product:string::*|feature:string|user:string|host:string|server:string|status:string|details:string
    3806479528000|creating a thread pool|MNL000WIN;turbofloat|turbofloat|||MNL000WIN|1|
    3806479528000|New lease assigned|MNL000WIN;turbofloat|turbofloat|upsi5i|149.191.228.231|MNL000WIN|3|
    3806479658000|Lease was released by client|MNL000WIN;turbofloat|turbofloat|upsi5i|149.191.228.231|MNL000WIN|4|
    3806479658000|Extended existing lease|MNL000WIN;turbofloat|turbofloat|loguj3|149.180.48.137|MNL000WIN|30|
    3806479658000|Lease has expired|MNL000WIN;turbofloat|turbofloat|uttehl|149.191.255.191|MNL000WIN|6|
    3806479658000|License lease request rejected|MNL000WIN;turbofloat|turbofloat|||MNL000WIN|20|no more free slots
    3806479658000|stopping in response to signal|MNL000WIN;turbofloat|turbofloat|||MNL000WIN|2|

  5. (Optional) If the log file does not have a .log extension, run the command:

    Command Syntax
    openit_confinit -c "logfilecollector-turbofloat.logfilecollector.source.pattern=<log_pattern>"

    where <log_pattern> is the log file name pattern.

    Example
    openit_confinit -c "logfilecollector-turbofloat.logfilecollector.source.pattern=*.txt"

  6. Update the configuration file, run the command:

    Command Syntax
    openit_confbuilder --client

    Make sure no errors are encountered.

Advanced Configuration

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

Object NameAccepted ValueDescription
source.dirDirName (e.g., C:\Program Files\TurboFloat)Location of the TurboFloat log files.
source.patternString (e.g., *.log)The glob pattern identifying source files in the source directory.
source.seenString (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.cmplinesInteger (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.dirDirName (i.e., ${OpeniT.directories.temp}/LogFileCollector)This is the location of the directory containing the collected log data.
target.moduleString (i.e., license)The target type of module (in general).
target.datatypeString (i.e., turbofloat)The specific type of target data.
target.intervalTimespan (e.g., P30S, P5M, P1D)The span of time between collector runs.
target.rotation-sizeInteger (e.g., 6, 10, 20)The log file rotates if it goes beyond the number (in mb) defined.
target.rotation-globString (e.g., *)The glob pattern to match before the log file rotates.
TurboFloat Log File Collection Configuration

TurboFloat Events Log File Collection Configuration​

Activating this produces the following aggregated data types used for historical reporting:

Activating Event Log Data Collection​

These are the required steps to activate the collection of the TurboFloat log file for events.

  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 TurboFloat events log data, run the command:

    Command Syntax
    openit_oconfinit -u "collect_license_turbofloat_event-logs.root.scheduler.jobs.collect_turbofloat_licenselogs-events.general.active=true"
Advanced Configuration

The collection runs every 5 minutes by default. To configure the intervals, update the collect_license_turbofloat_event-logs.oconf file in the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler. Locate the instances attribute under collect_turbofloat_licenselogs-events, preprocess_turbofloat_licenselogs-events, or transfer_turbofloat_licenselogs-events in the same file and configure the attributes.

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

Attribute NameAccepted ValueDescription
max-instancesUint (e.g., 5, 8, 9)The number of instances allowed to run the at the same time.
max-handlingString (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-timeoutTimespan (e.g., P30S, P5M, P1H)The maximum waiting time before terminating a running instance.
quarantineTimespan (e.g., P30S, P5M, P1H)The waiting time before starting a new instance after a previous one.
TurboFloat Log Job Scheduler Instances Configuration

Modifying Event Type Data Feature Name​

These are the required steps to modify the feature name for event log data if you don't want to use the default, turbofloat.

  1. Go to the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration, and open matchobjects-event-turbofloat.oconf.

  2. Locate the data-process2 node under the post-processing node and change the value of value=feature to your desired feature name.

    matchobjects-event-turbofloat.oconf
    data-process2
    {
        description=Feature name.
        type=string
        value=feature=(feature!="") ? feature :"TurboFloatFeature"
    }
    warning

    You can use any character except \/:*?"<>|.

  3. Save the changes.

Verifying Event Log Data Collection​

After configuration, you can verify that the data can be collected and parsed into the Open iT format successfully:

  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. Verify that Open iT can collect raw data, run the command:

    Command Syntax
    openit_logfilecollector -c "<config_dir>\logfilecollector-turbofloat.conf"

    where <config_dir> is the absolute path to the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

    Example
    openit_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-turbofloat.conf"

  4. Once done, verify that there are *.status and raw-turbofloat-license-LogFileCollector*.data files created in the LogFileCollector directory which is by default in C:\ProgramData\OpeniT\Data\temp\LogFileCollector.

  5. Verify that Open iT can parse the collected raw data to the Open iT format, run the command:

    Command Syntax
    openit_logparserturbofloat --srcdir "C:\ProgramData\OpeniT\Data\temp\LogFileCollector" --srcpattern raw-turbofloat-license-LogFileCollector*.data --srcfilehandling rename --trgdir "C:\ProgramData\OpeniT\Data\temp\LogParserTurboFloat" --module license --datatype event --resolution PT1H --matchobjects "C:\Program Files\OpeniT\Core\Configuration\matchobjects-event-turbofloat.oconf" --type event --disable-statlogging --debug warning

  6. Once done, verify that there are event-license-LogParserTurboFloat*.data files created in the LogParserTurboFloat directory, which is by default in C:\ProgramData\OpeniT\Data\temp\LogParserTurboFloat.

TurboFloat Records Log File Collection Configuration​

Activating this produces the following aggregated data types used for historical and real-time reporting:

Activating Record Log Data Collection​

These are the required steps to activate the collection of the TurboFloat log file for records.

  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 TurboFloat records log data, run the command:

    Command Syntax
    openit_oconfinit -u "collect_license_turbofloat_record-logs.root.scheduler.jobs.collect_turbofloat_licenselogs-records.general.active=true"
Advanced Configuration

The collection runs every 5 minutes by default. To configure the intervals, update the collect_license_turbofloat_record-logs.oconf file in the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler. Locate the instances attribute under collect_turbofloat_licenselogs-records, preprocess_turbofloat_licenselogs-records, or transfer_turbofloat_licenselogs-records in the same file and configure the attributes.

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

Attribute NameAccepted ValueDescription
max-instancesUint (e.g., 5, 8, 9)The number of instances allowed to run at the same time.
max-handlingString (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-timeoutTimespan (e.g., P30S, P5M, P1H)The maximum waiting time before terminating a running instance.
quarantineTimespan (e.g., P30S, P5M, P1H)The waiting time before starting a new instance after a previous one.
TurboFloat Log Job Scheduler Instances Configuration

Modifying Record Type Data Feature Name​

These are the required steps to modify the feature name for record log data if you don't want to use the default, turbofloat.

  1. Go to the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration, and open matchobjects-record-turbofloat.oconf.

  2. Locate the data-process2 node under the post-processing node and change the value of value=feature to your desired feature name.

    matchobjects-record-turbofloat.oconf
    data-process2
    {
        description=Feature name.
        type=string
        value=feature="TurboFloatFeature"
    }
    warning

    You can use any character except \/:*?"<>|.

  3. Save the changes.

Verifying Record Log data Collection​

After configuration, you can verify that the data can be collected and parsed into the Open iT format successfully:

  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. Verify that Open iT can collect raw data, run the command:

    Command Syntax
    openit_logfilecollector -c "<config_dir>\logfilecollector-turbofloat.conf" --target "<temp_dir>\Raw.TurboFloat.Record"

    where:

    • <config_dir> is the absolute path to the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration
    • <temp_dir> is the absolute path to the temp directory, which is by default C:\ProgramData\OpeniT\Data\temp

    Example
    openit_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-turbofloat.conf" --target "C:\ProgramData\OpeniT\Data\temp\Raw.TurboFloat.Record"

  4. Once done, verify that there are *.status and raw-turbofloat-license-logfilecollector*.data files created in the Raw.TurboFloat.Record directory, which is by default in C:\ProgramData\OpeniT\Data\temp\Raw.TurboFloat.Record.

  5. Verify that Open iT can parse the collected raw data into the Open iT format, run the command:

    Command Syntax
    openit_logparserturbofloat --srcdir "C:\ProgramData\OpeniT\Data\temp\Raw.TurboFloat.Record" --srcpattern raw-turbofloat-license-LogFileCollector*.data --srcfilehandling delete --trgdir "C:\ProgramData\OpeniT\Data\temp\LogParserTurboFloat" --module license --datatype record --resolution PT1H --matchobjects "C:\Program Files\OpeniT\Core\Configuration\matchobjects-record-turbofloat.oconf" --type record --debug warning

  6. Once done, verify that there are record-license-LogParserTurboFloat*.data files created in the LogParserTurboFloat directory, which is by default in C:\ProgramData\OpeniT\Data\temp\LogParserTurboFloat.

Sample Reports​

Historical Reports​

Utilization Trend​

This sample report provides a visual representation of license activity for the selected application. It helps users and administrators quickly understand how licenses are being used, when peak demand occurs, and whether any access issues (such as denials) are happening.
It offers several key benefits:

  • Centralized Visibility – provides a clear view of license usage, availability, and denials in a single interface.
  • Optimized License Allocation – helps ensure you are not over-purchasing licenses you don't need or under-provisioning.
  • Cost Savings – identifies opportunities to downgrade or redistribute licenses, reducing unnecessary expenses.
  • Usage Trends & Capacity Planning – shows peak usage patterns, allowing better forecasting for future needs.
  • Avoiding Service Disruptions – helps prevent situations where users cannot access software due to reaching the license limit.
  • Compliance & Audit Readiness – provides a usage record to ensure compliance with vendor agreements and avoid penalties.
  • Performance & Productivity Insights – helps assess whether certain teams or departments are under-utilizing or over-utilizing software.
  • Historical and Real-Time Analysis – combines near real-time monitoring with historical trend analysis, enabling both immediate decision-making and long-term planning.

Utilization Trend

Utilization Trend

License Efficiency​

This sample report gives you helpful insights on how much time a software license has been used. It shows whether licenses are being actively used or left idle, giving you a quick way to understand how efficiently your licenses are being managed.
It offers several key benefits:

  • License Utilization Tracking – monitors how long licenses are in use during a given period and see if any licenses are not being used so they can be reassigned.
  • Optimized License Allocation – helps ensure you are not over-purchasing licenses you don't need or under-provisioning.
  • Cost Savings – identifies opportunities to downgrade or redistribute licenses, reducing unnecessary expenses.
  • Compliance & Audit Readiness – provides a usage record to ensure compliance with vendor agreements and avoid penalties.

License Efficiency

License Efficiency

Heatmap​

This sample report provides a visual representation of license usage by day of the week and hour of the day for the selected application.
It offers several key benefits:

  • Peak Usage Identification – highlights the specific days and hours with the highest demand for licenses.
  • Workload Distribution – helps balance activity by identifying underutilized periods where tasks can be scheduled.
  • Resource Planning – supports better allocation of licenses by anticipating peak and off-peak usage times.
  • User Behavior Insights – reveals patterns in how and when users access software, such as evening or weekday activity.
  • Avoiding Bottlenecks – reduces delays by planning critical tasks during low-usage hours.
  • Historical & Predictive Trends – combines weekly usage patterns with historical insights to inform long-term planning and decision-making.

Heatmap

Heatmap

Real-time Report​

This sample report shows a drilled-down feature view of the online licenses in use and the licenses available.

License Monitor Portal

License Monitor Portal

Next Steps?​

Renaming Vendor License
Renaming Features
Analysis Server: License Monitor Portal
Analysis Server: Reporting