I'm using API call to pull data into json docs and ingesting through logstash, but when I go to run my config file, I get this in log stash
[2017-09-15T16:08:02,579][INFO ][logstash.pipeline ] Pipeline main started
[2017-09-15T16:08:02,658][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600}
No actual data is ingested however and an index is not created.
Same thing happens with JSON or XML.
I have no clue what I'm doing wrong because the logs do not show an error.
What if you comment out the elasticsearch output and focus on the stdout output? Are you getting anything? Are you sure Logstash has read access to the JSON files?
If I comment it out, will it still pipe to the index?
No, and that's the whole point. We want to simplify the configuration to make it easier to debug it.
How can I check its read permissions? I run it as admin.
Make sure the file itself is readable to the user that runs Logstash and that all directories leading up to the directory are at least executable to that user. The last directory, /Users/S.AWDRSRV/Downloads/MDMCSV/json, also needs to be readable.
You can increase Logstash's logging verbosity (there's a command line option for it) and it'll log additional details about what it's doing, including what filename patterns are expanded to. If your filename pattern expands to nothing that usually means that it doesn't have sufficient permissions.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.