You are using a deprecated config setting "truststore" set in http. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Use `ssl_truststore_path` instead

Elastic Stack Logstash
1

You are using a deprecated config setting "truststore" set in http. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Use ssl_truststore_path instead If you have any questions about this, please ask it on the Logstash - Discuss the Elastic Stack discussion forum {:name=>"truststore", :plugin=><LogStash::Outputs::Http keystore_password=>, http_method=>"post", content_type=>"application/json", truststore_password=>, format=>"message", keystore=>"/var/run/secrets/java.io/keystores/fi-keystore.jks", truststore=>"/var/run/secrets/java.io/keystores/sip-tls-truststore.jks", id=>"XXX", message=>"{"faultName":"LOGSTASH_1","createdAt":"%{errorCreatedAt}","serviceName":"logstash","severity":"Major","description":"Logstash parsing failure. See index XXX-error-XXX-%{+YYYY.MM}","faultyResource":"ewp-lwac","expiration":3600}", url=>"https://xxx:9999/yyy/v1/xxx", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_6fdd35a4-eda1-4965-8a7e-05exxx", enable_metric=>true, charset=>"UTF-8">, workers=>1, request_timeout=>60, socket_timeout=>10, connect_timeout=>10, follow_redirects=>true, pool_max=>50, pool_max_per_route=>25, keepalive=>true, automatic_retries=>1, retry_non_idempotent=>false, validate_after_inactivity=>200, ssl_enabled=>true, ssl_verification_mode=>"full", cookies=>true, keystore_type=>"JKS", truststore_type=>"JKS", retry_failed=>true, retryable_codes=>[429, 500, 502, 503, 504], http_compression=>false>}

2

Hi @Prateek_Garg,

Welcome to the community! From the error message it looks like you are using the setting truststore which is deprecated and will be removed in a future version. The message is advising you to switch to the ssl_truststore_path instead, as covered here.

If that isn't clear, can you share the version of Logstash you are using and your configuration?

Hope that helps!

3

In the error description it says
Logstash parsing failure. See index XXX-error-XXX-%{+YYYY.MM}

But there is no such index created in the system. So I am not sure whether it is a misleading message or not. If not then which parsing has failed.

4

Thanks for pointing that out @Prateek_Garg. It looks like an error parsing a pattern in your config but it's difficult to say why. Can you share your configuration and the version of Logstash you're using?