NetLock RMMNetLock RMM Docs
IV — Administration

DocBee

Connect NetLock RMM to DocBee: alerts become tickets of the mapped customer, the all-clear adds an internal message and sets the closing status, devices can be synced as customer objects, customers can be imported.

DocBee

Requirements

  • An access token, created in DocBee under the user icon in the top bar, Settings, Access Token. The token has the rights of its user, so NetLock cannot see records that the user cannot see. Use a dedicated user.
  • The user needs to read customers, locations, statuses and priorities and to write tickets and ticket messages, and for the device sync to read catalog objects and write customer objects.

Setup

  1. In Settings → Integrations, open the DocBee tile and choose Connect.
  2. Enter the Instance address and the Access token. Allow unencrypted http is for an instance on an internal network only.
  3. Under options, choose the Status of new tickets, the Status when closing and the Default priority, which DocBee requires on every ticket. Ticket category and Queue are optional.
  4. Map each tenant to a customer and its locations, or import them. Tenants without a mapping are not included.
  5. Optionally map the severities to priorities.
  6. Activate the connection.

Choose statuses that fit an automatic ticket. NetLock sets no contact on a ticket, so status e-mails to the customer contact are not sent, but a status can have other effects configured in DocBee, for example under Automation. If a category restricts its status changes, the closing status has to be reachable from the status of new tickets; otherwise the ticket stays open and the history says close_refused.

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 customer and location, with the customer object of the device if the asset sync linked one. A DocBee ticket has no title of its own, so the title is the first line of the description. The reference NetLock-Alert-<id> is stored in the external reference number.
  • When the alert ends, the ticket gets an internal message and the closing status, if nobody has taken it. A ticket that has no owner or stays with the queue of the connection counts as unassigned. Any other owner, including another queue, counts as assigned.

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 map device classes to catalog objects or choose a Default object: a customer object in DocBee always points to one.

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 becomes a customer object with the device name as extended name and NetLock-Device-<id> as number. Operating system, IP address and MAC address go into their fields, manufacturer, model and serial number into a marked block of the details. Text outside that block is kept.
  • A device with the name of an existing object of the customer is linked to that object, provided that exactly one such object exists, it has no number yet and no other device holds it.
  • An update sends only the values NetLock knows. Anything else you entered in DocBee is kept.
  • A device that moved to another tenant or location moves its object. If DocBee refuses that, the device is named in the history and tried again; the change is not marked as done.
  • 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 DocBee.

Known limits

  • When a job is repeated, NetLock looks for the ticket among the 200 newest tickets of the customer. An older ticket is not found, and a second ticket can open.