Jump to: navigation, search

Best Practices

This section lists some best practices administrators and users should review for optimal deployment, configuration, and operation of LFMT.

  • Deploy a separate LFMT Indexer/Collector pair(s) at each Data-Center if they are geographically distributed.
  • Deploy each LFMT Database in a RDBMS within the same local as the associated LFMT Indexer/Collector pair.
  • During the initial deployment of LFMT, consider a phased approach for adding Application servers (i.e. sip, urs, stat, gvp etc) to the log collection process.
  • Monitor the performance impact of LFMT on each Application server (i.e. sip, urs, stat, gvp etc) during the initial deployment.
  • To reduce the performance impact of log file collection set the LFMT Collection Schedule Interval to be twice the required log file transfer time.
  • Limit the LFMT custom Indexes for each Application/Application type; a general rule is 3 per Application.
  • Set up LFMT Scrubbing and Indexing for only those Application Types that are required.
  • Turn off Anti-virus checking on the LFMT Server Host(s).
  • Ensure that network traffic generated by Genesys application servers has a higher priority LFMT traffic.
  • Set a low quality of service (QoS) value for network traffic generated by LFMT.
  • If possible, use a dedicated VLAN or LAN for LFMT traffic.
This page was last edited on October 11, 2021, at 13:31.
Comments or questions about this documentation? Contact us for support!