Design your installation based on plugin usageedit
This documentation is still in development and may be changed or removed in a future release.
Our recommandations for your Logstash Kubernetes installation vary depending on the types of plugins that you plan to use, and their respective requirements.
Pull-based pluginsedit
Designing recommendations for pull-based plugins depend on whether or not the plugins support autoscaling.
Autoscaling
These plugins can autoscale by tracking work done externally to Logstash. Examples include Kafka, Azure Event Hubs in certain configurations, and others.
Recipe link.
Non-autoscaling
Description.
Recipe link.
Push-based pluginsedit
Designing recommendations for push-based plugins depend on whether or not the plugins support autoscaling.
Autoscaling
These plugins support autoscaling. Examples include Beats, HTTP, and others.
Recipe link.
Non-autoscaling
These plugins do not support autoscaling, either because they have a dependency on sincedb, or because …
Recipe link.
Other resources required
Certain plugins require additional resources to be available in order for them to run. Examples include the JDBC and JMS plugins, which require JARs to be available on on classpath.
Recipe link.