Microsoft publishes pretty detailed information on the structure of the QoEMetrics database where you can find information about the TraceRoute table in this Technet article.
As you can surmise by the name, this table is meant to capture trace route information for calls. However, the table description gives no information on how to enable this feature.
You can enable this by adding a custom policy entry to a Lync/SfB client policy. Custom policy entries are used to enable features that Microsoft has decided not to make too obvious for users for one reason or another. If you've got custom policy entries, you'll see them at the top of the list when you run Get-CsClientPolicy. If you have several of those, you can see it in a more readable format by typing (Get-CsClientPolicy policyname).PolicyEntry
The relevant policy entry for enabling tracerouting is called "EnableTraceRouteReporting", and you can add it to a client policy by running the following commands:
Whoever has that policy applied to them will now publish trace route reports to the QoEMetrics database. However, the built-in Lync/SfB reports do not expose this anywhere, so you would only want to turn this setting on if you are using a 3rd party reporting and analytics tool such as Event Zero's UC Commander (FYI, if you don't already know, I work for them).$x = New-CsClientPolicyEntry -Name "EnableTraceRouteReporting" -Value "TRUE" $y = Get-CsClientPolicy -Identity policyname $y.PolicyEntry.Add($x) Set-CsClientPolicy -Instance $y
|Sample screenshot of traceroute data as it appears in UC Commander|
This can be very useful to help track down network issues in the call path. This won't necessarily point the finger at a specific switch or router in every circumstance, but it can help.
Be warned that enabling this will add a bit of size to your QoEMetrics database. The additional data isn't huge but its not negligible either. You should carefully evaluate the impact before turning this on.