Skip to main content

Blog post · November 20, 2026 · aviznetworks.com

Aviz Networks explains Custom App-ID for unknown traffic

Summary

Aviz Networks has added Custom App-ID to its Aviz Service Nodes, letting operators label private and proprietary applications that standard DPI often reports as unknown. Unlabeled traffic complicates SLA reporting, capacity planning and partner agreements for enterprise IT leaders.

Limits of built-in DPI

Built-in deep packet inspection identifies thousands of public applications, but its signature libraries are not designed for private or internally developed services. Traffic from these applications is often classified as unknown or generic. The blog states that this affects SLA verification, capacity planning, zero-rating agreements and dependence on vendor signature roadmaps, which can take weeks.

How Custom App-ID works

Custom App-ID runs on Aviz Service Nodes alongside built-in DPI. Operators define rules using hosting location, port, protocol and, where needed, the initial bytes of traffic. Each rule assigns an application name and group, and matching sessions are labeled in real time.

Labeled sessions are exported in the existing AppName and AppGroup fields in Kafka, so current dashboards and KPIs can use the new names without a schema change. Operators can choose which engine to enable first in the datapath, and custom rules can be placed ahead of built-in DPI through a setting. The same rules apply within GTP-U tunnels and to data center traffic over IPv4 and IPv6.

Rule configuration

Rules are written in a YAML file, with each rule combining only the conditions it requires. A session must meet all of a rule's conditions to match, and rules are evaluated top to bottom with the first match taking effect. The blog's example file defines four rules: an enterprise ERP platform identified by destination address, port and TCP; an IoT telemetry service identified by UDP port and the first three bytes of payload; a payments partner API matched in either direction by address, port, TCP and TLS handshake start; and a corporate voice gateway identified by IPv6 address over UDP.

Operational behavior

Rules reload while traffic continues to flow, without a restart or packet loss, and sessions already classified keep their labels. Enabling the feature is a one-time configuration setting, after which changes are made by editing the rule file and running a single command. According to the blog, a new rule can be added on the same day a service launches, without a signature request, software upgrade or maintenance window.

Use cases

The blog lists enterprise and private 5G reporting per customer, IoT and M2M fleet separation by protocol signature, and verification of zero-rated and sponsored data. It also cites partner and B2B API monitoring, flagging traffic to specific endpoints for security and compliance, and tracking growth of in-house services for capacity planning.

Custom App-ID extends traffic classification on Aviz Service Nodes to operator-defined applications, with rule changes applied live. For enterprise decision-makers, the feature addresses gaps in reporting on private and proprietary services. This Blog Summary is a fact-based summary of the vendor blog.

Our summary. The original keeps its own byline.

Read the original on aviznetworks.com

Companies in this article

Topics