Search Results for "log"

Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream. Unlike other logging systems, Loki is built around the idea of only indexing metadata about your logs: labels (just like Prometheus labels).

The Logging operator solves your logging-related problems in Kubernetes environments by automating the deployment and configuration of a Kubernetes logging pipeline. The Logging operator manages the log collectors and log forwarders of your logging infrastructure, and the routing rules that specify where you want to send your different log messages. You can filter and process the incoming log messages using the flow custom resource of the log forwarder to route them to the appropriate output. The outputs are the destinations where you want to send your log messages, for example, Elasticsearch, or an Amazon S3 bucket. ...

...Beats is lightweight in that it has a small installation footprint, uses limited system resources and has no runtime dependencies. It consists of: Auditbeat (for audit data), Filebeat (for log files), Functionbeat (serverless shipper), Heartbeat (for uptime monitoring), Metricbeat (for metrics), Packetbeat (for monitoring network data), and Winlogbeat (for Windows Event logs), with many other Beats created by the community.

Logspout is a log router for Docker containers that runs inside Docker. It attaches to all containers on a host, then routes their logs wherever you want. It also has an extensible module system. It's a mostly stateless log appliance. It's not meant for managing log files or looking at history. It is just a means to get your logs out to live somewhere else, where they belong.

Stern allows you to tail multiple pods on Kubernetes and multiple containers within the pod. Each result is color-coded for quicker debugging. The query is a regular expression so the pod name can easily be filtered and you don't need to specify the exact id (for instance omitting the deployment id). If a pod is deleted it gets removed from tail and if a new pod is added it automatically gets tailed. When a pod contains multiple containers Stern can tail all of them too without having to do...

Kafka/distributed commit log service in Go. Protocol compatible with Kafka so Kafka clients and services work with Jocko. Use Serf for discovery, Raft for consensus (and remove the need to run ZooKeeper). Able to use percentages of disk space for retention policies rather than only bytes and time kept. Handling size configs when you change the number of partitions or add topics.