By type
2022/03/13 03:18:59.600744 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/13 03:18:59.600787 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/13 03:18:59.600849 logstash.go:90: INFO Max Retries set to: 3
2022/03/13 03:18:59.600879 metrics.go:23: INFO Metrics logging every 30s
2022/03/13 03:18:59.600935 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/13 03:18:59.601097 publish.go:295: INFO Publisher name: onap-vfc-vnflcm-84bd7747bf-v9nxh
2022/03/13 03:18:59.604173 async.go:63: INFO Flush Interval set to: 1s
2022/03/13 03:18:59.604191 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/13 03:18:59.604686 beat.go:221: INFO filebeat start running.
2022/03/13 03:18:59.604773 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/13 03:18:59.608502 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/13 03:18:59.608550 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/13 03:18:59.608572 crawler.go:38: INFO Loading Prospectors: 1
2022/03/13 03:18:59.608755 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/13 03:18:59.608845 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/13 03:18:59.608867 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/13 03:18:59.608878 registrar.go:236: INFO Starting Registrar
2022/03/13 03:18:59.608926 sync.go:41: INFO Start sending events to output
2022/03/13 03:18:59.608956 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/13 03:18:59.609528 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/13 03:19:29.602037 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/13 03:19:59.601356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:29.601177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:20:59.601263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:29.601266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:21:59.601303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:29.601176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:22:59.601210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:29.601355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:23:59.601287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:24:04.618699 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:24:29.601482 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/13 03:24:59.601224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:29.601206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:25:59.601287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:29.601239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:26:59.601257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:29.601646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:27:59.601687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:29.601198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:28:59.601194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:29.601217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:29:59.601258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:29.601228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:30:59.601160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:29.601439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:31:59.601425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:29.601172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:32:59.601172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:29.601233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:33:59.601198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:29.601571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:34:59.601298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:29.601157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:35:59.601358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:29.601155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:36:59.601207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:29.601228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:37:59.601246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:29.601240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:38:59.601234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:29.601302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:39:59.601230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:29.601348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:40:59.601218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:29.601210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:41:59.601236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:29.601216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:42:59.601200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:29.601260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:43:59.601247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:29.601251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:44:59.601215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:29.601203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:45:59.601390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:29.601231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:46:59.601217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:29.602996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:47:59.601271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:48:09.748531 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log
2022/03/13 03:48:14.706289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:14.706345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:15.709411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:15.709452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:17.712916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:17.713098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:21.720184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:21.720375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:29.601282 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/13 03:48:29.726995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:29.727031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:45.744341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:45.744387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:48:59.601293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:17.762078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:17.762116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:49:29.601181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:49:59.601190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:17.780484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:17.780527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:50:29.601317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:50:59.601179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:17.802576 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:17.802627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:51:29.601181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:51:59.601178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:17.822169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:17.822339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:52:29.601235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:52:59.601161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:53:14.770161 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnflcm/runtime_lcm.log. Closing because close_inactive of 5m0s reached.
2022/03/13 03:53:17.840855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:17.840893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:53:29.601210 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/13 03:53:59.601266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:17.858012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:17.858055 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:54:29.601196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:54:59.603336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:17.879893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:17.879931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:55:29.601285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:55:59.601193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:17.898893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:17.898936 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:56:29.601177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:56:59.601218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:17.916961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:17.916997 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:57:29.601213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:57:59.601288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:17.935405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:17.935461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:58:29.601324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:58:59.601230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:17.953755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:17.953885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 03:59:29.601226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 03:59:59.601212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:17.975722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:17.975758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:00:29.601236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:00:59.601205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:17.994973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:17.995009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:01:29.601206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:01:59.601202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:18.013094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:18.013147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:02:29.601159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:02:59.601165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:18.031326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:18.031366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:03:29.601199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:03:59.601290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:18.049130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:18.049162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:04:29.601191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:04:59.601172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:18.072215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:18.072268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:05:29.601296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:05:59.601177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:18.094157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:18.094189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:06:29.601225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:06:59.601364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:18.112170 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:18.112224 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:07:29.601278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:07:59.601211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:18.130033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:18.130071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:08:29.601176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:08:59.601164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:18.151034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:18.151196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:09:29.601273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:09:59.601223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:18.170186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:18.170232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:10:29.601300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:10:59.601195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:18.190902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:18.191035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:11:29.601196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:11:59.601166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:18.210133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:18.210187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:12:29.601161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:12:59.601226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:18.229929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:18.230003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:13:29.601273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:13:59.601263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:18.251943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:18.251978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:14:29.601253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:14:59.601275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:18.274362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:18.274409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:15:29.601261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:15:59.601260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:18.292088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:18.292125 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:16:29.601206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:16:59.601219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:18.314031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:18.314087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:17:29.601307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:17:59.601248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:18.332874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:18.332920 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:18:29.601168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:18:59.601267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:18.349910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:18.349950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:19:29.601210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:19:59.601203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:18.367914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:18.368104 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:20:29.601269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:20:59.601278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:18.390137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:18.390188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:21:29.601221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:21:59.601278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:18.408216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:18.408264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:22:29.601335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:22:59.601169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:18.426648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:18.426691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:23:29.601189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:23:59.601169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:18.445608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:18.445647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:24:29.601285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:24:59.601203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:18.464400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:18.464443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:25:29.601232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:25:59.601222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:18.481712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:18.481749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:26:29.601217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:26:59.601563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:18.500088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:18.500144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:27:29.601263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:27:59.601148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:18.519617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:18.519698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:28:29.601297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:28:59.601222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:18.540926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:18.540963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:29:29.601380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:29:59.601202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:18.562169 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:18.562296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:30:29.601254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:30:59.601189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:18.581964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:18.582013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:31:29.601188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:31:59.601186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:18.599582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:18.599622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:32:29.601191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:32:59.601318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:18.615790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:18.615840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:33:29.601253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:33:59.601355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:18.633395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:18.633572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:34:29.601204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:34:59.601214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:18.651229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:18.651280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:35:29.601280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:35:59.601207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:18.669885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:18.670151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:36:29.601237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:36:59.601142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/13 04:37:18.688981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/13 04:37:18.689027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host