Filebeat BeatUUID repeat

it is weird ,i run two contanier on diff server . when i see the log i find BeatUUID repeat
one log

2018-05-03T07:39:13.980Z	INFO	[monitoring]	log/log.go:133	Uptime: 16m47.756701522s
2018-05-03T07:39:13.980Z	INFO	[monitoring]	log/log.go:110	Stopping metrics logging.
2018-05-03T07:39:15.315Z	INFO	instance/beat.go:468	Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2018-05-03T07:39:15.315Z	INFO	instance/beat.go:475	Beat UUID: 288767ee-faa1-4668-aab7-dd192ea68330
2018-05-03T07:39:15.315Z	INFO	instance/beat.go:213	Setup Beat: filebeat; Version: 6.2.3
2018-05-03T07:39:15.317Z	INFO	pipeline/module.go:76	Beat name: e822d59df0be

another log

|2018-05-03T07:43:19.779Z|INFO|instance/beat.go:468|Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]|
|---|---|---|---|
|2018-05-03T07:43:19.779Z|INFO|instance/beat.go:475|Beat UUID: 288767ee-faa1-4668-aab7-dd192ea68330|
|2018-05-03T07:43:19.779Z|INFO|instance/beat.go:213|Setup Beat: filebeat; Version: 6.2.3|
|2018-05-03T07:43:19.780Z|INFO|pipeline/module.go:76|Beat name: 932b97e51f90|

my mistake i copy a meta.json
detail

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.