A query that runs on its own on the Engines, on chosen days at a time or every few hours, and saves each result to the database. Saved data stays in the database until you delete it.

An NXQL query on a schedule, with conditions on its result: what matches becomes an incident in your ITSM tool, gets a work note while it keeps matching, and is resolved once it stops. A new rule starts disabled: use Test rule to see what it would do (nothing is sent), then enable it. Only administrators change rules.

An NXQL query on a schedule whose rows are written into a table of your ITSM tool: the CMDB (ServiceNow's identification rules prevent duplicate CIs), users, or any table. Records are created or updated by their key, only what changed is sent, and nothing is ever deleted. A new sync starts disabled: Test sync shows what it would write (nothing is sent), even from sample rows you paste. Only administrators change syncs.

When a device moves to another Engine (role-based Collector assignment), its old record stays behind and still uses a license. A check groups the records of every Engine by device, keeps the newest (by last seen), and lists the old ones to remove from each Engine. On the next run it sees which ones are gone. V6 has no API to delete a device: remove them in Finder (the steps are with each list), or let the Engine purge them after its inactivity period.

Power BI Desktop reads the saved results straight from the results database, with a read-only login. A ready-made dashboard is a Power BI project (.pbip) over the saved results you choose: tables, links between them (the same device in two results), measures and pages; each refresh in Power BI shows the newest saves.

A report is a set of sections (key numbers, gauges, bar and pie charts, trend lines, tables) drawn from NXQL run across your Engines when the report is made, or from saved results: their newest save, or their last saves for a trend. Start from a template, let the connector design one from your data, or build it section by section. Every report is shared with every account.

Every query run, newest first. A run's merged result is kept as a file on the server for 30 days, for previews and downloads; what was saved to the database stays there until you delete it.

The Engines, the Portal and this connector, checked every 15 minutes: the Web API, the console (port 99), the services and the disks, the certificates and the devices seen. A problem is emailed when it starts and when it clears, after two checks in a row, and a health report is emailed every day.

Duplicate devices

The last run of each duplicate check (Duplicates tab), also in the daily report.

The V6 Engines queried through their Web API (https://<engine>:1671/2/query), with an account that has the Web API right, such as the one the NXQL Editor uses. Passwords are stored encrypted and never shown again. Only administrators add or change Engines.

Where alerts become incidents (and, later, where the CMDB is fed): ServiceNow, or any tool with an HTTP API through a generic webhook. The connector only calls out over HTTPS, so ServiceNow needs no MID server. Passwords and tokens are stored encrypted and never shown again. Only administrators add, change or send test incidents.

Every incident opened, updated or resolved (and every test), newest first.

Who can sign in. Every account uses the same Engines, query library and saved results; administrators also manage the Engines and the accounts. An account you create, or whose password you reset, chooses its own password at its next sign-in. On the server, docker exec -it nexthink-v6-connector python -m app.auth reset-password <user> also resets one.

The mail server the connector sends through: the health problems and the daily health report (Health tab). The password is stored encrypted and never shown again.

Install the connector on another machine, without Docker: on a Windows server or PC, or on Linux (CentOS/RHEL 7 and later, Rocky/Alma, Ubuntu, Debian; x86_64). Each brings everything it needs, runs as a service, and asks which ports the web page uses. Every connector installed with them offers both installers here.

Who did what, when and from where: every change, sign-in, run, download of data, and every action that was refused. Nobody can change or delete an entry, administrators included. Verify integrity checks that no entry was changed or removed since it was written.