By type
2022/01/11 04:02:27.957917 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/01/11 04:02:27.957961 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/11 04:02:27.958053 logstash.go:90: INFO Max Retries set to: 3
2022/01/11 04:02:27.958106 metrics.go:23: INFO Metrics logging every 30s
2022/01/11 04:02:27.958120 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/11 04:02:27.958337 publish.go:295: INFO Publisher name: onap-portal-sdk-856bc9b5d4-2kd9r
2022/01/11 04:02:27.958623 async.go:63: INFO Flush Interval set to: 1s
2022/01/11 04:02:27.958659 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/11 04:02:27.959373 beat.go:221: INFO filebeat start running.
2022/01/11 04:02:27.959441 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/11 04:02:28.019109 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/11 04:02:28.019207 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/11 04:02:28.019298 crawler.go:38: INFO Loading Prospectors: 1
2022/01/11 04:02:28.019332 registrar.go:236: INFO Starting Registrar
2022/01/11 04:02:28.019510 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/11 04:02:28.019491 sync.go:41: INFO Start sending events to output
2022/01/11 04:02:28.019504 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/11 04:02:28.019771 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/11 04:02:28.019816 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/11 04:02:28.020720 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/01/11 04:02:28.020840 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/01/11 04:02:28.021143 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/01/11 04:02:28.021348 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/01/11 04:02:28.021490 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/01/11 04:02:33.037352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:33.037387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:34.041260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:34.041298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:36.046559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:36.046593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:40.053933 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:40.053961 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:48.062073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:48.062105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:02:57.958511 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/01/11 04:03:04.069809 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:03:04.069856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:03:27.958586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:03:36.078575 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:03:36.078658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:03:57.958618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:04:27.958577 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:04:36.087334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:04:36.087386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:04:57.958469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:05:27.958495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:05:36.097703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:05:36.097739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:05:57.958564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:06:27.958718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:06:36.107813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:06:36.107857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:06:57.958664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:07:27.958562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:07:33.033102 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/01/11 04:07:33.033131 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/11 04:07:33.033239 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/01/11 04:07:33.033423 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/01/11 04:07:33.035479 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/01/11 04:07:36.117313 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:07:36.117369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:07:57.958564 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/01/11 04:08:27.958567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:08:36.127595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:08:36.127657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:08:57.959110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:09:27.958541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:09:36.136345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:09:36.136381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:09:57.958507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:10:27.958503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:10:36.145411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:10:36.145448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:10:57.958561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:11:27.958440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:11:36.155009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:11:36.155064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:11:57.958609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:12:27.958586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:12:36.164116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:12:36.164250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:12:57.958586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:13:27.958557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:13:36.173919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:13:36.173954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:13:57.958555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:14:27.958601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:14:36.184148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:14:36.184200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:14:57.958596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:15:27.958614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:15:36.192471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:15:36.192548 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:15:57.958642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:16:27.958529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:16:36.201413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:16:36.201451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:16:57.958549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:17:27.958535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:17:36.210480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:17:36.210512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:17:57.958518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:18:27.958544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:18:36.218307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:18:36.218348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:18:57.958611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:19:27.958503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:19:36.226881 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:19:36.226926 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:19:57.958518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:20:27.958471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:20:36.234947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:20:36.234982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:20:57.958444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:21:27.958549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:21:36.242949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:21:36.242995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:21:57.958484 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:22:27.958686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:22:36.249720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:22:36.249753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:22:57.958561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:23:27.958547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:23:36.258308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:23:36.258358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:23:57.958429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:24:27.958558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:24:36.266837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:24:36.266890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:24:57.958532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:25:27.958646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:25:36.276620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:25:36.276672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:25:57.959965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:26:27.958409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:26:36.286260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:26:36.286307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:26:57.958542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:27:27.958608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:27:36.295731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:27:36.295762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:27:57.958678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:28:27.958640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:28:36.304143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:28:36.304186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:28:57.958499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:29:27.958492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:29:36.312488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:29:36.312559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:29:57.958788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:30:27.958803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:30:36.321822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:30:36.321869 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:30:57.958528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:31:27.958591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:31:36.336464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:31:36.336501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:31:57.958611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:32:27.958699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:32:36.345289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:32:36.345368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:32:57.958565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:33:27.958541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:33:36.354830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:33:36.354876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:33:57.958494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:34:27.958627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:34:36.362869 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:34:36.362916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:34:57.958483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:35:27.958727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:35:36.372469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:35:36.372516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:35:57.958520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:36:27.958639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:36:36.382447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:36:36.382499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:36:57.958523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:37:27.958531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:37:36.391450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:37:36.391483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:37:57.958528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:38:27.958519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:38:36.400344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:38:36.400386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:38:57.958527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:39:27.958522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:39:36.408165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:39:36.408200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:39:57.958458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:40:27.958613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:40:36.417521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:40:36.417578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:40:57.958447 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:41:27.958475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:41:36.425831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:41:36.425874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:41:57.958736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:42:27.958539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:42:36.433776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:42:36.433848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:42:57.958583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:43:27.958472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:43:36.442364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:43:36.442402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:43:57.958558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:44:27.958537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:44:36.450771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:44:36.450822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:44:57.958504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:45:27.958409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:45:36.460297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:45:36.460338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:45:57.958533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:46:27.958518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:46:36.468111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:46:36.468158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:46:57.958555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:47:27.958531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:47:36.476996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:47:36.477038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:47:57.958541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:48:27.958537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:48:36.484367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:48:36.484411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:48:57.958601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:49:27.958419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:49:36.493826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:49:36.493876 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:49:57.958643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:50:27.958632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:50:36.501439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:50:36.501505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:50:57.958531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:51:27.958626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:51:36.511959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:51:36.512016 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:51:57.958559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:52:27.958557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:52:36.518836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:52:36.518871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:52:57.958552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:53:27.958619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:53:36.527157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:53:36.527203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:53:57.958531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:54:27.958558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:54:36.535151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:54:36.535210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:54:57.958837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:55:27.958609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:55:36.544553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:55:36.544605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:55:57.958553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:56:27.958554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:56:36.553344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:56:36.553396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:56:57.958558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:57:27.958541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:57:36.563271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:57:36.563320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:57:57.958418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:58:27.958475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:58:36.573921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:58:36.573993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:58:57.958413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:59:27.958451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:59:36.582468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:59:36.582502 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 04:59:57.958628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:00:27.958556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:00:36.591341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:00:36.591394 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:00:57.958533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:01:27.958540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:01:36.602057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:01:36.602111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:01:57.958499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:02:27.958699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:02:36.610204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:02:36.610240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:02:57.958679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:03:27.958492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:03:36.617976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:03:36.618013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:03:57.958584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:04:27.958479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:04:36.626445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:04:36.626483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:04:57.958477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:05:27.958604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:05:36.634360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:05:36.634416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:05:57.958596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:06:27.958443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:06:36.643462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:06:36.643521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:06:57.958421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:07:27.958528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:07:36.650669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:07:36.650698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:07:57.958534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:08:27.958631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:08:36.659821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:08:36.659854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:08:57.958595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:09:27.958782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:09:36.667828 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:09:36.667878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:09:57.958628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:10:27.958562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:10:36.676610 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:10:36.676648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:10:57.958611 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:11:27.958516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:11:36.684993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:11:36.685044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:11:57.958673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:12:27.958648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:12:36.694875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:12:36.694931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:12:57.958549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:13:27.958448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:13:36.704694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:13:36.704736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:13:57.958592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:14:27.958513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:14:36.712814 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:14:36.712843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:14:57.958468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:15:27.958445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:15:36.722244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:15:36.722321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:15:57.958860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:16:27.958546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:16:36.732229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:16:36.732265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:16:57.958505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:17:27.958493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:17:36.744142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:17:36.744201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:17:57.958528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:18:27.958658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:18:36.753799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:18:36.753837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:18:57.958530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:19:27.958524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:19:36.766402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:19:36.766464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:19:57.958486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:20:27.958469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:20:36.775762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:20:36.775815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:20:57.958552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:21:27.958553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:21:36.785946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:21:36.785994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:21:57.958583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:22:27.958593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:22:36.795120 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:22:36.795177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:22:57.958487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:23:27.958606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:23:36.804664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:23:36.804716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:23:57.958542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:24:27.958674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:24:36.814494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:24:36.814572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:24:57.958533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:25:27.958536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:25:36.823596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:25:36.823635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:25:57.958755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:26:27.958649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:26:36.833503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:26:36.833568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:26:57.958562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:27:27.958570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:27:36.842672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:27:36.842709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:27:57.958557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:28:27.958437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:28:36.850932 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:28:36.850970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:28:57.958514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:29:27.958519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:29:36.861431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:29:36.861494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:29:57.958605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:30:27.958926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:30:36.872021 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:30:36.872087 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:30:57.958499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:31:27.958533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:31:36.881006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:31:36.881086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:31:57.958403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:32:27.958462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:32:36.890083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:32:36.890130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:32:57.958670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:33:27.958563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:33:36.899338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:33:36.899401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:33:57.958600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:34:27.958518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:34:36.909454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:34:36.909601 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:34:57.958526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:35:27.958579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:35:36.917767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:35:36.917792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:35:57.958542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:36:27.958627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:36:36.924668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:36:36.924708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:36:57.958542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:37:27.958654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:37:36.934234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:37:36.934284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:37:57.958517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:38:27.958640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:38:36.944252 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:38:36.944284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:38:57.958373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:39:27.958606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:39:36.952787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:39:36.952837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:39:57.958603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:40:27.958544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:40:36.961530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:40:36.961592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:40:57.958473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:41:27.958470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:41:36.973871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:41:36.973925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:41:57.958497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:42:27.958472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:42:36.982862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:42:36.983034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:42:57.958629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:43:27.958511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:43:36.992601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:43:36.992659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:43:57.958678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:44:27.958668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:44:37.000935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:44:37.000981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 05:44:57.958602 metrics.go:34: INFO No non-zero metrics in the last 30s