Logstash
Backend & InfraLogstash - transport and process your logs, events, or other data
Release History
View all versions →v9.5.3This release provides updates and bug fixes for Logstash. Please refer to the release notes for detailed information.
v8.19.215 fixesThis release of Logstash (8.19.21) includes several bug fixes to improve stability and performance across various plugins, including HTTP, JDBC, JSON, Elasticsearch, and File inputs/outputs.
v9.4.6This release provides download links and release notes for Logstash version 9.4.6.
v9.5.2This release provides download links and release notes for Logstash version 9.5.2.
v8.19.205 fixesThis release of Logstash (8.19.20) focuses on stability and performance improvements. It includes several bug fixes across various input, output, and filter plugins to address issues with connection handling, bulk API responses, memory leaks, and error handling.
v9.5.1This release provides download links and release notes for Logstash version 9.5.1.
v9.4.5This release provides download and release note links for Logstash.
v9.5.0This release provides downloads and release notes for Logstash version 9.5.0. Further details on changes are available in the linked release notes.
v8.19.1910 fixesLogstash 8.19.19 addresses several critical bugs across various plugins, including issues with proxy settings, Elasticsearch connections, memory leaks, and performance degradations. This release focuses on improving stability and reliability.
v9.3.81 fixThis release of Logstash addresses a bug in the Beats input plugin where proxy environment variables were not being respected. This ensures that network traffic from the Beats input plugin correctly uses configured HTTP proxies.
v9.4.4This release provides download links and release notes for Logstash version 9.4.4.
v9.3.7This release provides updates for Logstash version 9.3.7. Specific details regarding changes are available in the linked release notes.
v8.19.18This release provides updates for Logstash version 8.19.18. Specific details regarding changes are available in the linked release notes.
v9.4.3This release provides download links and detailed release notes for Logstash version 9.4.3.
v9.3.6This release provides access to the Logstash downloads and detailed release notes for version 9.3.6.
v8.19.17This release provides updates for Logstash version 8.19.17. Specific details regarding changes are available in the linked release notes.
v9.4.2This release provides access to Logstash downloads and detailed release notes for version 9.4.2.
v9.3.5This release provides updates for Logstash version 9.3.5. Specific details are available in the linked release notes.
v8.19.16This release provides updates for Logstash version 8.19.16. Specific details regarding changes are available in the linked release notes.
v9.4.1This release provides download links and detailed release notes for Logstash version 9.4.1.
v9.4.0This release provides access to the Logstash 9.4.0 release notes and download links.
v9.3.4This release provides access to Logstash downloads and detailed release notes for version 9.3.4.
v8.19.15This release provides access to the Logstash 8.19.15 release, with detailed notes available via the provided documentation link.
v8.19.14This release provides updates for Logstash version 8.19.14. Specific details regarding changes are available in the linked release notes.
v9.2.8This release provides access to Logstash downloads and detailed release notes for version 9.2.8.
Common Errors
IllegalArgumentException2 reportsIllegalArgumentException in Logstash often arises from incorrect data type handling, particularly when a field's expected data type doesn't match the actual data being processed. Fix this by ensuring your Logstash configuration correctly casts or converts field values to the expected types using processors like mutate or ruby filters *before* they are used in operations expecting specific data types, and validate field content/format with a grok filter if necessary..
NoMethodError2 reportsA "NoMethodError" in Logstash usually signifies that you are calling a method on an object that doesn't have that method defined (or the object is nil). Examine the stack trace to identify the problematic object and method call. Ensure the object is of the expected class and that the method name is spelled correctly. If the object is nil, check for initialization errors or incorrect configuration of the pipeline.
IllegalStateException1 reportThe IllegalStateException in Logstash often arises when a pipeline attempts to access a field or event's state in an invalid context, such as accessing a non-existent field or modifying an event after it has been finalized. Ensure your filters correctly handle null or missing fields using conditionals (if statements) before accessing them and avoid modifying the event after it has been sent to downstream stages like the output. Review configurations for potentially problematic field references or late modifications that could trigger this improper state access.
SaslAuthenticationException1 reportThe "SaslAuthenticationException" in Logstash typically arises from incorrect or missing SASL configuration for Kafka authentication, such as wrong username/password or missing Kerberos setup. To fix it, carefully verify the `sasl_username`, `sasl_password`, `security_protocol`, `sasl_mechanism`, and Kerberos-related settings (if applicable) in your Logstash Kafka input or output plugin configuration, ensuring they match the Kafka server's requirements. Double-checking the Kerberos configuration on the Logstash host, including `krb5.conf`, is also essential for Kerberos-based authentication.
StringIndexOutOfBoundsException1 reportStringIndexOutOfBoundsException in Logstash Grok filters typically occurs when the grok pattern attempts to access a substring beyond the actual length of the input string. To fix this, carefully review your grok patterns, especially those with optional or repeated elements, ensuring they correctly account for variations in input string length and structure, preventing out-of-bounds access. Use conditionals or anchors to guide the expression to the correct starting/ending point.
QueueRuntimeException1 reportQueueRuntimeException in Logstash often arises from corrupted data in the persistent queue, typically caused by abrupt shutdowns or disk issues. To resolve this, first try gracefully stopping Logstash and restarting it to allow for queue recovery. If the error persists, consider deleting the contents of the data/queue directory (after backing it up) to force Logstash to start with a fresh queue, understanding that this will result in data loss from the queue.
Related Backend & Infra Packages
Production-Grade Container Scheduling and Management
Node.js JavaScript runtime ✨🐢🚀✨
Promise based HTTP client for the browser and node.js
A modern runtime for JavaScript and TypeScript.
Deliver web apps with confidence 🚀
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
Subscribe to Updates
Get notified when new versions are released