Personal tools
Skip to content. | Skip to navigation
Ruby API for Elasticsearch. See the `elasticsearch` gem for full integration.
Ruby integrations for Elasticsearch (client, API, etc.).
A syslog processing system that stores received messages in an Elasticsearch database. When coupled with the graylog-web-interface, which provides a front-end web interface, will allow for powerful message analytics for a server network. Other information, including but not limited to user credentials, stream configurations, etc, are stored in MongoDB
Beats - Lightweight shippers for Elasticsearch & Logstash The Beats are lightweight processes, written in Go, that you install on your servers to capture all sorts of operational data like logs, operating system metrics or network packet data, and to send it to Elasticsearch, either directly or via Logstash, so it can be visualized with Kibana.
You know, for windows event logs Winlogbeat is an open-source log collector that ships Windows Event Logs to Elasticsearch or Logstash. It installs as a Windows service on all versions since Windows XP.
Functionbeat is an Elastic Beat that you deploy on your serverless environment to collect events generated by cloud services and ship the events to Elasticsearch. This version supports deploying Functionbeat as an AWS Lambda service and responds to the triggers defined for the following event sources: CloudWatch Logs Amazon Simple Queue Service (SQS) Kinesis Filebeat is an open source file harvester, mostly used to fetch logs files and feed them
Packetbeat is an open source network packet analyzer that ships the data to Elasticsearch. Think of it like a distributed real-time Wireshark with a lot more analytics features. The Packetbeat shippers sniff the traffic between your application processes, parse on the fly protocols like HTTP, MySQL, PostgreSQL, Redis or Thrift and correlate the messages into transactions. For each transaction, the shipper inserts a JSON document into Elasticsearch, where it is stored and indexed. You can then use Kibana to view key metrics and do ad-hoc queries against the data. To learn more about Packetbeat, check out https://www.elastic.co/products/beats/packetbeat.
Journalbeat is a lightweight shipper for forwarding and centralizing log data from systemd journals. Installed as an agent on your servers, Journalbeat monitors the journal locations that you specify, collects log events, and forwards them to either to Elasticsearch or Logstash.
Filebeat is an open source file harvester, mostly used to fetch logs files and feed them into logstash. Together with the libbeat lumberjack output is a replacement for logstash-forwarder. To learn more about Filebeat, check out https://www.elastic.co/products/beats/filebeat.