-
Notifications
You must be signed in to change notification settings - Fork 57
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.
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
Add content to usage page #2095
Conversation
Newest code from ka0ula has been published to preview environment 🚀 Latest deployment was built on 2024-11-27 13:42:34 (17b01a71e7117f2882d7773a038e8999698edacd). |
docs/getting_started/usage.md
Outdated
Tracking consumption empowers users to proactively adjust their data usage and consider upgrading their plans if necessary. | ||
|
||
!!! note | ||
If you are on an **Intelligence pla**n only, please note that you will not see any analyzed bytes, as there are none associated with this plan. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pla**n
docs/getting_started/usage.md
Outdated
- **Current usage**: Displays the total bytes analyzed (e.g., 100 GB) and highlights any excess usage against the predefined fair use limit (e.g., 210 GB). | ||
- **Fair use indicator**: A visual marker shows whether current consumption exceeds the fair use threshold. | ||
|
||
### Fair use policy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure we should document our usage policies in this document. It should be in the contract.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gbossert you recommend removing the whole section? I think we need to explain what we mean by fair use and how it is calculated
Co-authored-by: Georges Bossert <[email protected]>
Co-authored-by: Georges Bossert <[email protected]>
Co-authored-by: Georges Bossert <[email protected]>
Co-authored-by: Georges Bossert <[email protected]>
Co-authored-by: Georges Bossert <[email protected]>
Pull request was merged, preview was removed. |
No description provided.