Jaze ISP Manager
Every session, recorded and searchable later.
Flow records are collected from your network devices, stored with their NAT translations, and made searchable through a query interface, which is what turns a compliance request into a search rather than a project.
ISP Manager / Logging
IPFIX records, compression and lookup
- Flows / second
- 0
- Raw logs today
- 0.0 GB
- Saved to disk
- 0.0 GB
- Lookup time
- 0 ms
IPFIX
Collecting- 100.0.4.45:34348.8.8.8:53
- 100.0.7.12:51433151.101.1.69:443
- 100.0.5.17:4487113.107.42.14:443
- 100.0.2.31:60211157.240.16.35:443
- 100.0.9.88:3811923.62.14.90:443
- 100.0.4.45:3441104.18.32.7:443
- 100.0.7.12:51420142.250.183.14:443
- 100.0.4.45:34348.8.8.8:53
Compress
87% savedRaw24.6 GB
Saved to disk3.1 GB
Query
ISP Manager / Logging
IPFIX records, compression and lookup
- Flows / second
- 0
- Raw logs today
- 0.0 GB
- Saved to disk
- 0.0 GB
- Lookup time
- 0 ms
IPFIX
Collecting- 100.0.4.45:34348.8.8.8:53
- 100.0.7.12:51433151.101.1.69:443
- 100.0.5.17:4487113.107.42.14:443
- 100.0.2.31:60211157.240.16.35:443
- 100.0.9.88:3811923.62.14.90:443
- 100.0.4.45:3441104.18.32.7:443
- 100.0.7.12:51420142.250.183.14:443
- 100.0.4.45:34348.8.8.8:53
Compress
87% savedRaw24.6 GB
Saved to disk3.1 GB
Query
In the dashboard
Logging & Lookup panel by panel.
Every flow is logged with its time, source and destination, compressed to a fraction of its size on disk, and traced back to the subscriber behind an IP in milliseconds.
IPFIX
Every flow, logged.
- Timestamp, source and destination on every record
- Collected live from the devices already exporting flows
Compress
A fraction of the size on disk.
- Raw logs compressed as they are written
- Raw size and size on disk, side by side
- Less storage for the same retention
Query
From an IP back to a subscriber.
- Search by timestamp and IP address
- Resolves to the username and email behind it
- Answered in milliseconds
Collection path
From exported flow to searchable record.
Jaze collects from the devices already exporting flow data, rather than asking you to put a new probe in the traffic path.
Subscriber traffic
Sessions traverse the access network as normal.
BNG / NetFlow device
The router exports IPFIX or NetFlow v9 records.
Jaze collector
Records parsed and stored, with NAT translations kept.
Searchable logs
Queried through a simple interface and downloaded.
Capabilities
Collection, translation and scale.
Collection
Gain network insights and ensure compliance
- IPFIX and NetFlow v9 log collection
- NetFlow device integration for log parsing and storage
- Scalable, storage-efficient IPDR capture
- Timestamp, source and destination IP and port logging
- Notification when log collection stops, with suggested remedy
NAT and session records
The translation kept alongside the flow
- NAT translation logging
- Source NAT logs redirected over FTP in compressed form
- Session log records with IP address and subscriber details
- Searchable and downloadable logs through a simple query interface
Scale
Sized for a subscriber base, not a lab
- Horizontally scalable to hundreds of thousands of subscribers
- Runs on commodity hardware
- Storage-efficient record format
Compliance
The logs a regulator asks for.
Compliance reporting is part of the platform rather than a project you run once a year.
Regulatory logging
Audit logs captured as the network runs
- TRAI and DOT session log records
- Lawful intercept log capture
- CALEA compliance logs
Monitoring
Traffic visibility alongside the record
- SNMP integration for MRTG graphing
- Per-user and per-interface traffic statistics
Talk through your reporting obligations.
What you need to retain, for how long, and how it is queried when someone asks.