Explorer
Explorer is Monocle's multi-dimensional traffic investigation view. Use it to break your traffic down by dimension (country, service, AI operator, traffic type, IP and more), narrow it to the slice you care about, and see which sessions your policy allowed or blocked.
Open Explorer from your application in the Monocle dashboard, or select Explore on the Policy page to open its Policy Decision tab.
Explorer requires the Team plan or above. On other plans, it shows a preview with example data and an Upgrade plan button.
Choose a time range
Pick a preset (Last 7 Days, Last 30 Days, Last 60 Days or Last 90 Days) or choose a custom range on the calendar. The calendar goes back 120 days, and a range can be up to 90 days long. If you pick a longer span, Explorer shows the last 30 days instead. Days run midnight to midnight UTC, and every tab, chart and table uses the range you choose.
Dimensions
Each tab breaks the same traffic down a different way. The number on a tab shows how many distinct values it has in the current range and scope.
| Tab | What it breaks traffic down by |
|---|---|
| AI Operator | The AI company or service behind the traffic, such as OPENAI. See Investigating AI traffic. |
| Anonymous | Anonymous vs not anonymous sessions |
| Event | Traffic events Monocle detected, such as a spike from one service. Only shown on accounts with Events enabled. |
| Geo Intelligence | Visitor country |
| Policy Decision | Policy decisions: allowed vs blocked |
| Service | The VPN, proxy or other service identified, such as GOOGLE_ONE_VPN |
| Time of Day Behavior | When traffic arrives, by hour of day (UTC) |
| Traffic Type | VPN, Proxied, RDP, DCH, AI Agentic, AI Crawling or Uncategorized |
| User IP | Individual visitor IP addresses |
Expand a row
On the Event, Service and User IP tabs, expand a row for more detail:
- Event: the event's volume and duration, how much of it was anonymous or blocked, and its top traffic types, countries and IPs
- Service: active IPs, distinct countries, top country and category, plus how the service's IP footprint is changing (net IP growth, average daily churn and TTL)
- User IP: classification, service, infrastructure, service exit location and ASN, plus any risk indicators
On the Service and User IP tabs, select Full profile to open the service's or IP's full profile. See Expanding IP and Service Rows in the Explorer in the Knowledgebase.
Event status
Each event your application raised has a status, so your team can see which events still need a look:
| Status | Meaning |
|---|---|
| New | Not looked at yet. Every newly detected event starts here. |
| Investigating | Someone is looking into it. |
| Reviewed | Looked at, and handled. |
| Dismissed | Looked at, and needs no action. |
To change an event's status, open the menu at the end of its row, choose Status and pick another. Everyone in your organization sees the change, and Monocle records who made it and when.
Investigating AI traffic
The AI Operator tab shows which AI services reach your application and how much of your traffic they account for. You don't need an AI policy to see it: Monocle identifies AI traffic as part of every assessment.
| Column | What it shows |
|---|---|
| Operator | The AI operator, such as OPENAI |
| Series | Plots the operator on the chart, in its own color |
| Type | Agentic if AI agent activity was observed in the operator's traffic in the range, Crawler if AI crawler activity was, or both. A dash means neither was observed. |
| Volume | Sessions from this operator in the range |
| Share | This operator's share of all traffic in the current view, not just AI traffic |
| Change | Change against the previous period of the same length. A dash means the operator had no traffic in that period. |
Every operator is listed on one page. Sort by any column except Series, for example Volume to find your biggest AI sources or Change to find the fastest-growing. Operators with no Change value sort last. Traffic with no AI operator isn't listed, so non-AI traffic is never attributed to one. AI Operator rows don't expand.
To follow one operator over time, select its row and choose Show on chart. To see what else it did, such as its countries or IPs, choose Include in filter and switch tabs.
Investigation Scope
Investigation Scope narrows everything on the page to the traffic you want to look at, including the Policy Decision tab. Select Add filter, then choose a field, an operator and a value. Each filter shows as a chip you can change or remove, and Clear all removes them all. Filters on different fields must all match. On the same field, is values match any of them, and is not values exclude all of them. The count on each tab updates to match.
| Field | Operators | Example |
|---|---|---|
| AI operator | is, is not | AI operator is OPENAI |
| Country | is, is not, contains | Country is United States of America |
| Date | is | One day in the selected range |
| Policy decision | is, is not | Policy decision is Blocked |
| Service | is, is not, contains | Service is not ICLOUD_RELAY_PROXY |
| Source IP | is, is not, contains | Source IP contains 203.0.113. |
| Time | is, is not | Hour 14 and minute 30 (UTC), or either one alone |
| Traffic type | is, is not | Traffic type is not Anonymous |
Time is in UTC, and its hour and minute filter separately. Time is 14:30 keeps the single minute 14:30. Time is not 14:30 excludes the whole 14:00 hour and also minute 30 of every other hour. Explorer can't exclude a single minute of one hour.
AI operator matches the name whatever its case, so openai and OPENAI are the same. AI operator is not keeps your non-AI traffic, the same way excluding a service does. To look only at AI traffic, use Traffic type is AI Agentic or AI Crawling. The Event tab isn't narrowed by AI operator yet, and says so when that filter is applied.
Policy decision narrows the summary, the chart and every assessment tab to the traffic your policy Allowed or Blocked, or excludes it. Each session counts by its first decision. Traffic your policy made no decision on matches neither value, so Policy decision is not Blocked keeps it. Events carry no policy decision, so the Event tab leaves this filter out and says so.
Select, include and exclude
Select rows in a tab's table to act on them. The toolbar shows how many you've selected (2 selected, for example) and offers:
- Include in filter: add the selected values to Investigation Scope, so the page shows only that traffic
- Exclude from filter: add them as exclusions, so the page shows everything else
- Show on chart: plot up to five of the selected values on the chart, to compare them over time
Select Clear all to start over.
Add a policy rule (Pro)
A service or country's menu, and its row's menu, can also block it in your app's policy without leaving Explorer: choose Block service or Block country. Monocle asks you to confirm before it saves. A value the policy already blocks offers Unblock service or Unblock country instead. Blocking a service you exempted takes it off your exempt services.
These are the same lists as the Service and Geo sections of Configure Policy, which you edit under the Custom strategy. Under Allow all, Normal or Aggressive, a change switches the policy to Custom with the strategy's current settings, so it goes on doing what it did plus your change, and Monocle says so before saving. Exemptions are made on Configure Policy. For an app with no policy yet, a block enables one: the Custom strategy with every traffic type allowed, so your block is its only rule. Without the Pro plan, the items open an upgrade instead. The country allowlist is only on Configure Policy: it allows only the countries on it, so adding the first country there would block every other. See Policies.
If the rule saves but your edge integration doesn't take the update, the rule still applies to your policy endpoint, and the toast offers Retry to publish it to the edge.
Investigating policy activity
The Policy Decision tab shows how many sessions your policy allowed and blocked over time, for the range and scope you've chosen. Its rows can be shown on the chart, but not added to a filter from the table.
To see what your policy blocked, for example its countries, services or IPs, add Policy decision is Blocked to Investigation Scope and switch tabs. Use it to compare traffic before and after a policy change. See Policies.