Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Vault documentation: updated client count FAQ document #13330

Merged
merged 2 commits into from
Dec 2, 2021
Merged

Vault documentation: updated client count FAQ document #13330

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
945cdca
modified based on feedback
taoism4504 Dec 2, 2021
2029a57
Update faq.mdx
taoism4504 Dec 2, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/content/docs/concepts/client-count/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Although client counts have been available via the usage metrics UI since Vault
* Vault 1.6: Introduction of client counts in the usage metrics UI
* Vault 1.8:
- Eliminated wrapped tokens and control groups from client count, thereby reducing the non-entity token count. Previously, the creation and usage of control groups and wrapping tokens affected the client count each time the response is read (in the case of a wrapping token) and each time a control group was created (a non-entity token was created)
- Changed logic of counting of non-entity tokens on usage instead of at create time (therefore resulting in more accurate client counts)
- Changed the logic of counting of active identity entities on usage instead of at create time, resulting in more accurate client counts
* Vault 1.9:
- Changed the non-entity token computation logic to deduplicate non-entity tokens, reducing the overall client count. Moving forward, non-entity tokens, where there is no entity to map tokens, Vault will use the contents fo the token to generate a unique client identifier based on the namespace ID and associated policies. The clientID will prevent duplicating the same token in the overall client count when the token is used again during the billing period.
- Changed the tracking of non-entity tokens to complete on access instead of creation.
Expand Down