2022/04/10 03:03:49.958726 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/04/10 03:03:49.958783 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/10 03:03:49.958874 logstash.go:90: INFO Max Retries set to: 3
2022/04/10 03:03:49.958907 metrics.go:23: INFO Metrics logging every 30s
2022/04/10 03:03:49.959013 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/10 03:03:49.959140 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-lp4wv
2022/04/10 03:03:49.959369 async.go:63: INFO Flush Interval set to: 1s
2022/04/10 03:03:49.959388 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/10 03:03:49.960137 beat.go:221: INFO filebeat start running.
2022/04/10 03:03:49.960251 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/10 03:03:49.964101 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/10 03:03:49.964182 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/10 03:03:49.964225 crawler.go:38: INFO Loading Prospectors: 1
2022/04/10 03:03:49.964469 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/10 03:03:49.964654 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/10 03:03:49.964732 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/10 03:03:49.964765 registrar.go:236: INFO Starting Registrar
2022/04/10 03:03:49.964869 sync.go:41: INFO Start sending events to output
2022/04/10 03:03:49.964933 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/10 03:03:49.966105 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/10 03:03:49.966260 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/10 03:03:49.966401 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/10 03:03:49.966452 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/10 03:03:49.966495 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/10 03:03:54.985730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:03:54.985765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:03:55.990593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:03:55.990630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:03:57.994192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:03:57.994352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:02.001727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:02.001774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:10.011039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:10.011128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:19.959382 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=356 registrar.writes=1
2022/04/10 03:04:26.043709 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:26.043760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:49.959298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:04:58.063929 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:04:58.063965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:05:19.960363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:05:49.959194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:05:58.089465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:05:58.089503 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:06:19.959512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:06:49.959295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:06:58.110262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:06:58.110335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:07:19.959216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:07:49.959283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:07:58.148619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:07:58.148665 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:08:19.959284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:08:49.959290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:08:54.981211 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/10 03:08:54.981248 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/10 03:08:54.981332 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/10 03:08:54.981283 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/10 03:08:54.981281 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/10 03:08:58.166983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:08:58.167010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:09:19.961759 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=5 filebeat.harvester.open_files=-5 filebeat.harvester.running=-5
2022/04/10 03:09:49.959266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:09:58.184816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:09:58.184857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:10:19.959201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:10:49.959226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:10:58.203851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:10:58.203993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:11:19.959211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:11:49.959248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:11:58.221813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:11:58.221854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:12:19.959241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:12:49.959550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:12:58.242117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:12:58.242177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:13:19.959252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:13:49.959220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:13:58.261711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:13:58.261758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:14:19.959289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:14:49.959741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:14:58.288405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:14:58.288453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:15:19.959232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:15:49.959279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:15:58.306801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:15:58.306842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:16:19.959218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:16:49.959676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:16:58.334968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:16:58.335015 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:17:19.959246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:17:49.959472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:17:58.355322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:17:58.355374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:18:19.959366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:18:49.959451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:18:58.383338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:18:58.383370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:19:19.959250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:19:49.959271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:19:58.411374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:19:58.411476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:20:19.959352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:20:49.959565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:20:58.434598 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:20:58.434634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:21:19.959276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:21:49.959218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:21:58.453568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:21:58.453608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:22:19.961324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:22:49.959407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:22:58.470495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:22:58.470535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:23:19.959207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:23:49.959287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:23:58.489415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:23:58.489451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:24:19.959457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:24:49.959343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:24:58.507260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:24:58.507309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:25:19.959267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:25:49.959247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:25:58.526508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:25:58.526558 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:26:19.959275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:26:49.959298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:26:58.544293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:26:58.544323 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:27:19.959241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:27:49.959276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:27:58.562494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:27:58.562529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:28:19.959291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:28:49.959230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:28:58.600742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:28:58.600791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:29:19.959314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:29:49.959219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:29:58.619766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:29:58.619808 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:30:19.959324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:30:49.959295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:30:58.637621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:30:58.637669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:31:19.959285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:31:49.959260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:31:58.656323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:31:58.656378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:32:19.959294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:32:49.959452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:32:58.677289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:32:58.677326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:33:19.959350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:33:49.959309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:33:58.696889 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:33:58.696935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:34:19.959292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:34:49.959295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:35:00.716571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:35:00.716629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:35:19.959258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:35:49.959310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:36:00.735122 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:36:00.735158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:36:19.959251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:36:49.959314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:37:00.754649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:37:00.754861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:37:19.959229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:37:49.959282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:38:00.773145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:38:00.773230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:38:19.959266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:38:49.959258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:39:00.794094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:39:00.794192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:39:19.959348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:39:49.959226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:40:00.812786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:40:00.812851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:40:19.959259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:40:49.959698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:41:00.837188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:41:00.837232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:41:19.959340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:41:49.959256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:42:00.863072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:42:00.863148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:42:19.959366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:42:49.959289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:43:00.882353 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:43:00.882397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:43:19.959267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:43:49.959332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:44:00.901275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:44:00.901418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:44:19.959340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:44:49.959335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:45:00.925055 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:45:00.925117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:45:19.959222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:45:49.959346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:46:00.944199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:46:00.944352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:46:19.960850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:46:49.959252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:47:00.962005 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:47:00.962057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:47:19.959317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:47:49.959250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:48:00.982145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:48:00.982188 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:48:19.959618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:48:49.959332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:49:01.001542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:49:01.001618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:49:19.959452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:49:49.959238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:50:01.020832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:50:01.020876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:50:19.959324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:50:49.959373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:51:01.040220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:51:01.040266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:51:19.959632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:51:49.959284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:52:01.059698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:52:01.059735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:52:19.959372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:52:49.959258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:53:01.078380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:53:01.078607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:53:19.959292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:53:49.959312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:54:01.098669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:54:01.098744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:54:19.959249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:54:49.959271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:55:01.116741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:55:01.116792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:55:19.959197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:55:49.959253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:56:01.136020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:56:01.136197 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:56:19.959154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:56:49.963208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:57:01.156656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:57:01.156702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:57:19.959290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:57:49.959729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:58:01.174838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:58:01.174890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:58:19.959504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:58:49.959263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:59:01.197033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:59:01.197072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 03:59:19.959313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 03:59:49.959227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:00:01.217092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:00:01.217147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:00:19.959320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:00:49.959252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:01:01.237537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:01:01.237580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:01:19.959851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:01:49.959436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:02:01.262428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:02:01.262494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:02:19.959274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:02:49.959306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:03:01.282371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:03:01.282436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:03:19.959326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:03:49.959272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:04:01.304074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:04:01.304130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:04:19.961598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:04:49.959385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:05:01.330365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:05:01.330412 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:05:19.959277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:05:49.959512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:06:01.348420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:06:01.348509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:06:19.961805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:06:49.959227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:07:01.366843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:07:01.366888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:07:19.959349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:07:49.959250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:08:01.386960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:08:01.387142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:08:19.959279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:08:49.959548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:09:01.405800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:09:01.405853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:09:19.959316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:09:49.959248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:10:01.425590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:10:01.425637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:10:19.959326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:10:49.959264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:11:01.445320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:11:01.445370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:11:19.959344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:11:49.959252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:12:01.464398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:12:01.464442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:12:19.959263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:12:49.959249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:13:01.483276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:13:01.483322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:13:19.959276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:13:49.959294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:14:01.501497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:14:01.501559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:14:19.959411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:14:49.959252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:15:01.520519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:15:01.520562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:15:19.959323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:15:49.959371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:16:01.538823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:16:01.538868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:16:19.959363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:16:49.959334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:17:01.557840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:17:01.557884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:17:19.959355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:17:49.959416 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:18:01.577660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:18:01.577713 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:18:19.961693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:18:49.959252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:19:01.595988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:19:01.596040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:19:19.959308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:19:49.959231 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:20:01.616524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:20:01.616564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:20:19.959230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:20:49.959323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:21:01.641212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:21:01.641344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:21:19.959387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:21:49.959255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:22:01.659785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:22:01.659890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:22:19.959254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:22:49.959575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:23:01.682877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:23:01.682972 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:23:19.959530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:23:49.959241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:24:01.701151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:24:01.701193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:24:19.959154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:24:49.959273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:25:01.725616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:25:01.725673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:25:19.959408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:25:49.959291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:26:01.744574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:26:01.744622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:26:19.959214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:26:49.959249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:27:01.764233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:27:01.764286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:27:19.959253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:27:49.959335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:28:01.784683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:28:01.784737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:28:19.959404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:28:49.959400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:29:01.805820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:29:01.805880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:29:19.959269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:29:49.959207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:30:01.826162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:30:01.826418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:30:19.959419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:30:49.959633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:31:01.845009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:31:01.845283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:31:19.959460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:31:49.959286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:32:01.869167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:32:01.869218 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:32:19.959286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:32:49.959239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:33:01.886384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:33:01.886437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:33:19.959204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:33:49.959313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:34:01.912559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:34:01.912667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:34:19.959222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:34:49.959311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:35:01.949710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:35:01.949781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:35:19.959280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:35:49.959212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:36:01.978003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:36:01.978043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:36:19.959325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:36:49.959298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:37:01.996983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:37:01.997027 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:37:19.959289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:37:49.959244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:38:02.019580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:38:02.019641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:38:19.959360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:38:49.959477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:39:02.040507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:39:02.040557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:39:19.959452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:39:49.959286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:40:02.060543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:40:02.060599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:40:19.959375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:40:49.959319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:41:02.080962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:41:02.081004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:41:19.959348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:41:49.959384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:42:02.099237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:42:02.099319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:42:19.959300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:42:49.959273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:43:02.123887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:43:02.123943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:43:19.959335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:43:49.959226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:44:02.143079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:44:02.143164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:44:19.959281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:44:49.959309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:45:02.170781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:45:02.170832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:45:19.959271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:45:49.959285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:46:02.194078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:46:02.194128 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:46:19.959324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:46:49.959256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:47:02.213934 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:47:02.213988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:47:19.959257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:47:49.959342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:48:02.238717 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:48:02.238777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:48:19.959387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:48:49.959272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:49:02.259149 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:49:02.259204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:49:19.961747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:49:49.959308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:50:02.279539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:50:02.279585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:50:19.959253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:50:49.959268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/10 04:51:02.299568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/10 04:51:02.299631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host