You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2020. It is now read-only.
As an operator of a Sensu server, I can prevent oversized events from being persisted to the datastore.
Current Behavior
Operators cannot reasonably prevent large check results from being piped into Sensu via client socket or standalone checks.
Possible Solution
Implement configurable limits on persisted event sizes.
Context
Under certain conditions, events of 100mb have caused Sensu instances to become unresponsive. Without the ability to prevent events like these from being persisted to the datastore, this could be used as a vector for denial of service attacks.
Your Environment
Sensu version used: 1.8.0
The text was updated successfully, but these errors were encountered:
Expected Behavior
As an operator of a Sensu server, I can prevent oversized events from being persisted to the datastore.
Current Behavior
Operators cannot reasonably prevent large check results from being piped into Sensu via client socket or standalone checks.
Possible Solution
Implement configurable limits on persisted event sizes.
Context
Under certain conditions, events of 100mb have caused Sensu instances to become unresponsive. Without the ability to prevent events like these from being persisted to the datastore, this could be used as a vector for denial of service attacks.
Your Environment
The text was updated successfully, but these errors were encountered: