Share your ideas

Multi-threaded DOM Capture Virtual Hit Session Agent

The DOM capture virtual hit session agent is single threaded and causes a transport pipeline bottleneck. This session agent is useful and needs to be made multi-threaded to be able to handle higher volumes of traffic. Similar to HBR child pipelines or, even better, have it automatically add/remove pipelines based on volume.

  • Wesley Thompson
  • Apr 30 2020
  • Under consideration
Experience Analytics On-Premise / Other
How will this idea be used?

High volume will be handled by the DOM Capture Virtual hit agent without backing up.

×

Attachments Open full size

What is your industry? Insurance
What is the idea priority? Medium
  • May 7, 2020

    Admin response

    Hi, Wes -

    Thank you for this. It's likely that the logging functionality in the pipeline is preventing the agent from being used in child pipelines without the use of HBREx. Until the agent is updated, there are a couple of options:

    • Use HBREx to put child pipelines in separate processes

    • Disable logging for the agent, which should allow the use of the agent in child pipelines without the use of HBREx, but it won't have the memory efficiency of HBREx. This is done by adding "EnableLogFile=false" to the config section.

    Here's some information about the topic: https://help.goacoustic.com/hc/en-us/articles/360044239713-Manage-pipelines-with-the-TMS-Pipeline-Editor

    Let us know your experience with these options.

    Best regards,

    Rob Hain
    Sr Product Manager
    Acoustic

Related ideas