In testing out a Windows Eventlog collection system using the Elastic stack, I discovered a curious problem with the password I was using for connecting through Xpack. I had used a system generated password that used several dashes ( - ) in the password, which Logstash refused to parse, saying that I was missing a closing brace at that line.
It took me a while to discover that this was the problem, since the Xpack passwords for my Kibana and Elastic installs also have dashes in them and had no problems (but they're parsed in the .yml file, NOT the config file). Putting quotes around the password allows the config file to be fully parsed, but the password is presented WITH the quotes, so it generates a bad password error when connecting to Elastic.
I'm curious if anyone else has seen this problem, and if there's a list of unparsable characters for the Logstash configuration file?