Skip to main content

Counter Groups Reference

A counter group is Trisul's basic unit of measurement. It keeps one time series per key, for example one per IP address, port, country or router interface. Each key holds several meters, such as bytes, packets or connections.

This page explains the concepts shared by every group and lists every group with its layer, what it measures and what its keys look like. Each group's own page gives exact key formats, special keys and the full meter table, all checked against the source code.

Concepts​

TermMeaning
Counter groupA named, GUID-identified collection of keys. Example: Hosts {4CD742B1-C1CA-4708-BE78-0FCA2EB01A86}.
KeyThe thing being counted, stored in a fixed machine format such as C0.A8.01.02. The UI shows a readable label (192.168.1.2, or a resolved name) when one is known.
MeterOne numeric series inside a key, identified by a meter ID (0, 1, 2 …). Meter 0 is usually the total bytes.
BucketThe time resolution of stored values. 60 s for most groups.
TopperTop-N (and bottom-N) key lists per meter, computed every topper interval (300 s by default). Top/Bottom in a meter table is how many keys are kept.
Native or LuaGroups are built in C++ inside the probe or its plugins (Geo, Badfellas), or written in Lua by the probe or a Trisul App. They behave the same once registered.

Layers used in this reference​

LayerKeys come from
L2 LinkEthernet frames: MAC addresses, VLAN IDs, MPLS labels, EtherTypes
L3 NetworkIP addresses, IP protocols, ICMP, geo lookups on IP addresses
L4 TransportTCP or UDP ports and TCP behavior
L7 ApplicationApplication payload: HTTP, TLS, DNS, SSH, HSRP
Flow RecordFields of NetFlow, IPFIX or sFlow records that packets do not carry: exporter, ifIndex, AS, next hop, VRF, vendor App-ID
AlertsIDS, threat-intel and MITRE alerts
External DataSNMP polling, ping, firewall syslog
DerivedAnother counter group, through a filter, statval, ruleset or crosskey
SystemThe probe itself

Input on each page says which feed fills the group: Packets (packet capture), Flows (NetFlow, IPFIX or sFlow), Alerts, SNMP, Syslog or Internal.

Key formats​

Keys are stored as compact strings. These formats recur across groups:

WhatKey formatExample keyReadable
IPv4 addressDotted uppercase hex, 2 digits per octetC0.A8.01.02192.168.1.2
IPv6 address32 uppercase hex digits, no separators20010DB80000000000000000000000012001:db8::1
MAC addressColon-separated hex00:00:0C:12:34:56Cisco System:12:34:56 (vendor from the OUI database)
Port (Apps)p- + 4 hex digitsp-01BB443, label https
IP protocol2 hex digits06TCP
EtherType4 hex digits86DDIPv6
VLAN ID4 hex digits0064VLAN 100
ICMP type and code4 hex digits, type then code0303Port Unreachable
Router interfaceExporter IPv4 in hex + _ + ifIndex as 8 hex digitsC0.A8.01.01_00000003192.168.1.1_3
AS numberDecimal string, no AS prefix15169GOOGLE
CountryISO 3166 2-letter codeINIndia
PrefixCIDR string203.0.113.0/24as is
Names (HTTP host, TLS org, user, App-ID…)The text as seen on the wire or in the recordwww.example.comas is
For tools and AI agents

Always query with the stored key format, not the readable label. To query host 10.1.1.5 in Hosts, use the key 0A.01.01.05.

Special keys​

SYS:GROUP_TOTALS​

Every counter group has the key SYS:GROUP_TOTALS. The stream engine (stengine/XCounterGroup.cpp) applies every update made to any key in the group to this key as well, including updates for keys that a crosskey group refused to track. Use it for "all of this group" questions, and to work out the Others share in top-N charts.

How a meter totals depends on its type:

Meter typeValue in SYS:GROUP_TOTALS
VT_RATE_COUNTER, VT_COUNTER, VT_RUNNING_COUNTERSum over all keys
VT_GAUGE, VT_DELTA_RATE_COUNTERLast value written by any key, not a sum
VT_MAX / VT_MINMaximum or minimum across all keys
VT_AVERAGEAverage of every sample written to any key
Double counting

The totals are a sum of updates, not of traffic. When one packet or flow updates two keys (source and destination host, input and output interface), the totals are about 2× the link traffic. Each group page says whether this applies. For network-wide traffic use Aggregates, key TOTALBW.

Other special keys​

Some groups use reserved keys for unknown values or for traffic that does not fit the normal key. Examples: UNTG (untagged frames in VLANStats), XY (country not found), XX (ASN or prefix not found), 0 (flow record without AS), 00.00.00.00 (missing next hop), FF:FF:FF:FF:FF:FF (broadcast MAC), TOTALBW and DIR_* in Aggregates. Each group's page lists its special keys under Keys → Special keys.

Meter types​

TypeWhat is stored per bucketTypical units
VT_RATE_COUNTERSum of values in the bucket ÷ bucket secondsBps, pps
VT_COUNTERSum of values in the buckethits, conns, alerts
VT_RUNNING_COUNTERRunning value carried across buckets (increments and decrements)active flows
VT_GAUGELast value written in the bucketqueue depth, ms
VT_DELTA_RATE_COUNTERChange in a cumulative value (such as an SNMP octet counter) ÷ bucket secondsBps
VT_AVERAGEMean of the values written in the bucketms
VT_MAX / VT_MINLargest or smallest value written

Every group also has two Unused Cardinality counter meters at the end of its table. The plugin framework adds them. They are filled only when you configure cardinality counting.

Derived counter groups​

You can define new groups that take their data from an existing parent group. They inherit the parent's meter list and key format.

KindHow keys get inBuilt-in examples
StatvalA parent update is copied when a chosen meter is above a valueInternal Hosts, External Hosts
FilterA parent update is copied when another group's key (such as a port) appears in the same packet or flowWeb Hosts, Email Hosts, SSH Hosts, Unusual Traffic Hosts, and the Interface Tracker groups (Hosts, Apps or NetworkLayerStats filtered by a FlowIntfs key)
RulesetMatching updates are renamed to a target keyUnleash Apps
KeysetOnly keys in listed ranges are kept or groupednone ship by default
CrosskeyKey is the combination of two or three groups' keys, e.g. AS × router interfaceFlow-ASN × FlowIntfs, BGP-Peer AS × FlowGens

Catalog: built-in counter groups​

These 63 groups ship with Trisul Probe and its Geo and Badfellas plugins. Groups marked ² are off by default or exist only when configured.

Ethernet frames: MAC addresses, VLANs, MPLS labels, EtherTypes.

GroupMeasuresKeyInputGUID
AggregatesNetwork totals, L2/L3 broadcast/multicast/unicast, home-net directionFixed names (TOTALBW, DIR_*, ipfrag, SG GUID)Packets, Flows{393B5EBC-AB41-4387-8F31-8077DB917336}
Dir MacBytes per directed source-to-destination MAC pairMAC pair "src ->dst"Packets, Flows{79F60A94-44BD-4C55-891A-77823D59161B}
LinkLayerStatsBytes and packets per EtherTypeEtherType (4 hex)Packets, Flows{9F5AD3A9-C74D-46D8-A8A8-DCDD773730BA}
MacBytes transmitted/received per Ethernet MACMAC addressPackets, Flows{4B09BD22-3B99-40FC-8215-94A430EA0A35}
MPLSStatsBytes per top-of-stack MPLS labelMPLS label (5 hex)Packets{6C312435-80C1-401F-AEDD-090FF4F46212}
VLANStatsBytes per 802.1Q VLAN, untagged as UNTGVLAN ID (4 hex)Packets, Flows{0EC72E9E-3AD2-43FD-8173-74693EEA08D0}

L3 Network​

IP addresses, IP protocols, ICMP, and geo or organization lookups on IP addresses.

GroupMeasuresKeyInputGUID
ASNumberHome↔external traffic by GeoLite2 ASN of external IPAS number (decimal string)Packets, Flows{03E016FC-46AA-4340-90FC-0E278B93C677}
City ²Home↔external traffic by GeoLite2 city (off by default)GeoNames city IDPackets, Flows{6D201FA3-6F8B-4F83-73F7-CB0B8A66EA2E}
CountryHome↔external traffic by GeoLite2 country of external IPISO country code (2 letters)Packets, Flows{00990011-44BD-4C55-891A-77823D59161B}
HostsPer-IPv4 traffic, connections, TCP flags, alerts, flow recordsIPv4 addressPackets, Flows{4CD742B1-C1CA-4708-BE78-0FCA2EB01A86}
HostsIPv6Per-IPv6 traffic, connections and flow recordsIPv6 addressPackets, Flows{9807E97A-6CD2-442F-BB18-8C104C8EB204}
ICMP TypesIPv4 ICMP bytes and packets per type/codeICMP type+code (4 hex)Packets{FA6466E2-EA6A-4E75-8F39-ADE7708C6F46}
NetworkLayerStatsBytes, packets, active/total flows per IP protocolIP protocol (2 hex)Packets, Flows{E89BCD56-30AD-40F5-B1C8-8B7683F440BD}
OrganizationDeprecated. Remote-office traffic and whitelist violations per organizationOrg code (text)Packets{3A597F63-29C0-44AF-A7EF-641897D68693}
Prefix ²Home↔external traffic by GeoLite2 ASN-block prefix (off by default)IPv4 CIDR (dotted decimal)Packets, Flows{2838D2E8-EABC-4050-90C4-8AE2589AAB25}
Remote OfficeDeprecated. Remote-office traffic and whitelist violations per branch<org>_<branch> (text)Packets{664D68BF-5544-43CE-A895-50F2E179EA5A}

L4 Transport​

Ports and TCP behavior.

GroupMeasuresKeyInputGUID
AppsBytes, home-net direction, connections per server portPort key p-XXXX or protocol namePackets, Flows{C51B48D4-7876-479E-B0D9-BD9EFF03CE2E}

L7 Application​

Values parsed from application payloads: HTTP headers, TLS handshakes, DNS, SSH, HSRP.

GroupMeasuresKeyInputGUID
HTTP Content TypesContent-Type headers (hits) and following flow bytesMIME type stringPackets{C0C9757F-2005-4CC5-BB96-D72F607E6188}
HTTP HostsFlow bytes after Host header seen, keyed by raw Host valueHTTP Host header stringPackets{D2AAD7C6-E129-4366-A2AD-A8CB9AA4C2F4}
HTTP MethodsHTTP request lines per method (GET/POST/PUT/DELETE/TRACE/OPTIONS/HEAD)HTTP method stringPackets{2A6957EB-4992-46CD-8E49-BE32318669D3}
HTTP Status CodesHTTP responses per status codeHTTP status code stringPackets{25E80A84-C175-4C01-977C-1411F5D10B56}
Long Fat Tail HostsHTTP flows to ranked domains below top FatTailRankDomain suffixPackets{27870892-5B20-4555-8BA2-2742F3DD0F04}
Long Thin Tail HostsHTTP flows to hosts absent from popularity rankingHTTP Host headerPackets{BF2C028A-CDDE-4074-8AF5-A007582D820E}
TLS CAsCA certs in server chain: Root CA / Inter CA hitsCA organization namePackets{15856A98-7F87-46D7-84D2-18DD549F8A6F}
TLS CiphersServerHello selected cipher suite: hits and flow bytesCipher suite ID, 4 hex digitsPackets{5B64A573-623F-4F5B-8865-78C62BF466A7}
TLS OrgsServer cert O= field: hits and flow bytesCertificate organization namePackets{432D7552-0363-4640-9CC5-23E4CA8410EA}

Flow Record​

Fields taken straight from NetFlow, IPFIX or sFlow records: exporters, interfaces, AS numbers, next hops, prefixes, TOS, VRF, vendor App/User IDs.

GroupMeasuresKeyInputGUID
App-IDTraffic per Palo Alto App-IDApp-ID stringFlows{9021F5D3-FEFB-401B-99EC-EF2ACD088578}
BGP-ASPATH ²NetFlow bytes by RIB AS path of each endpointAS path (ASNs joined by /)Flows{47F48ED1-C3E1-4CEE-E3FA-E768558BC07E}
BGP-Origin AS ²NetFlow bytes by origin AS (last AS in RIB path)AS number (decimal string)Flows{3950AB76-3C3A-40EE-5C94-80A87EE28D53}
BGP-Peer AS ²NetFlow bytes by peer AS (first AS in RIB path)AS number (decimal string)Flows{A643654F-2BA3-4832-4FF1-43EBDDE6E655}
BGP-Prefix External ²NetFlow bytes by matched BGP RIB prefixIPv4 CIDR (dotted decimal)Flows{C26520C4-DB9D-49EC-5D8B-35AD39951E36}
Flow-APPID-NBARTraffic per NBAR/RFC 6759 application IDengine:selectorFlows{322AFE57-BA50-47B1-BE5C-EBC05BCC186B}
Flow-ASNUpstream/downstream traffic per SRC_AS/DST_ASAS number (decimal)Flows{120A3124-E2BB-47BD-6C64-71BBB861C428}
Flow-BGP-NextHopTraffic per BGP next hopIPv4 address (hex)Flows{FC61EC07-BED0-4734-C64C-F5932FD8B943}
Flow-IP-NextHopTraffic per IP next hopIPv4 address (hex)Flows{79693CA3-ED3C-43B3-E12A-A3F64B125E4F}
Flow-Link-ASN ²Traffic per AS per router interfaceAS\router_ifIndexFlows{1D86CAB7-B4C4-433E-BCB9-C779A4244D70}
Flow-PrefixTraffic per source/destination prefix from router masksIPv4 CIDR stringFlows{2BE2A3B6-613D-4216-0737-3684E824EA33}
Flow-Prefix-v6Traffic per IPv6 prefix from router masksIPv6 CIDR stringFlows{467AE21F-F2B7-4509-EA69-514CF2352D36}
Flow-TOSBytes and flows per DSCP code pointDSCP (2 hex digits)Flows{965DDD07-F715-48D5-636B-A15106C9B502}
Flow-VRFTraffic per ingress VRF IDVRF:<id>Flows{7FAB8F84-C580-424B-2BA4-B2546D2DB15A}
FlowGensFlow traffic, record counts and export volume per exporterExporter IPv4 (hex)Flows{2314BB8E-2BCC-4B86-8AA2-677E5554C0FE}
FlowIntfsReceive/transmit/flows and utilization per router interfaceExporter IPv4 + ifIndex (hex)Flows{C0B04CA7-95FA-44EF-8475-3835F3314761}
User-IDTraffic per firewall-reported userUser name stringFlows{86A8880D-F4B2-4E49-A4FA-718880CAA976}

Alerts​

Counts of IDS, threat-intel and MITRE-tagged alerts.

GroupMeasuresKeyInputGUID
Alert ClassesIDS alerts per classificationClassification string (cid-N)Alerts{20BC4345-37F0-44D0-ABFF-3BED97363CB1}
Alert PrioritiesIDS alerts per prioritysn- + priority numberAlerts{9EFAFDD0-6CBB-4C04-8B13-2C8E0A9D3F85}
Alert SignaturesIDS alerts per signature IDSignature ID string (sid-N)Alerts{A0FA9464-B496-4A20-A9AB-4D2D09AFF902}
BlacklistBadfellas indicator matches counted per feed categoryIntel source/category stringPackets, Flows{6255BD85-2DCB-49E7-AF1F-1267AAF4DCA1}
MITRE SubtechniqueAlerts tagged with sub-technique ID (Txxxx.yyy)MITRE ATT&CK sub-technique IDAlerts{A2B72E5D-9E80-4796-23A9-618ABCEE1D57}
MITRE TacticAlerts tagged with tactic ID (TA00xx)MITRE ATT&CK tactic IDAlerts{70703134-26E7-4A41-7A29-46DFC85C3778}
MITRE TechniqueAlerts tagged with technique ID (Txxxx)MITRE ATT&CK technique IDAlerts{DC0296AA-61F2-413D-C8F3-97538F9C5418}

Derived​

Built from another group: statval, filter, ruleset or crosskey groups, plus groups re-keyed from another group's toppers.

GroupMeasuresKeyInputGUID
Base DomainsExternal host bytes mapped to DNS name queriedDNS question name or rule namePackets{74FE9532-EDEB-421E-BD92-B5C62E7F2346}
Email Hosts ²Hosts with traffic on SMTP/POP/IMAP portsIPv4 addressPackets, Flows{22D4082E-B8BA-40D0-A287-1F524DF8DA7B}
External HostsHosts keys outside the home networkIPv4 addressPackets, Flows{00AA77BB-0063-11A5-8380-FEBDBABBDBEA}
External Hosts v6 ²HostsIPv6 keys outside the home network (only if configured)IPv6 addressPackets, Flows{9DC000A5-E122-4BDC-BC56-D3594A00BB53}
Internal HostsHosts keys inside the home networkIPv4 addressPackets, Flows{889900CC-0063-11A5-8380-FEBDBABBDBEA}
Internal Hosts v6 ²HostsIPv6 keys inside the home network (only if configured)IPv6 addressPackets, Flows{0BDE3B47-B465-43DD-9275-45829D9A9748}
SSH Hosts ²Hosts with traffic on port 22IPv4 addressPackets, Flows{439002E4-3758-4E88-9438-8034FE1616AF}
Unleash Apps ²Demo ruleset: rule-matched Apps traffic under a target keyRule target name or Apps keyPackets, Flows{FF889910-9293-AAA5-0028-883991889884}
Unusual Traffic Hosts ²Hosts with traffic outside web/mail/FTP/SSH portsIPv4 addressPackets, Flows{AE3A1449-5663-41A5-A028-FDE61DBB7EFA}
Web Hosts ²Hosts with traffic on ports 80/443IPv4 addressPackets, Flows{EEF95297-0C8D-4673-AD6B-F4BD2345FD69}

System​

The probe monitoring itself.

GroupMeasuresKeyInputGUID
Meta Counter GroupPer-group key counts, new keys, flush timeCounter group GUIDInternal{4D88CC23-2883-4DEA-A313-A23B60FE8BDA}
Meta Session GroupFlow cache size, new/expired/terminated/flushed flowsSession group GUIDInternal{594606BD-EEB2-4E0B-BAC4-84B7057088C8}
Perf-StatsProbe flush time, CPU, memory, capture drops, PCAP write rateComponent (engine-N, inputfilter-N)Internal{0D39F2A7-2627-49D5-9DCF-707E6F1C0571}

Catalog: counter groups added by Trisul Apps​

These 40 groups appear only after you install the named app from Trisul Apps. Their pages note bugs found in the app code that affect the numbers.

GroupAppLayerMeasuresKeyGUID
App Category ²fortigate-connectorExternal DataFlow bytes per FortiGate app categoryFortiGate appcat name{2DE5A613-BC31-4C73-1EAA-B527FDD40E7D}
DHCP Hostnamesfortigate-connectorDerivedInternal Hosts traffic intended to be keyed by DHCP hostnameIPv4 address{A8D34B1F-E0E5-458D-012A-0A31B0746D41}
External Syslog IPfortigate-connectorExternal DataExternal IPs seen in firewall syslog (not populated)IPv4 address{459BACD7-8F16-428F-2882-9DED4801C46D}
HSRP HitshsrpL7 ApplicationLast HSRP Hello state (Active/Standby) per VIP/MACvirtual IPv4|MAC{0A79F27A-4741-40E8-DAF1-32F8ADB2653E}
HSRP RoutershsrpL7 ApplicationRouters sending HSRP HellosIPv4 address (dotted decimal){47FB78D7-76F6-4AF0-D45A-7D9BA6E83762}
Proxy Externalhttp-proxyL7 ApplicationProxied HTTP/CONNECT flow bytes by real destinationShortened hostname{55F98CC1-646E-4DE6-AD79-6B896211F178}
Exchange MAC ²IGMP_multicastL2 LinkBytes of IPv4 UDP packets per src/dst IP and dst MACIPv4\IPv4\dest MAC{095E0C56-D17F-4634-A0B8-E000B4E85140}
Exchange XFlowIGMP_multicastL4 TransportTCP client/server/port bytes and multicast UDP bytesIPv4\IPv4\port[\mcast IP]{942AB99F-7A65-4B2E-6F6C-A3050F0F7B35}
IP X MulticastIGMP_multicastDerivedMember×group crosskey: IGMP heartbeats and group trafficmember IPv4 + multicast IPv4{074E78B6-E032-4B22-B085-12A2E72E1BB7}
Multicast HostsIGMP_multicastL3 NetworkHosts traffic of multicast groups that have IGMPv2 membersIPv4 multicast address{2792D434-496E-40C9-5E2D-73B60623A631}
Multicast MembersIGMP_multicastL3 NetworkGroup traffic charged to each IGMPv2 member hostIPv4 address (member){51177E0A-7535-46B7-1477-9F0E0E0F9808}
IP-MAC-PAIRip-mac-mapperL2 LinkBytes per IP+MAC pairIPv4_MAC{4D6F1A1C-B8B5-4635-AFF8-20BE2A306020}
IP2Loc ASNip2locationL3 NetworkFlow bytes/flows by IP2Location ASN of external IPAS number{EF44F11F-B90B-4B24-A9F5-86482C51D125}
IP2Loc Cityip2locationL3 NetworkFlow bytes/flows by IP2Location city of external IPCC_City string{E85FEB77-942C-411D-DF12-5DFCFCF2B932}
IP2Loc Countryip2locationL3 NetworkFlow bytes/flows by IP2Location country of external IPCountry code{F962527D-985D-42FD-91D5-DA39F4D2A222}
IP2Loc Proxyip2locationL3 NetworkFlow bytes/flows to known proxy/VPN/TOR IPs by typeIP2Proxy type code{2DCA13EB-0EB3-46F6-CAA2-9989EA904051}
IP2Loc Stateip2locationL3 NetworkFlow bytes/flows by IP2Location region of external IPCC_Region string{5C28445E-19E3-499E-E14D-E4CC7128B62B}
OTT AppsottDerivedExternal Hosts traffic mapped to OTT app via Passive DNSApp name{0D5FFF94-BDA1-4BDB-A13D-A5AED7D6A96C}
OTT XKeyottDerivedDefined but not updated by current code(none){113091EA-CF82-46E0-DE38-9A8C42DD0279}
PING LatencypingmonExternal DataICMP ping latency per targetIP address (dotted decimal){4DF11F00-B726-4260-5F83-0D9891197B45}
Protocol Treeprotocol-treeL3 NetworkBytes and frames per EtherType/IP-proto/port pathethertype/proto/port path{2CF4DCFF-77E5-45E9-AA03-8D827CE0813C}
Prune-PCAPprune-encrypted-pcapSystemNew flows excluded from PCAP storage per keywordmatched regex keyword{1E92FD61-5129-499D-0A12-883E9FC1C00C}
File Extractionsave_binariesSystemExtracted files: events, bytes, file typesevent name or libmagic type{282E13BE-9691-4B61-F0A3-21CB90792478}
ShiftX MetricsshiftxDerivedTop-K rank-shift scores of a monitored group<CounterGUID>-<meter>{22B6E494-382B-47D5-D914-591CF8572343}
SNIsni-tlsL7 ApplicationPort-443 flow bytes and flows per ClientHello SNISNI hostname{38497403-23FB-4206-65C2-0AD5C419DD53}
SNMP-Interface ²snmppollExternal DataSNMP in/out octet rates and utilization per interfaceAgent IPv4 + ifIndex (hex){9781DB2C-F78A-4F7F-A7E8-2B1A9A7BE71A}
FlowIntf_bx_QOSsnmpqospollExternal DataCBQOS stats per interface and classrouter_ifindex\classid{D3F7A892-4E1B-4C6D-8A5F-2E1C9B7D4A63}
QoS-ClasssnmpqospollExternal DataLabel store for CBQOS class-map names (no counters)CBQOS class ID{116888A7-23B4-4873-5691-E6E0806CCB11}
QOS-TrafficsnmpqospollExternal DataCBQOS pre/post-policy, drop, queue stats per classCBQOS class ID{1AB9F248-1E49-4245-571A-55BCDA658843}
Proxied Serverssquid-proxyL7 ApplicationTunnel bytes and hits per HTTP CONNECT targetCONNECT host:port{B7571E87-F794-4BF6-A57A-EEA8A90F0324}
SSH Endpointsssh-alertL7 ApplicationSuccessful SSH logins per client/server software bannerSSH version banner{E6A387F4-5B51-4C8B-86FD-DE6258D3F214}
TCP Analyzertcp-analyzerL4 TransportPer-host TCP setup RTT, retransmissions, timeoutsIP address (v4/v6){E45623ED-744C-4053-1401-84C72EE49D3B}
TCP Analyzer Appstcp-analyzerL4 TransportPer-server-port TCP setup RTT, retransmissions, timeoutsport p-XXXX{24DBD78F-CBB6-4383-7A78-B2C734FC480F}
TLS Public Key Algotls-metrics-packL7 ApplicationCertificates per public key algorithm or EC curveAlgorithm name{88F603AE-4519-4E3D-E1C8-D1882E398724}
TLS Sig Algotls-metrics-packL7 ApplicationCertificates per signature algorithmAlgorithm name{C90640F6-ACD1-4BE5-92FF-A417DC6A987A}
TLS Versionstls-metrics-packL7 ApplicationPort-443 flows and bytes per negotiated TLS versionDecimal TLS version{44DBB4E0-B79F-4FB5-A437-3CFEDFB7B65E}
JA3 FINGERPRINTtls-printL7 ApplicationClientHello JA3 and ServerHello JA3S hits per hashMD5 hex (uppercase){E8D5E68F-B320-49F3-C83D-66751C3B485F}
JA4 FINGERPRINTtls-printL7 ApplicationClientHello hits per JA4 fingerprintJA4 string{D7C3F2B1-9D4E-4A8F-B6E5-123456789ABD}
JA4S FINGERPRINTtls-printL7 ApplicationServerHello hits per JA4S fingerprintJA4S string{D8D4E3C2-AE5F-4B90-C7F6-234567890BCD}
Outside Umbrella Top-1Mumbrella-top-1mL7 ApplicationDNS names not in the Umbrella Top-1M listDNS name{3317EEB3-CE83-4C8F-E321-79E7194BD974}

Not covered here​

  • Groups you create, such as crosskey, filter, Interface Tracker (IFTRACK_*) or custom Lua groups, are documented by whoever creates them. Their key format follows the parent groups.
  • Registry entries with no code. Some installs list HTTP URL Category, BGP-Prefix Home or Flow-Prefix-Home. No current probe, plugin or app code fills them, so they stay empty.
  • Subnets, Interfaces and VSAT classes exist in the probe source but are not registered, so no such groups appear.
  • stablekeys (Trisul App) defines no group. It watches FlowGens and raises an alert when an exporter key stops reporting.

See meters in the product​

Go to Customize → View Meters to see the meters of any group on your probe. Select the group from Jump to see meter info in counter group.

View Meters

Figure: View Meters

The table there shows the same columns as the meter tables in this reference: ID, Description, Top Count, Bottom Count, Type and Units.