Ability to Place Profiles in Monitoring Mode While Enabling Full Analytics

Currently, when a Control D profile is used in a "monitoring mode" (where traffic is fully allowed), the analytics dashboard only displays the raw domains visited. While explicitly adding Native Services in "Bypass/Allow" mode maps service names to the analytics logs, this metadata is entirely missing for native Web Filtering Categories.I would like to request that Web Filtering Categories also be mapped and displayed within profile analytics when running a passive monitoring policy. This could be achieved by introducing an explicit "Allow/Monitor" action state directly within the Native Categories settings, or by creating a dedicated global "Monitoring Mode" switch at the profile level.
Secondary Benefit: Introducing an explicit "Allow" action for Native Categories would also provide helpful, granular override capabilities for administrators utilizing a strict, block-by-default profile posture.