By type
2022/03/11 03:19:20.804918 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/11 03:19:20.805015 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:19:20.805237 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:19:20.805365 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:19:20.805622 publish.go:295: INFO Publisher name: onap-vfc-vnfres-844dfc67b6-2drl5
2022/03/11 03:19:20.806020 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:19:20.806045 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:19:20.806802 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:19:20.806933 beat.go:221: INFO filebeat start running.
2022/03/11 03:19:20.807041 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:19:20.813045 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:19:20.813211 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:19:20.813453 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:19:20.813648 sync.go:41: INFO Start sending events to output
2022/03/11 03:19:20.813901 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:19:20.814026 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:19:20.814345 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/11 03:19:20.814377 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:19:20.814916 registrar.go:236: INFO Starting Registrar
2022/03/11 03:19:20.815350 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/11 03:19:50.807145 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/11 03:20:20.807185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:50.807442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:20.807258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:50.807213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:20.807118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:50.807170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:20.807198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:50.807127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:24:20.807180 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:24:25.845030 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:24:50.807134 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/11 03:25:20.807158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:50.807170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:20.807176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:50.807098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:20.807124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:50.807132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:20.807100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:50.807179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:20.807236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:50.807094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:20.807092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:50.807092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:20.807070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:50.807170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:20.807219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:50.807073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:20.807128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:50.807113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:20.807520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:50.807254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:20.807146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:50.807272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:20.807136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:50.807105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:20.807080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:50.807074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:20.807073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:50.807055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:20.807111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:50.807163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:20.807046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:50.807128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:20.807117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:50.807219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:20.807062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:50.807070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:20.807137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:50.807163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:20.807115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:50.807113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:20.807149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:50.807181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:20.807144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:50.807064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:20.807118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:50.807224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:51.010513 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log
2022/03/11 03:47:56.032562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:56.032618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:57.037282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:57.037319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:59.041176 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:47:59.041210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:03.052906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:03.052965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:11.062968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:11.063008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:20.807136 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/11 03:48:27.081969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:27.082010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:50.807090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:48:59.101332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:59.101422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:20.807095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:50.807161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:59.119460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:59.119575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:20.807156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:50.807101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:59.145869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:59.145910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:20.807100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:50.807118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:59.169816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:59.169857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:20.807084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:50.807070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:56.020201 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfres/runtime_res.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:52:59.202909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:59.203018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:20.807132 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/11 03:53:50.807158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:59.220337 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:59.220454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:20.807276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:50.807090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:59.239847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:59.239902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:20.807131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:50.807157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:59.259406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:59.259447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:20.807125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:50.807216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:59.282422 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:59.282464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:20.807121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:50.807086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:59.301420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:59.301459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:20.807061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:50.807078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:59.319658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:59.319784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:20.807119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:50.807122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:59.337384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:59.337431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:20.807049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:50.807095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:59.354591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:59.354629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:20.807097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:50.807177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:59.371828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:59.371868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:20.807203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:50.807061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:59.393483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:59.393565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:20.807094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:50.807081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:59.413421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:59.413576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:20.807066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:50.807147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:59.430546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:59.430583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:20.807126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:50.807102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:59.449767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:59.449943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:20.807066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:50.807106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:59.469278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:59.469318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:20.807083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:50.807174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:59.489086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:59.489285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:20.807148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:50.807101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:59.508036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:59.508078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:20.807114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:50.808504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:59.525752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:59.525880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:20.807092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:50.807070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:59.548563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:59.548669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:20.807133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:50.807059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:59.566185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:59.566250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:20.807219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:50.807161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:59.583582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:59.583621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:20.808410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:50.807057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:59.600643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:59.600701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:20.807077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:50.808657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:59.618866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:59.618901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:20.807046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:50.807097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:59.637551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:59.637584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:20.807198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:50.807091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:59.654918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:59.654956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:20.807885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:50.807130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:59.674001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:59.674043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:20.807107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:50.807066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:59.691360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:59.691401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:20.807139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:50.807099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:59.709362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:59.709401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:20.807144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:50.807049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:59.727834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:59.727877 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:20.807125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:50.807046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:59.746970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:59.747020 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:20.807104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:50.807096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:59.763968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:59.764002 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:20.807158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:50.807196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:59.782531 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:59.782570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:20.807134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:50.807092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:59.799460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:59.799703 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:20.807155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:50.807059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:59.817987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:59.818027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:20.807083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:50.807127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:59.839352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:59.839388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:20.807113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:50.807186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:59.861355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:59.861398 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:20.807070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:50.807076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:59.880694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:59.880744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:20.807154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:50.807085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:59.900893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:59.900933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:20.807106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:50.807113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:59.920413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:59.920452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:20.807101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:50.807040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:59.938438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:59.938477 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:20.807176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:50.807100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:59.957050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:59.957091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host