The configuration file of the Redis module for Filebeat seems to support normal logs (from the Redis server's log file) and slowlogs (from the API)... see:
I can understand how the logs are picked up from the log files, but I had no idea that Filebeat had the capability to issue a command to a server and thus retrieve information. Is there any documentation on how this feature works, and in what format the slowlogs are shipped?
Hi, thanks for the doc link. I understand where Filebeat is getting the slowlogs from, however I was looking for more detail in how this works in Filebeat, given that Filebeat is meant to monitor files. I was also looking for the format/structure in which they are shipped.
Filebeat can also retrieve "logs" from remote systems like hosts or queues like Kafka, or Amazon S3. The idea is that everything that can be parsed as log line can be parsed by Filebeat.
Is it required to use the Redis filebeat module for shipping slowlogs, or can it be configured without it?
I'm looking to ship Redis logs to a third party managed ELK, so it's not possible to set up the pipeline and resources that the module seems to expect.
Yes, send them to Logstash node of ELK, that's right. I can use Filebeat to ship Redis logs, but is it also possible to ship the slowlogs without being able to set up the environment (pipeline etc)?
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.