NetLock RMMNetLock RMM Docs
IV — Administration

ITFlow

Connect NetLock RMM to a self-hosted ITFlow: alerts become tickets, the all-clear adds an internal reply and resolves or closes the ticket, devices can be synced as assets, clients and locations can be imported.

ITFlow

Requirements

  • A self-hosted ITFlow instance, version 26.08 or newer. Older versions have no API for replies; the test of the connection shows that.
  • An API key, created in ITFlow under Admin, API keys. A key runs as its ITFlow user, with that user's role and client access, and has no separate limits. Use a dedicated user with access to the mapped clients only, and with the support module for tickets.

Setup

  1. In Settings → Integrations, open the ITFlow tile and choose Connect.
  2. Enter the Instance address and the API key. Allow unencrypted http is for an instance on an internal network only.
  3. Under options, decide whether tickets are closed or only resolved at an all-clear, see below.
  4. Map each tenant to a client and its locations, or import them. Tenants without a mapping are not included. Without a severity mapping the four severities follow the four priorities.
  5. Activate the connection.

What goes to the vendor

For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.

With the asset sync on, also: device name, operating system, manufacturer, model, serial number, IP address and MAC address.

What happens to a ticket

  • An alert becomes a ticket of the mapped client, with the asset of the device if the asset sync linked one. The subject ends in [NetLock-Alert-<id>], and the reference is also stored in the vendor ticket number.
  • When the alert ends, the ticket gets an internal reply and is resolved if nobody is assigned. With Close tickets instead of resolving them it is closed as well.

The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.

Asset sync

The sync is off by default. Switch on Sync devices as assets, and optionally map device classes to asset types or enter a Default asset type, which is free text in ITFlow.

Every hour NetLock sends the authorized devices of the mapped tenants that changed since the last run, at most 200 per run; if more devices changed, the next run starts right after. Synchronize now starts a run immediately.

  • A device with the name of an existing asset of its client is linked to that asset, provided that exactly one such asset exists, it is not archived and no other device holds it. Otherwise a new asset is created.
  • An update sends only the values NetLock knows. Anything else you entered in ITFlow is kept.
  • A device that moved to another tenant gets a new asset at the new client. The old asset stays.
  • A device that fails is named in the history and waits for the next hourly run; the other devices are still processed.

Nothing is deleted in ITFlow.

Known limits

  • For read requests, ITFlow accepts the key only in the request URL, so it appears in the access log of your ITFlow web server. NetLock keeps it out of its own history and logs. Use a dedicated key.
  • API keys of ITFlow expire. The connection then shows that the credentials are invalid or expired; create a new key and use Replace credentials.
  • ITFlow has no search for tickets. When a job has to be repeated, NetLock reads the tickets of the client to find out whether the ticket already exists. If it cannot read all of them, the job ends as failed without a new ticket, and you decide whether to use Send again.