Plugin Telemetry

Hey Developers,
I’m curious to know how you are monitoring the use of your plugins while deployed in the wild. I’d like to understand how often users interact with the plugin and which functionality they use the most. Also, some basic location data to spot preferences across geographies, Rhino versions etc.

I have a working prototype counting interactions with my commands and save the count to Supabase on document close, but maybe there are existing solutions which do it more efficiently?

Also, what’s McNeel’s policy on user data collection? Are there any limitations on how much plugin developers are allowed to track?

1 Like

We use Serilog Structured Logging coupled with Elastic Cloud database and Kibana for data exploration and visualization. May well be better setups but it works well enough for us.
Make sure you build in a switch to turn it off in your plugin, some customers will require that.

4 Likes