Skip to content

Commit

Permalink
docs: add logs collection to windows section
Browse files Browse the repository at this point in the history
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
  • Loading branch information
Dominik Rosiek committed Mar 5, 2024
1 parent f8769b7 commit 085240a
Showing 1 changed file with 32 additions and 2 deletions.
34 changes: 32 additions & 2 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,9 @@ Falco is embedded in this Helm Chart for user convenience only - Sumo Logic does

Support for Windows is experimental.

Windows nodes are supported only for metrics collection. To enable it, add the following configuration to your `user-values.yaml`
#### Merics collection

Windows nodes are supported for metrics collection. To enable it, add the following configuration to your `user-values.yaml`

```yaml
prometheus-windows-exporter:
Expand All @@ -137,4 +139,32 @@ prometheus-windows-exporter:
It will send `windows_` prefixed metrics to Sumo Logic.

> [!NOTE] We currently do not have dashboards using using these metrics.
> [!NOTE] We currently do not have dashboards using these metrics.

#### Logs collection

There is support for logs collection, but only container ones. In order to enable logs collection, please add the following configuration to your `user-values.yaml`:

```yaml
sumologic:
logs:
collector:
otelwindows:
enabled: true
otelwindows:
daemonset:
nameservers:
- ${NAMESERVER_IP}
```

where `${NAMESERVER_IP}` is a cluster DNS server IP. For the following example:

```yaml
kubectl get service kube-dns -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kube-dns ClusterIP 10.100.0.10 <none> 53/UDP,53/TCP 13d
```

it will be `10.100.0.10`.

> [!NOTE] Nameserver will be forcefully used as primary DNS server for the whole Node

0 comments on commit 085240a

Please sign in to comment.