HTTP Client Device Engines

HTTP Client Device Engines are provided to enable the integration of web-based APIs that accept HTTP GET/POST with xMatters; this Device Engine is intended for use with HTTP xMatters SMS and HTTP Generic Protocol Providers.

HTTP Client Engine details

Details

Description

Name

Name used to identify this Device Engine.

Description

Brief description of this Device Engine (optional).

Notification Polling (sec)

How often (in seconds) the Device Engine polls the notification node for new alerts. Must be a whole number greater than or equal to 10 and less than or equal to 300.

Concurrent Threads

Number of requests or tasks that this Device Engine can run at the same time. Your Active Licenses control the maximum number of available threads.

Response Message

Portion of the notification message that contains the response instructions.

Guidelines:

  • This field should inform Users that when responding to a plain-text alert, they should type the keyword “RESPONSE” in the subject line, followed by a single space, and then one of the options listed. For example, they might respond with "RESPONSE ACCEPT".

Also note that this response should be the only text in either the subject of the email, or the first line in the body of the email message.

If you have configured simple SMS replies, as described in Configuring simple SMS replies, this field should be changed to reflect the new response process. The recommended value is "Reply %Response Choices%".

  • If you are configuring this Device Engine to work with a fax provider (e.g., Phaxio), the response instructions should indicate that Users should not attempt to fax their response back to xMatters, but should instead call in, or log in to the web user interface, to respond.

Logging

For an explanation of Device Engine logging, see Enabling Device Engine logging.