@@ -24,6 +24,7 @@ The following tables lists the configurable parameters of the lm-logs chart and
24
24
| ` global.nameOverride ` | Global storage class for dynamic provisioning | ` "" ` |
25
25
| ` global.fullnameOverride ` | Global storage class for dynamic provisioning | ` "" ` |
26
26
| ` global.lm_company_name ` | LogicMonitor account name | ` nil ` |
27
+ | ` global.lm_company_domain ` | LogicMonitor company domain name | ` logicmonitor.com ` |
27
28
| ` global.lm_access_id ` | LogicMonitor API Token Access ID | ` nil ` |
28
29
| ` global.lm_access_key ` | LogicMonitor API Token Access Key | ` nil ` |
29
30
| ` image.repository ` | Container image repository | ` logicmonitor/lm-logs-k8s-fluentd ` |
@@ -34,6 +35,7 @@ The following tables lists the configurable parameters of the lm-logs chart and
34
35
| ` resources.requests.memory ` | Container memory resource requests | ` 700Mi ` |
35
36
| ` fluent.device_less_logs ` | beta feature. when set true, do not send resource information. send ` service ` and ` namespace ` as metadata when true | ` false ` |
36
37
| ` fluent.include_metadata ` | if true send all metadata along with log msg | ` true ` |
38
+ | ` fluent.resource_type ` | If specified, the value will be statically applied to all ingested logs. | ` "" ` |
37
39
| ` fluent.buffer.memory ` | fluentd's buffer memory plugin config | ` flush_interval 1s,chunk_limit_size 8m,flush_thread_count 8 ` |
38
40
| ` tolerations ` | Tolerations for pod assignment | ` {} ` (evaluated as a template) |
39
41
| ` nodeSelectors ` | Node labels for pod assignment | ` {} ` (evaluated as a template) |
@@ -44,7 +46,7 @@ The following tables lists the configurable parameters of the lm-logs chart and
44
46
| ` kubernetes.multiline_concat_key ` | Key to look for fluentD to concatenate multiline logs | ` "log" ` |
45
47
46
48
47
- ### Avaialble Environment variables
49
+ ### Available Environment variables
48
50
For descriptions see: https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter
49
51
50
52
* FLUENT_LOG_LEVEL
@@ -70,24 +72,24 @@ When `fluent.device_less_logs=true`
70
72
Anomaly detection will be done on ` namespace ` and ` service `
71
73
- namespace will be k8s namespace
72
74
- service will be extracted from metadata for yaml in the following priority.
73
- - kubernetets .labels.app ( deployments )
74
- - kubernetets .labels.app_kubernetes_io/name (daemon sets)
75
- - kubernetets .container_name
76
- - kubernetets .pod_name
75
+ - kubernetes .labels.app ( deployments )
76
+ - kubernetes .labels.app_kubernetes_io/name (daemon sets)
77
+ - kubernetes .container_name
78
+ - kubernetes .pod_name
77
79
78
80
#### Multiline log support for k8s lm logs
79
81
To use regexp to match beginning of multiline set ` kubernetes.multiline_start_regexp=<some-regex-pattern> `
80
82
by default the regex is set to ` /^\[(\d{4}-)?\d{2}-\d{2} \d{2}:\d{2}:\d{2}.\d{3}.*\]/ `
81
83
82
84
### Logs appearing in cri format
83
- If conatiner runtime is containerD or cri-o, on lm-logs ui you might see logs with prefix eg.
85
+ If container runtime is containerD or cri-o, on lm-logs ui you might see logs with prefix eg.
84
86
```
85
87
2016-10-06T00:17:09.669794202Z stdout F The content of the log entry 1
86
88
```
87
89
To solve this we need to install lm-logs with following command :
88
90
```
89
91
helm upgrade --install -n <namespace> \
90
- --set lm_company_name="<comapny >" \
92
+ --set lm_company_name="<company >" \
91
93
--set lm_access_id="<access_id>" \
92
94
--set lm_access_key="<access_key"> \
93
95
--set env.FLUENT_CONTAINER_TAIL_PARSER_TYPE="cri" \
0 commit comments