You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 5, 2021. It is now read-only.
`LOG_FORMAT`|Format in which to post logs to Sumo. Allowable values:<br/><br/>`text`—Logs will appear in SumoLogic in text format.<br/>`json`—Logs will appear in SumoLogic in json format.<br/>`json_merge`—Same as json but if the container logs in json format to stdout it will merge in the container json log at the root level and remove the log field.<br/><br/>Default: `json`
105
105
`MULTILINE_START_REGEXP`|The regular expression for the `concat` plugin to use when merging multi-line messages. Defaults to Julian dates, for example, Jul 29, 2017.
106
106
`NUM_THREADS`|Set the number of HTTP threads to Sumo. It might be necessary to do so in heavy-logging clusters. <br/><br/>Default: `1`
@@ -147,10 +147,29 @@ The following table show which environment variables affect which Fluentd sourc
147
147
### FluentD stops processing logs
148
148
When dealing with large volumes of data (TB's from what we have seen), FluentD may stop processing logs, but continue to run. This issue seems to be caused by the [scalability of the inotify process](https://github.com/fluent/fluentd/issues/1630) that is packaged with the FluentD in_tail plugin. If you encounter this situation, setting the `ENABLE_STAT_WATCHER` to `false` should resolve this issue.
149
149
150
-
### Override environment variables using annotations
151
-
You can override the `LOG_FORMAT`, `KUBERNETES_META_REDUCE`, `SOURCE_CATEGORY` and `SOURCE_NAME` environment variables, per pod, using [Kubernetes annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/). For example:
150
+
### Reducing Kubernetes metadata
152
151
153
-
```
152
+
You can use the `KUBERNETES_META_REDUCE` environment variable (global) or the `sumologic.com/kubernetes_meta_reduce` annotation (per pod) to reduce the amount of Kubernetes metadata included with each log line under the `kubernetes` field.
153
+
154
+
When set, FluentD will remove the following properties:
155
+
156
+
*`pod_id`
157
+
*`container_id`
158
+
*`namespace_id`
159
+
*`master_url`
160
+
*`labels`
161
+
*`annotations`
162
+
163
+
Logs will still include:
164
+
165
+
*`pod_name`
166
+
*`container_name`
167
+
*`namespace_name`
168
+
*`host`
169
+
170
+
These fields still allow you to uniquely identify a pod and look up additional details with the Kubernetes API.
171
+
172
+
```yaml
154
173
apiVersion: v1
155
174
kind: ReplicationController
156
175
metadata:
@@ -165,10 +184,7 @@ spec:
165
184
labels:
166
185
app: mywebsite
167
186
annotations:
168
-
sumologic.com/format: "text"
169
187
sumologic.com/kubernetes_meta_reduce: "true"
170
-
sumologic.com/sourceCategory: "mywebsite/nginx"
171
-
sumologic.com/sourceName: "mywebsite_nginx"
172
188
spec:
173
189
containers:
174
190
- name: nginx
@@ -177,9 +193,10 @@ spec:
177
193
- containerPort: 80
178
194
```
179
195
180
-
### Reduce Kubernetes Metadata using annotations
181
-
You can also use the "sumologic.com/kubernetes_meta_reduce" annotation to exclude `pod_id`,
182
-
`container_id`, `namespace_id`, `namespace_name`, `master_url` and `labels` from Kubernetes Metadata.
196
+
197
+
### Override environment variables using annotations
198
+
You can override the `LOG_FORMAT`, `KUBERNETES_META_REDUCE`, `SOURCE_CATEGORY` and `SOURCE_NAME` environment variables, per pod, using [Kubernetes annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/). For example:
0 commit comments