Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Are “groups” and “roles” different concepts? ​

I think the most natural place to put the user and role CRUD telemetry would be in Identity’s UserManager and RoleManager classes. There are many other ways to update the Identity database without going through those Manager classes, but at that point I’d say you’re on your own for this kind of telemetry. Same goes if you’re not using Identity.

As far as updates go, are there any particular updates we’re interested in? Since Identity makes the TUser and TRole generic parameters, it’s hard for us to efficiently know exactly what is updated during a user update.

We could go out of our way to check whether certain things like user name, email, password, security stamp, phone number, email confirmation status, roles, claims, etc… have been updated, but doing so would require a separate query to the store for each property. While this is generally fast for the EF stores since they just read properties from TUser and TRole, that’s not guaranteed to be the case for every store.

To me yes groups & roles are different concepts especially as we use them for different things.

I agree with your thoughts about the most natural place to be triggered the generation of metrics and that it is only available to users using Identity.

In terms of updates I am not interested in implementing a change log persee but rather a journal of which entity is being changed, the type of entity & action type. Suggest checking the otel schematics for fields and also check the Elastic common schema fields which are being incorporated into otel.