Skip to content

ERP Integration (DATAZONE ERP) ​

The ERP integration optionally connects DATAZONE Control with the DATAZONE ERP. It is off by default; an update never sends data on its own. Without the ERP, Control keeps working in full.

The integration works in two directions:

DirectionWhat happens
Customer pull (ERP -> Control)Control pulls the complete customer list from the ERP and keeps it locally. Technicians can therefore assign hosts to customers that have no hosts in Control yet.
Inventory push (Control -> ERP)Control reports per customer which products are monitored (features with counts). The ERP uses this for segments such as "all PVE customers without PBS".

Setup ​

Path: sidebar Administration → Settings > ERP Integration. Visible to administrators only.

FieldDescription
Integration activeEnables pull and push. Address and secret must be set before enabling.
ERP addressBase address without path, e.g. http://10.0.0.12:8000. The endpoints are appended.
SecretThe same secret as in the ERP under Settings > Integrations > DATAZONE Control. Write-only, never displayed.
Customer pull intervalMinutes between incremental pulls (default 60).
Inventory check intervalMinutes between inventory change checks (default 5).
Nightly runTime (UTC) for the daily full customer pull and the full inventory of all customers.

Procedure:

  1. Create the secret in the ERP and enable the inventory integration there.
  2. Enter address and secret in Control and click Test connection.
  3. Tick Integration active and Save.
  4. Optionally click Pull customers now and Send inventory now for the initial sync. Otherwise the background job does it within minutes.

TIP

The connection test also works while the integration is disabled. It checks reachability and secret without changing any data.

Customer pull ​

  • Matching is done strictly by customer number as a string. Names are display-only because they are not unique in the ERP and may change.
  • The ERP overwrites name, name suffix, city and the active flag. Control-specific fields (tags, Wazuh level, contact) are kept.
  • Inactive customers are included and remain selectable, but are marked and sorted last in pick lists.
  • Customers that exist in Control but not in the ERP list are never deleted; they are flagged not in ERP.
  • While the integration is active, customers cannot be created in Control. New customers are created in the ERP and appear after the next pull.
  • An empty full list from the ERP is discarded; the local state is kept. If the ERP is unreachable, Control continues with the last known state.

Inventory push ​

Reported features (lower-case keys):

KeySourceCount
pveProxmox VE modulePVE hosts
pve_vmProxmox VE moduleVMs + containers across all PVE hosts
pbsProxmox Backup Server modulePBS hosts
opnsenseOPNsense modulefirewalls
windowsWindows modulemonitored Windows machines (agent only)
linuxLinux modulemonitored Linux machines (agent only; PVE/PBS hosts excluded)
vmwarehardware vendor of agent hostshosts running as VMs on VMware (weak signal)
veeamWindows software inventoryhosts with Veeam Backup & Replication (weak signal, no agents/plug-ins)

Each feature carries the oldest known date (seit) and the host names (ref) so the ERP can trace its origin.

Rules:

  • Every report is a full inventory of the customer: features not listed count as removed in the ERP (dated there, never deleted).
  • Control detects changes via a hash of the last reported state and only reports changed customers. Customers without hosts that were reported before are reported once with an empty list.
  • Failed reports stay pending and are retried with increasing delay (up to 60 minutes). The nightly run sends all customers and heals lost single reports.
  • The signature is an HMAC-SHA256 over the raw bytes sent (X-DC-Signature: sha256=<hex>).
  • If the ERP answers with ok: false, the report counts as rejected and stays pending. Manual and background runs lock each other out; a parallel start is rejected with a notice.
  • The Integration active switch only takes effect with address and secret set; the connection test works regardless.

Status and control ​

The tab shows last success, counts, trigger (manual, automatic, nightly) and last error for both customer pull and inventory push. Unknown customer numbers and unknown feature keys from the ERP response are displayed and written to the audit log.

The preview lists per customer what Control would report and whether the report is pending or already sent.

Data quality

windows and linux count machines with a DATAZONE agent only, not the customer's full estate. vmware and veeam are based on a few agent hosts and are meant as sales signals, not as inventory.

DATAZONE Control Documentation