You're right, currently they are only surfaced in the exception view.
Customers with a similar need (including ourselves for the applications we've instrumented with Analytics) have typically resorted to logging this kinds of information using a dedicated TrackFeature calls, right after monitor.Start or after user login or whatever constitutes a suitable "start point" to your app where you have gathered the information you need.
For instance, at startup you could call TrackFeature("LoginType." + loginType) just once, where loginType could then be "Citrix", "Web", "RDP", or whatever. You can then both see the distribution of LoginType.* as a graph and also filter on that feature name in an advanced query to show only data where "LoginType.Citrix" exists. Note, it will only work in advanced queries and not globally affect the display of all graphs in one fell swoop, but currently it's the best way to do what you want.
ICENIUM MONITOR AVAILABLE FOR DOWNLOAD.
Monitor and track applications built with Icenium at run-time. Reduce support by fixing run-time crashes as they occur, obtain user insights such as location and system configuration, find and remove application bottlenecks, and track which features are used most to help prioritize development.
Try Icenium with EQATEC Analytics today >>