By type
2022/03/06 03:17:11.172003 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/06 03:17:11.172101 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/06 03:17:11.172306 logstash.go:90: INFO Max Retries set to: 3
2022/03/06 03:17:11.172479 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/06 03:17:11.172684 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-pwhtl
2022/03/06 03:17:11.181056 metrics.go:23: INFO Metrics logging every 30s
2022/03/06 03:17:11.181447 async.go:63: INFO Flush Interval set to: 1s
2022/03/06 03:17:11.181471 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/06 03:17:11.182254 beat.go:221: INFO filebeat start running.
2022/03/06 03:17:11.182359 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/06 03:17:11.240572 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/06 03:17:11.240701 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/06 03:17:11.240783 crawler.go:38: INFO Loading Prospectors: 1
2022/03/06 03:17:11.242070 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/06 03:17:11.242271 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/06 03:17:11.242309 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/06 03:17:11.242335 registrar.go:236: INFO Starting Registrar
2022/03/06 03:17:11.242442 sync.go:41: INFO Start sending events to output
2022/03/06 03:17:11.242503 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/06 03:17:41.185313 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/06 03:17:41.258570 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/06 03:17:41.259425 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/06 03:17:41.259460 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/06 03:17:41.259944 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/06 03:17:41.259994 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/06 03:17:41.381300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:41.381347 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:42.393403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:42.395251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:44.449697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:44.449791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:48.530571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:48.530668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:56.621895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:17:56.621942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:18:11.187100 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=59
2022/03/06 03:18:12.685860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:18:12.685912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:18:41.181770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:18:44.771048 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:18:44.771097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:19:11.182137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:19:41.185063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:19:44.789974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:19:44.790046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:20:11.185049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:20:41.181536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:20:44.814562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:20:44.814600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:21:11.181792 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:21:41.181954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:21:44.853054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:21:44.853315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:22:11.184967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:22:41.181595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:22:44.883017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:22:44.883075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:22:46.378831 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/06 03:22:47.352754 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/06 03:22:47.352946 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/06 03:22:48.354301 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/06 03:23:11.181893 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2022/03/06 03:23:41.181724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:23:44.913319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:23:44.913366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:24:11.181621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:24:41.183333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:24:44.978239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:24:44.978284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:25:11.181672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:25:41.181591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:25:45.007533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:25:45.007576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:26:11.185065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:26:41.183520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:26:45.077056 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:26:45.077096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:27:11.181714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:27:41.183358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:27:45.094728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:27:45.094778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:28:11.181670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:28:41.186274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:28:45.165302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:28:45.165375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:29:11.197167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:29:41.181576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:29:45.183781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:29:45.183832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:30:11.185102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:30:41.190724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:30:45.283075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:30:45.283132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:31:11.181567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:31:41.181530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:31:45.323636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:31:45.323689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:32:11.182360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:32:41.183820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:32:45.358441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:32:45.358472 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:33:11.183460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:33:41.185506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:33:45.413533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:33:45.413602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:34:11.185343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:34:41.193991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:34:45.512214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:34:45.512284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:35:11.183200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:35:41.185223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:35:45.551599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:35:45.551652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:36:11.181822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:36:41.182090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:36:45.567852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:36:45.567911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:37:11.185049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:37:41.181669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:37:45.584130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:37:45.584179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:38:11.181438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:38:41.185240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:38:45.613842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:38:45.613894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:39:11.181471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:39:41.181667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:39:45.633192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:39:45.633246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:40:11.183085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:40:41.183293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:40:45.690815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:40:45.691110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:41:11.189508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:41:41.182427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:41:45.767865 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:41:45.767912 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:42:11.181502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:42:41.181623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:42:45.795853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:42:45.796387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:43:11.181483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:43:41.181501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:43:45.819191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:43:45.819254 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:44:11.181592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:44:41.181529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:44:45.870502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:44:45.870547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:45:11.188379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:45:41.181602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:45:45.902568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:45:45.902640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:46:11.181875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:46:41.181596 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:46:45.949031 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:46:45.949088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:47:11.181533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:47:41.181494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:47:45.962704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:47:45.962754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:48:11.186225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:48:41.181787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:48:45.991673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:48:45.991718 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:49:11.181565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:49:41.181545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:49:46.018104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:49:46.018154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:50:11.181612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:50:41.187176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:50:46.081354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:50:46.081402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:51:11.182069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:51:41.181500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:51:46.093927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:51:46.093996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:52:11.181753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:52:41.181975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:52:46.106035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:52:46.106088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:53:11.181677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:53:41.181917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:53:46.122041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:53:46.122115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:54:11.181538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:54:41.181649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:54:46.154577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:54:46.154645 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:55:11.181685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:55:41.183878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:55:46.183790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:55:46.183849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:56:11.181814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:56:41.182290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:56:46.213631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:56:46.213674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:57:11.183034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:57:41.187552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:57:46.251377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:57:46.251453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:58:11.181730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:58:41.181517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:58:46.282806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:58:46.284785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:59:11.181737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:59:41.181614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 03:59:46.302659 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 03:59:46.302699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:00:11.181655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:00:41.181767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:00:46.388233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:00:46.388282 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:01:11.181636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:01:41.183929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:01:46.415144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:01:46.415194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:02:11.181886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:02:41.181726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:02:46.477041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:02:46.477098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:03:11.181550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:03:41.181717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:03:46.513910 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:03:46.513962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:04:11.182182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:04:41.182470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:04:46.594134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:04:46.594211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:05:11.181670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:05:41.182723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:05:46.643034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:05:46.643118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:06:11.184958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:06:41.181925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:06:46.657753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:06:46.657832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:07:11.181496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:07:41.181908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:07:46.689237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:07:46.689297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:08:11.181500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:08:41.181593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:08:46.715863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:08:46.715929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:09:11.181458 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:09:41.181490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:09:46.754107 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:09:46.754152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:10:11.181627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:10:41.182024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:10:46.788754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:10:46.788840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:11:11.181594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:11:41.186855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:11:46.829733 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:11:46.829794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:12:11.181711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:12:41.181755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:12:46.862877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:12:46.862934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:13:11.182800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:13:41.181670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:13:46.890398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:13:46.890449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:14:11.181498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:14:41.181519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:14:46.902722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:14:46.902775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:15:11.181644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:15:41.181741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:15:46.946719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:15:46.946816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:16:11.181471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:16:41.181662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:16:46.964038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:16:46.964101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:17:11.191431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:17:41.181640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:17:47.000034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:17:47.000366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:18:11.181655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:18:41.182654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:18:47.011303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:18:47.011457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:19:11.181658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:19:41.181855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:19:47.020686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:19:47.020732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:20:11.181769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:20:41.187674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:20:47.036218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:20:47.036457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:21:11.181777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:21:41.182175 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:21:47.064238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:21:47.064298 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:22:11.182935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:22:41.181554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:22:47.077723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:22:47.077788 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:23:11.181521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:23:41.181672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:23:47.113144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:23:47.113210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:24:11.182307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:24:41.182679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:24:47.189091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:24:47.189478 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:25:11.181415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:25:41.181476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:25:47.205366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:25:47.205427 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:26:11.181763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:26:41.181790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:26:47.218979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:26:47.219048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:27:11.181801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:27:41.181999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:27:47.252759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:27:47.252858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:28:11.181850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:28:41.181619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:28:47.305080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:28:47.305131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:29:11.181888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:29:41.181508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:29:47.315460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:29:47.315506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:30:11.185660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:30:41.183140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:30:47.386118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:30:47.386176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:31:11.182189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:31:41.181573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:31:47.413112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:31:47.413148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:32:11.181590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:32:41.181546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:32:47.446903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:32:47.446952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:33:11.181651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:33:41.183246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:33:47.456448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:33:47.456516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:34:11.181843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:34:41.186976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:34:47.472585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:34:47.472636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:35:11.181469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:35:41.181729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:35:47.508196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:35:47.508231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:36:11.181558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:36:41.182400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:36:47.540900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:36:47.541267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:37:11.181547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:37:41.182609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:37:47.548998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:37:47.549036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:38:11.181650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:38:41.181574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:38:47.556553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:38:47.556597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:39:11.181827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:39:41.182062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:39:47.562334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:39:47.562383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:40:11.181541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:40:41.181504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:40:47.569433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:40:47.569500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:41:11.181406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:41:41.181842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:41:47.597297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:41:47.597346 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:42:11.181717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:42:41.181511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:42:47.604227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:42:47.604268 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:43:11.181782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:43:41.182080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:43:47.612171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:43:47.612213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:44:11.181691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:44:41.181981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:44:47.637233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:44:47.637292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:45:11.182347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:45:41.181943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:45:47.670342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:45:47.670403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:46:11.181572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:46:41.182424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:46:47.678593 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:46:47.678652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:47:11.181783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:47:41.181487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:47:47.692377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:47:47.692440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:48:11.182012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:48:41.181539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:48:47.704462 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:48:47.704524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:49:11.181585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:49:41.181518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:49:47.716235 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:49:47.716280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:50:11.181541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:50:41.181561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:50:47.747643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:50:47.747691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:51:11.185209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:51:41.181495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:51:47.759284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:51:47.759332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:52:11.181391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:52:41.182520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:52:47.771858 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:52:47.774927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:53:11.181536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:53:41.181816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:53:47.784501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:53:47.784564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:54:11.181564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:54:41.187657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:54:47.855072 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:54:47.855141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:55:11.187333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:55:41.189975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:55:47.864551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:55:47.864607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:56:11.181554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:56:41.181675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:56:47.871029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:56:47.871082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:57:11.182179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:57:41.181584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:57:47.884306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:57:47.884360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:58:11.181593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:58:41.186234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:58:47.906038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:58:47.906091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:59:11.184174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:59:41.181783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 04:59:47.974606 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 04:59:47.974683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:00:11.181628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:00:41.181626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:00:47.983267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:00:47.983439 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:01:11.191421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:01:41.185094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:01:48.083115 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:01:48.083342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:02:11.181663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:02:41.181506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:02:48.101750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:02:48.101820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:03:11.183222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:03:41.182803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:03:48.207525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:03:48.207572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:04:11.185061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:04:41.181653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/06 05:04:48.245180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:04:48.245264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/06 05:05:11.181604 metrics.go:34: INFO No non-zero metrics in the last 30s