Rate Limit Throttle Message Disable

Sure, so LM can do various things with alerts. We can send emails (what you're currently doing). We can call you on your phone. We can send you an SMS text. Additionally, we can do something often referred to as a web hook. This means that LM will "execute" an HTTP request for each alert. This execution is similar to you putting an address in your browser and clicking go. The request is made, in this case, from your browser and the results come back to your browser. This is how all web browsing works. 

In the case of an alert integration within LM, LM can make an HTTP request when an alert comes through. All we really need to know is what URL to request from Cherwell that results in a ticket being created. Normally that's done with a special kind of request called a POST. So, all we need to know from Cherwell is what URL we need to post to in order to create a ticket. Usually, they'll also include some documentation that details how we can pass over the information from the alert (device name, datapoint, current value, etc.). 

Usually, sending alerts to a ticketing system via this mechanism has a few advantages, the primary being lower latency than email. It also continues to work even if the sending email server or Cherwell's receiving email server have issues.

More on our capabilities around this here: https://www.logicmonitor.com/support/alerts/integrations/custom-http-delivery