@@ -43,6 +43,7 @@ See [getting started](docs/getting_started.md).
| fluentbit.image.repository | string | `"registry.cern.ch/monit/cern-it-monitoring-fluent-bit"` | image repository applied to all Fluent Bit instances |
| fluentbit.image.tag | string | `"3.2.6"` | image tag applied to all Fluent Bit instances |
| kubernetes.clusterName | string | `""` | name of the kubernetes cluster to monitor. This value will be appended to very metric and log via k8s_cluster_name label. This bit is required if fluentbit is enabled (default) |
| logs.collectedNamespaces | list | `["default"]` | restrict log sending from pods in these namespaces. you can provide literals or regular expressions. |
| logs.enabled | bool | `false` | indicates if logs metrics components should be enabled or not. If set to false no logs component will be installed nor configured |
@@ -12,12 +12,22 @@ To **enable** or **disable** logs collection:
logs:
enabled:true# Set to 'false' to disable logs collection
```
If `logs.enabled` is set to `false`, no logging components (such as Fluentbit) will be installed or configured.
## 2. Base Logs Collected
By default, the chart deploys **Fluentbit** as a DaemonSet to gather logs from Kubernetes containers. Fluentbit is highly efficient and lightweight but can generate substantial API requests in large deployments (100+ nodes) due to the Kubernetes filter.
Without further user-provided configuration, only logs generated by pods in the `default` namespace are collected. To augment the set of mined namespaces, please configured the desired list of namespaces via the `logs.collectedNamespaces` setting, for example:
```yaml
logs:
collectedNamespaces:
-myapp
-user.+
```
### Fluentbit Configuration
Fluentbit collects logs from the `/var/log/containers/` directory and applies a set of filters before forwarding them to the central monitoring system via the OpenTelemetry protocol.