Announcing InMon Traffic Sentinel 8.7

May 2022: InMon Traffic Sentinel 8.7 is now available for download. This is a free upgrade for customers who have purchased annual maintenance.

Previous release: 8.6

New features include:

  1. Sankey chart flow visualization
  2. Collect switches into zones using patterns
  3. Upgrade to Apache Tomcat 8
  4. Performance and Scalability Improvements

Sankey chart flow vizualization

Traffic Sentinel ships with an example "sankey.js" dashboard script under File>REST. Make a Copy and edit to customize. The list of layers defines the columns in the Sankey chart. Functions such as "name(asn(ipsource))" can be used. When set to refresh the chart will update every minute using a morphing animation. The "description:" comment at the top can be used to change the banner.

// description: sankeyflows
// author: InMon
// date: 5/15/2022
// version: 1.0
// authLevel:operator
// clientJS:sankey-1.0.js
// ttl:60
// view:traffic
// resultFormat: json


new Sankey({
    height: 600,
    layers: ['sourceaddress','protocol','destinationaddress'],
    value: "bps",
    interval: "last5minutes",
    colors: '#000000,#db3a34,#f0c808,#56926e,#6c4f77,#4281a4',
    refresh: true,
    where: "",
    debug: false

Collect switches into zones using patterns

If the IP address allocation for your switches does not align with the hierarchy you want for your zones and groups you can now use patterns to capture switches into groups instead of CIDRs and agent-ranges. Patterns can be applied to identifiers such as the hostname reported by sFlow, the DNS name learned by reverse-lookup, and the sysName, sysDescr, sysLocation and sysObjectID learned from SNMP. Your overall CIDRs should still be added to the config (e.g. in a group "All"), but these patterns can then capture switches and servers into more specific zones and groups for convenient navigation.

Upgrade to Apache Tomcat 8

The web front-end now uses Apache Tomcat 8.5.78.

Performance and Scalability Improvements

For the case where the arrival rate of sFlow/NetFlow packets is very high, a new option was added to use multiple reader threads when servicing the socket. See the tutorial on Sentinel Performance Tuning.

Previous Release: Announcing Traffic Sentinel 8.6