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.

Sign up for GitHub

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

Jump to bottom

Update the instructions for FluentD configuration changes #324

Merged
merged 2 commits into from
Nov 27, 2019
Merged

Update the instructions for FluentD configuration changes #324

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
174a28c
Update the instructions for FluentD configuration changes
Nov 27, 2019
7087fd3
Change to Fluentd; Update redeploy command
Nov 27, 2019
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
17 changes: 15 additions & 2 deletions deploy/docs/Troubleshoot_Collection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,19 @@ To enable debug or trace logs from a specific Fluentd plugin, add the following
</match>
```

To enable debug or trace logs using the Helm chart, you can override the value `sumologic.fluentdLogLevel`:

```sh
helm upgrade collection sumologic/sumologic --reuse-values --set sumologic.fluentdLogLevel="debug"
```

For configuration changes to take effect in Fluentd, you can redeploy the pods by scaling to zero and back to the desired deployment size:

```sh
kubectl scale deployment/collection-sumologic --replicas=0
kubectl scale deployment/collection-sumologic --replicas=3
```

### Prometheus Logs

To view Prometheus logs:
Expand Down Expand Up @@ -126,8 +139,8 @@ to
Then redeploy your `fluentd` deployment:

```sh
kubectl delete deployment fluentd
kubectl apply -f /path/to/fluentd-sumologic.yaml
kubectl scale deployment/collection-sumologic --replicas=0
kubectl scale deployment/collection-sumologic --replicas=3
```

You should see data being sent to Fluentd logs, which you can get using the commands [above](#fluentd-logs).
Expand Down