Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: rename clusterCollection.logs -> .logFiles #130

Merged
merged 2 commits into from
Dec 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -210,15 +210,15 @@ spec:
enabled: true # enables log forwarding for pods with tracing injected
```

#### Logging support via pod log files
#### Fetching container logs via files

Workloads that are using runtimes not supported by current Lumigo OTEL distro (e.g. Go, Rust) can still send logs to Lumigo, via logs files from containers that k8s manages on each node in the cluster.
The Lumigo Kubernetes operator will automatically collect logs from those files and send them to Lumigo, once the following setting is applied when installing the operator:

```sh
helm upgrade -i lumigo lumigo/lumigo-operator \
# ...
--set "clusterCollection.logFiles.enabled=true"
--set "clusterCollection.logs.enabled=true"
--set "lumigoToken.value=t_123456789012345678901"
```

Expand All @@ -230,9 +230,8 @@ echo "
lumigoToken:
value: t_123456789012345678901
clusterCollection:
logFiles:
enabled: true
logs:
enabled: true
include:
- namespacePattern: some-ns
podPattern: some-pod-*
Expand Down
Loading