docker
"Use It Or Lose It" with Desktop Insights
Tell us about your request Better metadata around org members and any membership changes to assist in license governance
- joined may be ages ago, but if they were just added to the org than telemetry may be lagging and reclaim shouldn't be done. So having the org.joined timestamp can help avoid removal, but also to nudge folks to complete onboarding after a license is issued. e.g org.joined diff w (user.lli or user.lastseen) > 15d
- frequent disable and enable for the same email may indicate that the telemetry is broken on their desktop install or they are on a legacy version. may need admin intervention to get them working as expected. this might need a way to query deactivated users (removed from org) and timestamps, but maybe easier to do as a report similar to the unassociated views.
Ideally this would be in some sort of report format, but even having that type of data in the export allows me to figure it out.
Which service(s) is this request for? Docker Desktop Insights
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? To meet our financial governance I need to show that the licenses are being actively used which means i need to reclaim on a frequent basis. I would like to reduce some of the false positive results i am getting from "unused" seats.
Are you currently working around the issue? I use our license allocation data combined w active membership exports in a separate tool to try and avoid some of these issues.
Tacking onto the same Issue since it's all about active governance.
Last Logged In and Last Seen dates are a bit wonky. I would expect that LLI would be within some window of the Seen date, but I am seeing seen as months newer than LLI. Not sure if thats because using a refresh_token doesn't count toward a login or what, but been making it tougher to detect who is actively using the license.
- join remains linked to account.create versus when they were last activated in the org which may have no relationship to their affiliation to the org
- lli seems to only trigger on the browser oauth flow so refresh_token use doesn't seem to be in scope making it seem like the JWT has a huge expiration window
- seen I know has ties back to different approaches to telemetry available per release, but given the other data points when can seen indicate that a license is inactive.
Just like to see better patterns we can use based on the data in the members export or as Admin views in Insights to help manage the licenses effectively.