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
Is it possible to have supervisord's log in the same format?
I gather and parse docker(kubernetes) logs using fluentd. This is my config:
<source>
type tail
path /var/log/containers/*.log
pos_file /var/log/fluentd-containers.log.pos
time_format %Y-%m-%dT%H:%M:%S.%NZ
tag kubernetes.*
format json
read_from_head true
</source>
<filter kubernetes.**>
@type parser
format /^(?<name>[^ ]*) (?<stream>[^ ]*) [^ ]* (?<log>.*)$/
key_name log
reserve_data true
inject_key_prefix kubernetes.app.
</filter>
As a result I see this in kibana:
"log": "mongos_jetlore stdout | 2017-07-07T12:46:54.424+0000 I SHARDING [Balancer] distributed lock with ts: 595f82be07b9697e6caf0af3' unlocked.\n",
"stream": "stdout",
"kubernetes.app.name": "mongos_jetlore",
"kubernetes.app.stream": "stdout",
"kubernetes.app.log": "2017-07-07T12:46:54.424+0000 I SHARDING [Balancer] distributed lock with ts: 595f82be07b9697e6caf0af3' unlocked.",
"docker": {
"container_id": "4fb5b6422d57385d1f9cf26ddec83b71f2fe4cc2452af2240af75938ace98158"
},
But also I see entries:
"stream": "stdout",
"kubernetes.app.name": "2017-07-07",
"kubernetes.app.stream": "11:41:06,240",
"kubernetes.app.log": "success: goofys entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)",
This happens because supervisor-stdout doesn't append supervisord's out. It appends log only for programs controlled by supervisord.
I tried to use this config:
Is it possible to have supervisord's log in the same format?
I gather and parse docker(kubernetes) logs using fluentd. This is my config:
As a result I see this in kibana:
But also I see entries:
This happens because supervisor-stdout doesn't append supervisord's out. It appends log only for programs controlled by supervisord.
I tried to use this config:
But this doesn't work.
The text was updated successfully, but these errors were encountered: