Connect UniFi

The UniFi integration lets you choose a site, link it to an existing LogCentral location or create one in the setup assistant, then configure log forwarding.

Before you start

• A LogCentral organization Owner must save the UniFi API key. Owners and Members can then manage sites and their configuration. This workflow is unavailable to the Read-only role.
• The key must provide access to the site in Site Manager and to its console through Cloud Connector. A site may appear in the list while access to its settings is denied.
• Automatic setup requires an active subscription or trial, an active location and authorized source IPs.
• Automatic configuration is currently validated for UniFi Network 10.6.109. Use manual setup on other versions. Unrecognized settings or active Netconsole also block automation.

A UniFi site can only be linked to one location. A location already linked to Meraki cannot also be linked to UniFi.

1. Connect your UniFi account

1. Select the intended LogCentral organization and open Integrations.
2. On the UniFi card, click Connect UniFi.
3. Use Create a key in UniFi to open Site Manager’s API key settings.
4. Enter the key in Site Manager API key, then click Save key.

The key is stored on the server and is not displayed again after saving. Connecting does not change console settings.

2. Choose a site and location

1. Click Manage UniFi sites and search for the console or site.
2. Choose the site to configure. Check the console name: several consoles may have a site called “Default”.
3. Choose Existing location or New location.
4. For a new location, review the suggested name and click Create and continue. Your plan’s usual location limits apply.
5. Review the selected site and location, then click Associate site.

A newly created location remains inactive. Choosing a site or location does not enable log forwarding. If creation could not be confirmed, search for the location in the list before trying again.

You can also manage an association from the UniFi card in the location details.

3. Prepare reception

The assistant shows the Current UniFi destination and This location’s collector. The LogCentral destination is the IPv4 address and UDP port assigned to that location.

1. Review the detected public WAN addresses and click Authorize these IP addresses if they match the outgoing connections used by your logs.
2. If needed, click Activate this location.
3. Allow outbound UDP traffic to the collector’s address and port on your firewall.

The integration does not authorize addresses without your action. After an IP change or WAN failover, review and authorize new addresses: UniFi IPs are not synchronized automatically. For a VPN, relay or CGNAT connection, verify the actual source IP and see the authorized IP guide.

4. Configure forwarding

1. Choose the Log categories. The initial selection covers gateway, access points, switches, administrator activity, device events and client events.
2. Review the current destination. UniFi uses one remote destination in this workflow: replacing it may stop forwarding to another collector.
3. If a confirmation to replace the destination or switch from controller storage appears, read it and confirm your choice.
4. Click Configure syslog.

Additional categories depend on the events your installation produces. Default firewall policy also requires Gateway.

UniFi setting verified means LogCentral has read back the settings saved in UniFi. It does not yet confirm log reception.

Manual setup

If automatic configuration is unavailable, use the destination shown in the assistant or in the location configuration. In UniFi, open Integration → System Logging / SIEM, select the SIEM server, enter the location’s address and UDP port, and choose the categories.

Labels may vary by UniFi version. See the official UniFi log export guide. Check authorized IPs and reception after any manual setup.

5. Verify a new UniFi event

Open the location’s live logs and find a recent UniFi event corresponding to an identifiable action on the intended site. Use today’s log search if needed.

The location’s Last activity may come from another source. It does not prove UniFi reception on its own. If no event arrives, check the destination, port, UDP protocol, outgoing IPs, location activation and selected categories.

Manage an operation or remove the integration

Situation	Action
Result needs verification after a timeout	Wait at least one minute, then click Check uncertain operation. This reads the settings without sending the configuration again.
Expired preview or different settings	Click Refresh, then review the site, destination and IPs before confirming again.
Return to the previous destination	Use Restore previous destination if a backup is available. A change made directly in UniFi in the meantime must be reviewed before restoration.
Remove the link	Click Unlink site. Restore the previous destination first, or explicitly choose to keep the current destination in UniFi.
Replace the key	An Owner can save a new key in the connection settings. It must retain access to every linked site.
Disconnect UniFi	Unlink every site in the organization, then click Disconnect. This removes the key saved in LogCentral; revoking it in UniFi is a separate action.

Restoration requires a saved previous configuration. A site configured before it was linked does not receive a historical backup.

Unlinking removes the association and restoration backup but retains authorized IPs and logs already received. If you keep the UniFi destination, devices may continue sending logs. Restore or unlink the site before archiving or deleting its location: those actions do not automatically change UniFi.

If the console denies access or remains unreachable, check the key’s permissions and remote connectivity. For help, send LogCentral support the location name, Network version, displayed message and test time. Do not send your API key.