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.

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

Proposal for limit page update #2263

Closed
wants to merge 5 commits into from
Closed

Proposal for limit page update #2263

wants to merge 5 commits into from

Conversation

eickler
Copy link
Contributor

@eickler eickler commented Jul 9, 2024

This is a draft PR, general review is not yet required.

Copy link
Contributor

github-actions bot commented Jul 9, 2024

Preview available here

</table>
Your {{< product-c8y-iot >}} service includes so-called ``quotas``. These quotas ensure that the service operates within the guarantees of the {{< product-c8y-iot >}} service-level agreements.

There are three types of quotas in {{< product-c8y-iot >}}:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the 3rd type of quotas is not present in the list below, is that intentional?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, well spotted. It was just the idea that we could have plans with different limits. I'll commit it out until we have that facility.

Comment on lines +58 to +61
|[Notifications 2.0 message backlog](/change-logs/?#cumulocity-undefined-advance-notice-of-reduced-storage-limits-for-notifications-2.0-and-microservice-based-data-broker)|Hard|25 MB|
|[Notifications 2.0 time-to-live](/change-logs/?#cumulocity-undefined-advance-notice-of-reduced-storage-limits-for-notifications-2.0-and-microservice-based-data-broker)|Hard|36 hours|
|[Microservice-based data broker message backlog](/change-logs/?#cumulocity-undefined-advance-notice-of-reduced-storage-limits-for-notifications-2.0-and-microservice-based-data-broker)|Hard|50 MB|
|[Microservice-based data broker time-to-live](/change-logs/?#cumulocity-undefined-advance-notice-of-reduced-storage-limits-for-notifications-2.0-and-microservice-based-data-broker)|Hard|36 hours|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are technically all configurable and we document how to configure them, hence my question in the doc about whether "configurable" is a type of limit or a property of limits.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@scmi-c8y For me, there is a difference between what you can theoretically configure by manipulating internal configuration files and what we offer generally to be configurable.

You can increase the size of message backlogs or the array limit in CDH, but I assume that the system has not been tested with the setup and there are consequences to system dimensioning (file system space? memory usage? -- otherwise the limit would not be there in the first place).

So rather than giving a carte blanche to change it, I would document it as hard limit. What we could do, though, is to offer a professional service to test for different hard limits for customers.

@eickler
Copy link
Contributor Author

eickler commented Oct 21, 2024

I''ll close this pull request; further discussion can be carried out as part of PR #2452

eickler added a commit that referenced this pull request Oct 21, 2024
@eickler eickler closed this Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants