Connect Data Ingestion

This page explains the three methods available for feeding network data into Kudzu Canopy NOC and helps you choose the right one for your deployment.

Before you begin#

Complete the network onboarding checklist so that your network exists in the platform.
Have your LNS credentials or upstream webhook configuration ready.

Ingestion methods#

LNS integration (recommended)#

An LNS integration connects Canopy NOC directly to your LoRaWAN Network Server. This method provides the richest data — uplinks, downlinks, gateway statistics, and device identity — and supports automatic synchronization of device and gateway inventories.

Use this method when your LNS is one of the supported types:

HTTP ingress#

HTTP ingress accepts webhook-style payloads from upstream systems such as Actility ThingPark. The platform generates a unique endpoint URL and authentication token that you configure in your upstream system’s forwarding settings.

HTTP ingress receives post-deduplication data and cannot provide low-level RF analytics. Use this method only when a direct LNS integration is not available.

Connect via HTTP Ingress

API ingress#

API ingress supports custom integrations through a gRPC-based interface. Generate an API key in Configuration > API Ingress and use it with one of the provided collector agents or a custom client built against the Kudzu Analytics protobuf definitions.

Supported collectors:

After data flows#

Once data is being received through any ingestion method:

Navigate to Configuration > Monitoring KPIs and import the analysis algorithms you want to track.
Open the Metrics Dashboard to verify that computed metrics are appearing.

Onboard Your Network — the guided onboarding checklist that includes setting up your first integration.