-
Notifications
You must be signed in to change notification settings - Fork 218
Sumo Logic Limits document #5348
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
base: main
Are you sure you want to change the base?
Conversation
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.
@JV0812, this is a great list! However, I think you should add links directly to the sections that describe the limits. I added a few for you, but I think you need to do it for the rest of them. This is so that customers get more information about the limits. What do you think?
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.
Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com>
Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com>
…ogic-documentation into sumologic-limits
Thanks for your feedback @jpipkin1. I will add the doc links to the limits mentioned wherever applicable. |
- Maximum number of collector per organization is 10,000. | ||
- A single installed collector can handle up to 15,000 events per second. | ||
- Log messages greater than 64KB are truncated. | ||
- A collector or sources can have up to 10 fields. |
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.
- A collector or sources can have up to 10 fields. | |
- A collector or source can have up to 10 fields. |
## Partitions | ||
|
||
- **Maximum partitions**. Up to 50 per account. | ||
- **Optimal size**. Between 1%–30% of daily ingest. Ideally, with less than 5 TB data per day flowing into them. |
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.
- **Optimal size**. Between 1%–30% of daily ingest. Ideally, with less than 5 TB data per day flowing into them. | |
- **Optimal size**. Between 1%–30% of daily ingest. Ideally, with less than 5 TB data per day flowing into each. |
Purpose of this pull request
This pull request is to create a standalone doc for Sumo Limits.
Select the type of change
Ticket (if applicable)
Need document that lists all limits on Sumo Logic