Current FormRun telemetry is too limited in the information it provides. To make more effective use of it, please add customization information:

• Is a saved view applied?
• If so, which one, and on which level (personal or shared) was the view created
• Has the query been manipulated?
• If so, provide the query details (preferrably SQL) when startup exceeds a certain threshold, for example log it above 1s
• The MenuItem we were called from
• CallerSource information

When users start customizing forms, it is often a problem that their manipulations are not performance-effective. Isolating these cases is very difficult, mostly because you need the cooperation of the users, which have to understand what's happening to a certain extent. Having this telemetry, an administrator could continously monitor the system for bad customizations.