Observation
When managing SSR via Mist WAN Assurance, application identification is far more limited than in the legacy SSR Conductor.
Conductor supported multiple identification methods (L3/L4 signatures, FQDN/SNI parsing, TLS CN inspection, heuristics), allowing SSR to classify most flows into meaningful applications.
In Mist, only applications included in the predefined Mist app catalog are recognized.
All other flows appear as "Unknown", even though the SSR dataplane is fully capable of identifying them for routing/QoS purposes. In other words, the SSR classification engine still works - the Mist visibility layer simply does not expose or map these applications.
Question
Is there a published roadmap or timeline for expanding Mist's application identification for SSR - specifically support for custom application definitions and deeper classifiers (e.g., SNI/TLS-CN) similar to what Conductor provided?
This capability is critical for environments with internal apps and non-catalog SaaS services that currently remain "Unknown" in Mist.
------------------------------
Hannu Rokka
Senior Advisor (DataCom)
------------------------------