Back to workspace
AXORIK Help Center
Learn by outcome

What do you want to accomplish?

Find a workflow, understand live evidence or learn the safest next step. Search by the job you need to complete, not only by a feature name.

Understand 6 minute read Lesson 6 of 19

Use Applications

Explain traffic by application, client and network instead of relying on one bandwidth total.

Network ownerIT teamMSP
Complete this lesson, then continue through the system0 of 19 completed

Outcome

Trace unusual consumption to the correct source and review targeted policy options.

Where to find it

Main navigation > Applications

Start here

Complete guide to Use Applications

When you do this

Use Applications when bandwidth is unexpectedly high, users report slowness or you need to understand which services consume network capacity.

What this means

Applications classifies observed traffic and attributes it to clients and network segments. It helps explain usage patterns, but classification alone does not prove that a user or application is malicious.

Before you start

  • Choose the correct site and a time range that covers the reported issue.
  • Know whether you are investigating a live spike, a workday pattern or a longer trend.
  • Identify business-critical applications that must not be interrupted.

Do this step by step

  1. 1Set the Time range to the period in question.
  2. 2Open Application overview and compare the leading applications and categories.
  3. 3Select an application to view its trend instead of relying only on total volume.
  4. 4Use Client attribution to identify the devices and network segments responsible.
  5. 5If a supported Application policy is available, review its scope, schedule and exceptions before applying it.

How to know it worked

You can name the application, clients, network segment and time window responsible for the traffic and explain whether any policy was applied.

If it does not work

  • If no applications appear, confirm traffic analysis is supported, enabled and current for the connected console.
  • If a label seems wrong, use the client and destination context before drawing a conclusion.
  • If a policy does not reduce traffic, confirm the matched application, target clients and schedule.

Important

Do not block or limit an application until you confirm legitimate business use and required exceptions.

What you will see on this page

These are the exact AXORIK sections to look for. Read them in the order shown unless the complete guide directs you to a specific finding.

1

Application overview

Ranks detected applications and categories by observed traffic.

2

Time range

Changes the question from a live issue to a workday pattern or longer trend.

3

Client attribution

Shows which clients and network segments generated the traffic.

4

Application policy

Prepares supported control by scope, schedule and exceptions when available.

Recommended workflow

Follow these steps in order. If a step is blocked, resolve it before moving to the next one.

1

Choose the time range

Select a window that matches the issue you are investigating.

2

Open the application

Compare its share and trend with the rest of the site traffic.

3

Trace clients and networks

Identify who generated the traffic and from which segment.

4

Review policy impact

Confirm business use, scope, schedule and exceptions before control.

Safety and interpretation

  • Classification is evidence, not proof of malicious intent.
  • A policy may affect legitimate work.
  • Confirm exceptions before blocking or limiting traffic.

AXORIK Essentials lesson 6 of 19

Can you now explain when and why to use this feature?

Mark it complete only when you know where to find it, what its main sections mean and what the safe next step is.