Give each exporter a friendly name, its timezone (defaults to Asia/Kolkata), and, optionally, its circuit capacity in Mbps - set a capacity to enable utilization tracking for it. Leave capacity blank if you don't know it; it will never be guessed. Circuits without a capacity are listed first.

Shown in the sidebar below the product name/logo - e.g. your company or team name. Leave blank to show no organization name.

Dark is the default. Saved to this browser only - other browsers/devices keep their own choice.

Country > parent site > exporter. Group exporters/links that belong to the same physical or logical site (e.g. "JKT5" grouping Jakarta_RT01 + Jakarta_RT02), and set its country - this is what builds the Sites tree. Country is auto-suggested via IP geolocation from the first exporter assigned, when possible - it's always editable below and never authoritative, especially for private/lab IPs which won't geolocate at all.

Map a site's source subnets (e.g. 10.1.5.0/24) to the department that uses them, based on information the customer provides - this is entered by us and never auto-detected or guessed from traffic. Once at least one mapping exists for a site, its non-business traffic also breaks down by department, in addition to the existing per-app view.

Every NBAR-resolved application is grouped into one of 11 fixed categories (Streaming, Social Media, Gaming, SaaS/Productivity, Backup/Sync, VoIP/Conferencing, OS/Software Updates, Security, File Transfer, Web/General, Unknown), and each category has a default business/non-business/neutral classification. Any individual app can be overridden regardless of its category's default - e.g. Facebook defaults to non-business, but a marketing team's traffic can be marked business without changing every other social app. Anything NBAR reports that isn't yet categorized shows honestly as "Unclassified" here and on the dashboard - it is never silently counted as business.

Some applications (e.g. Apple's shared "apple-services" traffic) mix a small steady baseline with occasional large bulk transfers that are really a different use case - a rule here splits any flow averaging above a byte threshold off into its own named sub-application, which gets its own classification below instead of inheriting the parent app's.

Amber/red banding for non-business traffic share, used anywhere a site or circuit's non-business % is shown with a color flag. Circuit utilization and saturation cutoffs (80%/95%/90%) are fixed design constants, not configurable here.