Skip to main content

Data forwarders

Lenovo XClarity One can forward data about events that occur in your environment, based on criteria (filters) that you select, to external services that you can then use to monitor and analyze the data. Every generated event is monitored to see if it matches the criteria. If it matches, the event is forwarded to the specified destination using the appropriate protocol.

To create a data forwarder, click Data forwarding in the context menu of the Settings view, click the Add icon (Add icon), and then follow instructions in the wizard.

You can test the connection to the external service from the Configure tab in the wizard before saving the data forwarder. When you click Test connection, a test event is sent using the provided configuration settings.

Event criteria​

You can define the events to forward based on the following types of criteria. If you do not provide criteria, data is forwarded for all events that are generated by all resources (managed devices, management hubs, and XClarity One portal).
  • Resources and device components that generated the events
  • Event severity

Forwarder destinations​

You can forward event data to the following destinations.

  • Email

    You can forward event data to email addresses for one or more users in the organization. You cannot forward event data to external users.

    New events that match the selected criteria are forwarded via email every hour. The emails are sent from noreply@xclarityone.lenovo.com with the subject “Buffered Event Forwarding.”

    Tip
    If you change the filter criteria for the forwarder, events that were buffered before the changes were saved will match the previous filter criteria, and events that were buffered after the changes were saved will match the latest filter criteria. So, the email that is sent after the changes were save might have some events that match the previous filter criteria.

    Events are listed in tabular format, one row per event.

  • REST web service

    You can forward event data to ServiceNow Cloud. Other user-defined REST web services are not supported.

    New events that match the selected criteria are forwarded over the network to the web service as soon as the events are raised, using the HTTPS protocol. Port 443 is used by default.

    Attention
    • Ensure that ServiceNow Cloud is configured to accept valid incoming traffic.
    • Ensure that ServiceNow Cloud uses a trusted CA-signed certificate. Self-signed certificates are not supported.
    • Ensure that you test the connection to the web service by clicking Test Connection in the Data Forwarder wizard. During the test-connection process, XClarity One imports and validates the certificate chain from the web service. After the certificate is validated, XClarity One sends a sample event to the web service.
Events are forwarded in JSON format. The following example shows event data that is forwarded to an email or web service.
{
   "id": 937,
   "createTimestamp": "2023-02-06T11:36:00.533Z",
   "description": "The Management Hub connected to the portal.",
   "eventClass": "system",
   "eventCode": "FQXXOCO1019I",
   "message": "Management Hub 192.0.2.28 connected successfully.",
   "messageArgs": ["192.0.2.28"],
   "recoveryURL": null,
   "service": "none",
   "severity": "informational",
   "source": {
      "id": "5F2B5B7AFAA4E0D8D572E02163D91D00",
      "name": "192.0.2.28",
      "type": "XClarity Management Hub",
      "uri": "/api/v1/managers-management/managers/5F2B5B7AFAA4E0D8D572E02163D91D00"
   },
   "targetResource": {
      "id": "5F2B5B7AFAA4E0D8D572E02163D91D00",
      "name": "192.0.2.28",
      "type": "XClarity Management Hub",
      "uri": "/api/v1/managers-management/managers/5F2B5B7AFAA4E0D8D572E02163D91D00"
   },
   "timestamp": "2023-02-06T11:36:00.533Z",
   "userAction": "No user action required.",
   "_lang_en": {
      "description": "The Management Hub connected to the portal",
      "eventClass": "System",
      "message": "Management Hub 192.0.2.28 connected successfully.",
      "service": "None",
      "severity": "Informational",
      "userAction": "No user action required."
   },
   "_links": {
      "rel": "self",
      "uri": "/api/v1/monitoring/events/937"
   },
   "_metadata": {
      "commonEventID": null,
      "isLocal": false,
      "msgID": null
   }
}