---
title: "Connecting usage data"
description: "Connect real traffic data to Flux: map a LibreNMS, Generic, Meraki, or UniFi data source per circuit, using signed webhooks or polled API credentials."
---

> Documentation Index
> Fetch the complete documentation index at: https://support.vigilis.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting usage data

The Network section (branded "Flux" in some places) is for admins and needs the Network add-on on your plan. Depending on your plan and role you may not see it in the sidebar. If you think it should be part of your plan, ask your provider.

[Auto-Flux](/network/auto-flux/) and the rightsizing view need real traffic data to make decisions. You connect that data per circuit, on the circuit's **Data Sources** tab, plus a one-time credential step on the org **Integrations** tab.

## Data source mappings

On a circuit's **Data Sources** tab, add a mapping with a source type and its fields:

- **LibreNMS**: a **device ID** and a **port ID**.
- **Generic webhook**: a **Service Key** that you also include in each webhook body.
- **Meraki**: a **network ID**, an **uplink** (WAN 1, WAN 2, or Cellular), and an optional **serial**.
- **UniFi**: a **console (host) ID**, a **network site ID**, and a **gateway device ID**.

On any source type you can also set an optional **display name** and a **capacity** in Mbps.

## Push path (webhooks)

LibreNMS, and any tool that can POST signed JSON, sends utilization to Vigilis. On the org **Integrations** tab, generate the webhook's shared **secret**. It is shown only once, so copy it then. Each request is signed with that secret and verified on arrival. The payload carries in and out utilization percentages, and optionally a capacity and a timestamp.

## Pull path (polling)

For **Meraki** (an API key plus organization ID) or **UniFi** (an API key plus host), set the credentials on the **Integrations** tab and Vigilis polls usage about every 5 minutes. No separate monitoring tool is needed.

## When data is missing or stale

If data is missing or stale, Auto-Flux simply holds the current speed. It never scales on old readings, so a monitoring gap results in no change rather than a wrong one. Scaling resumes automatically once fresh readings come in.

## Related

- [Auto-Flux](/network/auto-flux/) for how the usage data drives automatic scaling, including its stale-data hold.
- [Circuit connections](/network/circuit-connections/) for syncing your circuit inventory before you map data sources.
- [Organization settings](/administration/organization-settings/) for the Integrations tab where secrets and API keys live.

## Common questions

**What happens to a circuit when its usage data goes missing or stale?**

Auto-Flux holds the current speed. It never scales on stale readings, so a monitoring outage cannot trigger an unwanted change; it simply waits for fresh data to resume.

**Do I need a monitoring tool to feed usage data to Vigilis?**

Not for Meraki or UniFi. Set your API credentials on the Integrations tab and Vigilis polls usage about every 5 minutes. For LibreNMS or other tools, push signed webhooks instead.

Source: https://support.vigilis.io/network/setting-up-network/index.mdx