logging-operator | Logging operator for Kubernetes

by banzaicloud Go Version: 3.17.10 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | logging-operator Summary

logging-operator is a Go library typically used in Logging applications. logging-operator has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This operator helps you bundle logging information with your applications: you can describe the behavior of your application in its charts, the Logging operator does the rest.

Support

Quality

Security

License

Reuse

Support

logging-operator has a medium active ecosystem.

It has 1062 star(s) with 256 fork(s). There are 34 watchers for this library.

It had no major release in the last 12 months.

There are 82 open issues and 318 have been closed. On average issues are closed in 84 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of logging-operator is 3.17.10

Quality

logging-operator has no bugs reported.

Security

logging-operator has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

logging-operator is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

logging-operator releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of logging-operator

Get all kandi verified functions for this library.

logging-operator Key Features

No Key Features are available at this moment for logging-operator.

logging-operator Examples and Code Snippets

No Code Snippets are available at this moment for logging-operator.

Community Discussions

Trending Discussions on logging-operator

Why does rancher logging operator have both Fluent Bit and Fluentd?

QUESTION

Why does rancher logging operator have both Fluent Bit and Fluentd?

Asked 2021-Jan-14 at 02:19

Rancher v2.5 logging uses the banzai cloud logging operator - see here.

The operator deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system. Fluent Bit queries the Kubernetes API and enriches the logs with metadata about the pods, and transfers both the logs and the metadata to Fluentd. Fluentd receives, filters, and transfer logs to multiple outputs

I don't know much about Fluent Bit, but the documentation says

Fluent Bit is an open source Log Processor and Forwarder which allows you to collect any data like metrics and logs from different sources, enrich them with filters and send them to multiple destinations.

Sounds quite similar to Fluentd (and other log forwarders like LogStash).

So what would be the reason/benefit of having both Fluent bit and Fluentd as part of the logging operator?

...

ANSWER

Answered 2021-Jan-14 at 02:19

Performance and resource utilization. FluentBit is much more lightweight and therefore less expensive to run as a DaemonSet. Forwarding on to FluentD also makes sense, since FluentD has hundreds more plugins and is generally more flexible and configurable. The FluentBit docs themselves say:

Fluentd is a great option due to it flexibility and availability of plugins (more than 300 extensions!) but if the data collection will happen in an Embedded environment or an IoT device where the system capacity is restricted, Fluent Bit is the solution to use.

So what it looks like this operator is doing is using FluentBit to forward the logs in as lightweight a process as possible, then using FluentD to do the heavy processing/aggregating/shipping to destinations, the same way an app might use its own log forwarder to send to FluentD (for example over the HTTP input from somewhere outside of Kubernetes) and then have FluentD manage processing those logs and shipping them to destinations.

Source https://stackoverflow.com/questions/65712383

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install logging-operator

Follow these quickstart guides to try out the Logging operator!.
Deploy Logging Operator with Kubernetes manifests or Helm chart. Caution: The master branch is under heavy development. Use releases instead of the master branch to get stable software.