As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

Best Practices

  • To reduce the performance impact of log file collection, collection intervals need to be kept small. Recommended approach is to set this interval to be twice the required log file transfer time.
  • Configure the max transfer rate for log collection to preserve network capacity for other system components.
  • Turn off Anti virus checking on the LFMT Server host.
  • If possible, use a dedicated network interface for log file transferring.
  • Set a low process priority for the RSYNC utility to force it to execute as a background task.
  • Schedule the frequency of log collection to prevent starting a new log file transferring job before a previous job is finished.
  • If your Genesys solution is hosted in more than one site linked via WAN, deploy an LFMT server per site. Avoid transmitting large amounts of data via WAN unless the links have sufficient bandwidth.
  • Do not use more than three scrubbing and indexing regular expressions each.
  • Set up scrubbing and indexing for only those application types that are required.
  • Set a low quality of service (QoS) value for network traffic generated by LFMT.
  • Ensure that network traffic generated by Genesys application servers has a higher priority LFMT traffic.
  • If possible, use a dedicated VLAN or LAN for LFMT traffic.
  • During the initial deployment of LFMT, consider a phased approach for adding application servers to the log collection process.
  • Monitor the performance impact of LFMT on each application server during the initial deployment.
This page was last edited on November 29, 2019, at 14:41.


Comment on this article:

blog comments powered by Disqus