NetLock RMMNetLock RMM Docs
IV — Administration

ServiceNow

Connect NetLock RMM to ServiceNow: alerts become incidents of the mapped company, the all-clear adds work notes and resolves the incident, companies can be imported as tenants. Incidents only, no CMDB.

ServiceNow

Requirements

  • A ServiceNow instance under service-now.com.
  • An integration user with the role itil and read access to core_company, sys_user_group and sys_choice.
  • As an alternative, an OAuth client with client id and secret. The client credentials grant is off by default: an administrator of the instance has to switch it on and specify the user the client acts as. See Client credentials grant workflow.

Setup

  1. In Settings → Integrations, open the ServiceNow tile and choose Connect.
  2. Enter the Instance address, for example https://yourcompany.service-now.com. Only addresses under service-now.com are accepted.
  3. Enter the Login name and Password of the integration user, or the OAuth client ID and OAuth client secret. With a client id, the user fields are ignored.
  4. Under options, choose the Close code an incident is resolved with. The values come from your instance. Group sets the assignment group. Caller expects the sys_id of a user, for an instance that requires a caller.
  5. Map each tenant to a company, or import companies as tenants. Tenants without a mapping are not included. Severities follow the impact and urgency of the default priority lookup unless they are mapped.
  6. 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.

What happens to a ticket

  • An alert becomes an incident of the mapped company. The reference NetLock-Alert-<id> is stored in the correlation_id, which NetLock uses to find the incident again.
  • When the alert ends, the incident gets work notes and is set to Resolved with the chosen close code and the note as close notes, if nobody is 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.

Known limits

  • Incidents only. NetLock writes nothing to the CMDB.
  • Domain separation is not supported.
  • If a data policy or business rule stops the resolve, or the instance answers without the new state, the note is kept and the incident stays open. The history shows close_refused.
  • If the instance refuses the work notes, the incident is left unchanged. The history shows note_refused.
  • NetLock does not change closed or canceled incidents.
  • If NetLock cannot confirm whether an incident exists, the job ends as failed and no second incident is created. Use an account without row filters on incidents.
  • Rate limits are configured on your instance. When a limit is reached, the instance answers with 429, and the jobs wait for the time it specifies.