2V0-71.23 Question 97
Select 3A team deploying Tanzu Kubernetes clusters wants to implement a centralized logging solution. They decide to use Fluent Bit to aggregate logs from all worker nodes in the cluster. What are some of the key roles Fluent Bit plays in this scenario?
- A
Collects logs from multiple sources, such as container logs and system logs, on each node.
- B
Provides persistent storage for long-term log retention directly within Tanzu Kubernetes clusters.
- C
Transforms and filters logs to remove unnecessary noise before forwarding them.
- D
Forwards logs to external systems like Elasticsearch, Splunk, or Kafka for analysis and storage.
- E
Manages log rotation and compression on the nodes to save disk space.
Show answer and explanation
Correct answers: A, C, D
Explanation
Fluent Bit is a lightweight and efficient log processor and forwarder commonly used in Tanzu Kubernetes clusters. Its primary roles include collecting logs from various sources, transforming or filtering them to improve log quality, and forwarding them to external systems for further analysis or storage. However, it does not provide persistent storage for logs nor does it manage log rotation or compression, which are outside its scope of functionality.
- A. Correct.
Correct: Fluent Bit is designed to collect logs from sources such as container logs, system logs, and application logs on each node in the cluster.
- B. Incorrect.
Incorrect: Fluent Bit does not provide persistent storage for long-term log retention. It acts as a lightweight log processor and forwarder, not a storage solution.
- C. Correct.
Correct: Fluent Bit can transform and filter logs to remove unnecessary data, reduce log size, and improve log quality before sending them to external systems.
- D. Correct.
Correct: Fluent Bit forwards logs to external systems like Elasticsearch, Splunk, or Kafka, which are responsible for log analysis, visualization, and long-term storage.
- E. Incorrect.
Incorrect: Fluent Bit does not manage log rotation and compression. These are typically handled by other tools or system configurations on the nodes.