Moogsoft Docs

REST-based LAMs direct HTTPS Workaround

A performance issue impacts the throughput of REST-based LAMs using direct HTTPS connections. It does not affect integrations in the Moogsoft AIOps UI.

The affected LAMs are:

  • Ansible Tower
  • AppDynamics
  • AWS SNS
  • Datadog
  • Dynatrace APM Plugin
  • Dynatrace Notification
  • Fluentd
  • HP OMi Plugin
  • Microsoft SCOM
  • Nagios
  • New Relic webhook
  • Node.js
  • Node-RED
  • Oracle Enterprise Manager
  • Pingdom
  • REST LAM
  • Splunk
  • VMware vROps
  • Webhook

The issue affects the time taken to establish an HTTPS connection to the LAM. The problem occurs at a low event rate and increases as the event rate increases. It can cause a backlog at the event source, delayed events and lost events.

Note the following:

  • Nginx HTTPS to LAM HTTPS connections are affected.
  • SaaS installations using Nginx HTTPS to HTTP redirects are unaffected.
  • Direct HTTP connections are unaffected.

You can work around the problem as follows:

  • Install and configure the UI component on the LAM server.
  • Ensure Apache is not configured to start automatically, unless the LAM server is also the UI server.
  • Ensure Nginx is configured to start automatically.
  • Configure an Nginx redirect to the LAM using $MOOGSOFT_HOME/etc/cots/nginx/moog-proxies.conf . See Create a Proxy Pass for vROps for an example.

Do not run REST-based LAMs with an HTTPS connection ( use_ssl : true ) as this reintroduces the problem.