@kami619 - thank you for this change. Pointing to the user metrics is a good start.

I would like it to be more specific about the events that are relevant to the sizing guide, so you would name login, refresh_token and client_login (not sure about the last one, please verify).

I see that it is currently part of the "Calculation example" section. If we would move it to its own section, we can add more context on when and how to use this. A draft statement in that new section could be "Use the the metrics X, Y and Z to measure the activity around user login, refresh token and client credential grant to validate your inputs for sizing calculation, monitor user activity load changes in the daily and weekly cycle, and watch out for trends that would require re-sizing your system".

If we see that the login event captures not only password based logins but also cookie based logins, this could be a note in the documentation as well. Maybe using some one the HTTP metrics can be a help to sort cookie based logins from password based logins: Password based logins will show as s POST once you submit the form, and the cookie based ones won't.

Please expand and add more context and details as needed :D

@ahus1 thanks for the feedback. I have updated the docs, but still couple of things are pending from how I want it to look, such as verifying the metrics for particular events.

You could still share me any more feedback based on the changes I did so far.