This connector allows for integrations between Logic Monitor and a PSA (Professional Services Automation) tool like Xurrent.

PSA - Generate Ticket

The PSA endpoint listening for Logic Monitor webhooks to generate a ticket.

This trigger listens to Custom PSA Integration messages from Logic Monitor. To configure the integration in Logic Monitor go to Settings → Integrations → Add → Custom HTTP integration.. Then choose the following:

• Choose your PSA Solution: Custom PSA
• API Credentials
• Password: Set any value and ignore (required, but not used)
• API Ticket generation:
• Ticketing Endpoint URL: The trigger endpoint, e.g. https://trigger.ipaas.xurrent.com/inbound/1/d4b8ddd0-b8ba/01922296-df4a
• User Name: Any user name that matches the user name in the inbound connection configuration.
• Password: Any password that matches the password in the inbound connection configuration.

Register LM user

If the Logic Monitor connector will be used for multiple Logic Monitor customers this action is required to generate a password for each customer.

Once this action completes, the customer needs to be informed on how to configure their Custom PSD Integration in Logic Monitor. All information required during that setup is provided in the action output.

If the Logic Monitor connector will be used for multiple customers the "(Un)Registers LM user" actions are required to generate passwords for each customer. The setup works as follows:

• In the inbound connection configuration leave the "User Name" and "Password" fields empty.
• Create a runbook that is triggered for each new customer and use the "Register LM user" action to generate a password for the customer.
• The user name that is provided in the configuration should contain a unique ID for the customer.
• Also provide the runbook that is using the "PSA - Generate Ticket" trigger.
• Each customer needs to be informed on how to configure their Custom PSD Integration in Logic Monitor. All information required for that setup is provided in the "Register LM user" action output.
• When the "PSA - Generate Ticket" runbook is triggered, the password is automatically validated and the User Name identifying the customer is available in the trigger output.
• Do not forget to create another runbook that is triggered on customer removal that uses the "Unregister LM user" action to remove the access for that customer.

Unregister LM user

If the Logic Monitor connector will be used for multiple Logic Monitor customers this action is required to remove the generated password for a given customer when they no longer require the integration.

Once this action completes subsequent calls to the "PSA - Generate Ticket" trigger for this customer will fail.

Fetch devices from Logic Monitor CMDB

Retrieves a comprehensive list of devices from Logic Monitor CMDB (Configuration Management Database), including detailed device information for device management and asset tracking.

Input:

• Last sync datetime (optional) - for incremental synchronization (filters devices updated after this time)
• Page size (1-1000, default: 100) - Number of devices to return per page

Output:

• Complete list of all devices with comprehensive information including:
• Device identification (ID, name, display name)
• System properties (array of {name, value} objects from Logic Monitor)
• All results automatically retrieved across all pages (pagination handled internally)
• Pagination continues until a page with fewer items than the page size is returned (or no items at all)

Use Case: Device inventory management, CMDB synchronization, asset tracking, integration with IT service management systems, device discovery and mapping

Example Input:

{
"last_sync": "2024-01-01T00:00:00Z",
"page_size": 100
}

Example Output:

{
"total": 606,
"has_next_page": true,
"devices": [
  {
    "device_id": 1,
    "name": "LMAWSACCOUNT-17",
    "display_name": "DevOps Account",
    "system_properties": [{"name":"system.device.provider","value":"AWS"},{"name":"system.hostname","value":"LMAWSACCOUNT-17"}]
  }
]
}

Authentication: Requires a permanent bearer token configured in the outbound connection.
Rate Limit: 700 requests per minute (automatic backoff on 429 errors).