By type
2022/01/11 03:51:11.200137 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 03:51:11.200167 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/11 03:51:11.200239 logstash.go:90: INFO Max Retries set to: 3
2022/01/11 03:51:11.200334 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/11 03:51:11.200431 metrics.go:23: INFO Metrics logging every 30s
2022/01/11 03:51:11.200481 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-nxhcg
2022/01/11 03:51:11.200630 async.go:63: INFO Flush Interval set to: 1s
2022/01/11 03:51:11.200653 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/11 03:51:11.200952 beat.go:221: INFO filebeat start running.
2022/01/11 03:51:11.201013 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/11 03:51:11.208856 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/11 03:51:11.208925 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/11 03:51:11.208992 crawler.go:38: INFO Loading Prospectors: 1
2022/01/11 03:51:11.209020 registrar.go:236: INFO Starting Registrar
2022/01/11 03:51:11.209047 sync.go:41: INFO Start sending events to output
2022/01/11 03:51:11.209125 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/11 03:51:11.209155 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/11 03:51:11.209200 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/01/11 03:51:11.209209 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/11 03:51:11.209818 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/11 03:51:11.209975 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/11 03:51:11.210213 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/11 03:51:11.210305 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/11 03:51:11.210425 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/11 03:51:11.242980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:11.243008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:12.246088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:12.246138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:14.249069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:14.249109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:18.255178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:18.255211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:26.269144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:26.269173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:41.200840 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=2043 registrar.writes=1
2022/01/11 03:51:42.275555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:51:42.275585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:52:11.200810 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:52:14.282639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:52:14.282664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:52:41.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:53:11.200743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:53:14.288833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:53:14.288885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:53:41.200778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:54:11.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:54:14.294513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:54:14.294554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:54:41.200707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:55:11.200683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:55:14.300979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:55:14.301014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:55:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:56:11.200816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:56:14.306947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:56:14.306973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:56:16.217109 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/11 03:56:41.200726 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/11 03:57:11.200763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:57:14.313823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:57:14.313872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:57:41.200740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:58:11.200720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:58:14.321672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:58:14.321696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:58:41.201450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:59:11.200732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 03:59:14.328848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:59:14.328882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 03:59:41.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:00:11.200698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:00:14.336790 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:00:14.336834 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:00:41.200684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:01:11.200867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:01:14.344335 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:01:14.344365 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:01:41.200706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:02:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:02:14.350537 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:14.350576 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:41.200744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:03:11.200876 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:03:14.357826 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:14.357866 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:41.200754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:04:11.200685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:04:14.365500 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:14.365531 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:41.200750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:05:11.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:05:14.373365 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:14.373397 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:41.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:06:11.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:06:14.380373 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:14.380413 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:41.200752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:07:11.200741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:07:14.388954 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:14.388999 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:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:08:11.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:08:14.394714 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:14.394763 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:41.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:09:11.200765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:09:14.405938 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:14.405965 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:41.200750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:10:11.200727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:10:14.415567 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:14.415596 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:41.200702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:11:11.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:11:14.423200 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:14.423232 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:41.200764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:12:11.200729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:12:14.429247 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:14.429289 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:41.200799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:13:11.200766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:13:14.437364 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:14.437394 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:41.200742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:14:11.200679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:14:14.443773 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:14.443810 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:41.200805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:15:11.200738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:15:14.451729 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:14.451788 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:41.200791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:16:11.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:16:14.463388 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:14.463414 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:41.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:17:11.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:17:14.472811 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:14.472853 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:41.200709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:18:11.200711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:18:14.479755 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:14.479783 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:41.200699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:19:11.200703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:19:14.487645 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:14.487675 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:41.200758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:20:11.200780 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:20:14.493745 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:14.493778 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:41.200891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:21:11.200744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:21:14.504132 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:14.504165 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:41.200745 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:22:11.200779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:22:14.510585 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:14.510631 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:41.200783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:23:11.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:23:14.520876 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:14.520902 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:41.200678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:24:11.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:24:14.527030 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:14.527061 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:41.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:25:11.200724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:25:14.534503 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:14.534529 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:41.200871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:26:11.200742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:26:14.541723 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:14.541751 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:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:27:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:27:14.548440 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:14.548472 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:41.200742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:28:11.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:28:14.554952 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:14.554985 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:41.200763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:29:11.200893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:29:14.563562 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:14.563589 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:41.200683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:30:11.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:30:14.570190 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:14.570235 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:41.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:31:11.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:31:14.578506 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:14.578535 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:41.200730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:32:11.200768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:32:14.585865 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:14.585921 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:41.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:33:11.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:33:14.595363 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:14.595396 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:41.200677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:34:11.200723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:34:14.601787 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:14.601815 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:41.200669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:35:11.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:35:14.613566 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:14.613605 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:41.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:36:11.200692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:36:14.619690 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:14.619714 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:41.200720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:37:11.200703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:37:14.625985 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:14.626019 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:41.200729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:38:11.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:38:14.632957 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:14.632994 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:41.200747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:39:11.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:39:14.642264 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:14.642296 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:41.200856 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:40:11.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:40:14.648744 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:14.648773 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:41.200773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:41:11.200739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:41:14.657531 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:14.657562 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:41.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:42:11.200751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:42:14.664482 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:14.664511 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:41.200738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:43:11.200769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:43:14.672030 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:14.672092 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:41.200753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:44:11.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:44:14.679456 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:14.679486 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:41.200720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:45:11.200737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:45:14.686756 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:14.686787 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:41.200732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:46:11.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:46:14.692684 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:14.692726 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:41.200701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:47:11.200739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:47:14.700162 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:14.700190 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:41.200755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:48:11.200783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:48:14.707424 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:14.707465 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:41.200812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:49:11.200694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:49:14.717079 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:14.717111 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:41.200774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:50:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:50:14.723315 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:14.723360 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:41.200772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:51:11.200766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:51:14.731271 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:14.731300 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:41.200687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:52:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:52:14.737587 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:14.737631 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:41.200747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:53:11.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:53:14.744809 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:14.744840 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:41.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:54:11.200817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:54:14.750605 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:14.750643 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:41.200756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:55:11.200911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:55:14.760934 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:14.760963 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:41.200743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:56:11.200691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:56:14.767014 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:14.767042 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:41.200760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:57:11.200738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:57:14.776628 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:14.776663 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:41.200691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:58:11.200755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:58:14.782887 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:14.782928 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:41.200670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:59:11.200715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 04:59:14.792206 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:14.792233 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:41.200703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:00:11.200741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:00:14.798505 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:14.798530 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:41.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:01:11.200684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:01:14.807624 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:14.807658 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:41.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:02:11.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:02:14.814671 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:14.814713 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:41.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:03:11.200693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:03:14.825185 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:14.825210 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:41.200772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:04:11.200696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:04:14.832829 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:14.832864 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:41.200678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:05:11.200690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:05:14.841736 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:14.841963 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:41.200693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:06:11.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:06:14.848486 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:14.848526 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:41.200749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:07:11.200754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:07:14.856834 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:14.856860 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:41.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:08:11.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:08:14.862881 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:14.862915 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:41.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:09:11.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:09:14.872826 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:14.872857 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:41.200840 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:10:11.200749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:10:14.879532 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:14.879561 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:41.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:11:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:11:14.889700 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:14.889734 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:41.200729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:12:11.200715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:12:14.895765 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:14.895796 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:41.200709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:13:11.200741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:13:14.903591 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:14.903621 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:41.200742 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:14:11.200819 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:14:14.911287 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:14.911332 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:41.200816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:15:11.200736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:15:14.919656 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:14.919687 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:41.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:16:11.200737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:16:14.926810 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:14.926921 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:41.200702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:17:11.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:17:14.935791 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:14.935816 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:41.200709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:18:11.200736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:18:14.942055 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:14.942098 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:41.200734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:19:11.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:19:14.951725 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:14.951753 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:41.200768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:20:11.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:20:14.957542 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:14.957572 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:41.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:21:11.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:21:14.966531 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:14.966562 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:41.200729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:22:11.200702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:22:14.973076 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:14.973120 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:41.200715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:23:11.200764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:23:14.980558 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:14.980587 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:41.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:24:11.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:24:14.986910 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:14.986940 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:41.200702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:25:11.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:25:14.993939 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:14.993981 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:41.200735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:26:11.200699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:26:15.000603 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:15.000641 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:41.200752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:27:11.200720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:27:15.012244 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:15.012286 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:41.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:28:11.200698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:28:15.018582 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:15.018612 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:41.200703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:29:11.200694 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:29:15.026557 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:15.026587 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:41.200707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:30:11.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:30:15.033132 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:15.033163 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:41.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:31:11.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:31:15.041824 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:15.041848 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:41.200691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:32:11.200752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:32:15.048273 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:15.048303 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:41.200679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:33:11.200741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:33:15.125792 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:15.125838 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:41.200686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:34:11.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:34:15.132403 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:15.132428 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:41.200748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:35:11.200754 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:35:15.144363 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:15.144394 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:41.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:36:11.200711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:36:15.150546 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:15.150579 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:41.200734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:37:11.201077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:37:15.157861 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:15.157891 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:41.200688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:38:11.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:38:15.164610 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:15.164639 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:41.200737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:39:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:39:15.174495 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:15.174528 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:41.200739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:40:11.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:40:15.181300 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:15.181335 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:41.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:41:11.200688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:41:15.191793 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:15.191819 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:41.200686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:42:11.200683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:42:15.199045 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:15.199073 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:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:43:11.200713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:43:15.208350 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:15.208379 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:41.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:44:11.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:44:15.215286 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:15.215319 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:41.200776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:45:11.200702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:45:15.222884 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:45:15.222914 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:45:41.200701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:46:11.200732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:46:15.229256 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:46:15.229290 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:46:41.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:47:11.200661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:47:15.236611 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:47:15.236654 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:47:41.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:48:11.200706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:48:15.243057 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:48:15.243094 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:48:41.200719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:49:11.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:49:15.252709 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:49:15.252742 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:49:41.200768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:50:11.200671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:50:15.259323 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:50:15.259355 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:50:41.200724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:51:11.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:51:15.272050 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:51:15.272074 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:51:41.200690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:52:11.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:52:15.278894 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:52:15.278929 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:52:41.200808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:53:11.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:53:15.287592 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:53:15.287619 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:53:41.200769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:54:11.200753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:54:15.296099 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:54:15.296135 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:54:41.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:55:11.200736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:55:15.304592 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:55:15.304633 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:55:41.200715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:56:11.200781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:56:15.320959 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:56:15.320989 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:56:41.200712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:57:11.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:57:15.331184 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:57:15.331215 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:57:41.200712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:58:11.200808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:58:15.337784 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:58:15.337813 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:58:41.200724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:59:11.200729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 05:59:15.346283 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:59:15.346306 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:59:41.200724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:00:11.200684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:00:15.353633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:00:15.353667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:00:41.200737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:01:11.200736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:01:15.360574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:01:15.360598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:01:41.200695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:02:11.200744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:02:15.363793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:02:15.363828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:02:41.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:03:11.200703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:03:15.372146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:03:15.372175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:03:41.200749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:04:11.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:04:15.379222 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:04:15.379262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:04:41.200757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:05:11.200692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:05:15.387177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:05:15.387206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:05:41.200727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:06:11.200744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:06:15.394640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:06:15.394671 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:06:41.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:07:11.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:07:15.405007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:07:15.405032 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:07:41.200715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:08:11.200720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:08:15.413686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:08:15.413717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:08:41.200675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:09:11.200801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:09:15.421734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:09:15.421759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:09:41.200732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:10:11.200734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:10:15.428102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:10:15.428144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:10:41.200767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:11:11.200704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:11:15.436989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:11:15.437014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:11:41.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:12:11.200734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:12:15.445096 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:12:15.445122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:12:41.200759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:13:11.200772 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:13:15.454001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:13:15.454028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:13:41.200746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:14:11.200761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:14:15.461371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:14:15.461403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:14:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:15:11.200687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:15:15.471583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:15:15.471617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:15:41.200736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:16:11.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:16:15.479073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:16:15.479123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:16:41.200712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:17:11.200671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:17:15.489258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:17:15.489290 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:17:41.200709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:18:11.200899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:18:15.496712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:18:15.496744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:18:41.200735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:19:11.200777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:19:15.505967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:19:15.506012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:19:41.200783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:20:11.201079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:20:15.513457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:20:15.513500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:20:41.200727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:21:11.200704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:21:15.521537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:21:15.521559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:21:41.200750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:22:11.200744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:22:15.533267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:22:15.533300 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:22:41.200747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:23:11.200699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:23:15.541114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:23:15.541145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:23:41.200715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:24:11.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:24:15.549219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:24:15.549250 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:24:41.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:25:11.200698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:25:15.560084 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:25:15.560117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:25:41.200708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:26:11.200729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:26:15.566850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:26:15.566886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:26:41.200700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:27:11.200683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:27:15.574347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:27:15.574375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:27:41.200743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:28:11.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:28:15.582025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:28:15.582053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:28:41.200769 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:29:11.200703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:29:15.591731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:29:15.591775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:29:41.200697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:30:11.200689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:30:15.602310 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:30:15.602337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:30:41.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:31:11.200677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:31:15.609788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:31:15.609819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:31:41.200731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:32:11.200720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:32:15.617347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:32:15.617380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:32:41.200712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:33:11.200761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:33:15.626253 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:33:15.626293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:33:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:34:11.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:34:15.633872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:34:15.633917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:34:41.200736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:35:11.200719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:35:15.648437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:35:15.648467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:35:41.200740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:36:11.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:36:15.655145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:36:15.655174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:36:41.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:37:11.200763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:37:15.665481 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:37:15.665525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:37:41.200764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:38:11.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:38:15.673895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:38:15.673925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:38:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:39:11.200747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:39:15.685269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:39:15.685296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:39:41.200738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:40:11.200778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:40:15.692250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:40:15.692292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:40:41.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:41:11.200747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:41:15.700340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:41:15.700368 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:41:41.200674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:42:11.200764 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:42:15.707388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:42:15.707418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:42:41.200782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:43:11.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:43:15.716109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:43:15.716151 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:43:41.200760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:44:11.200741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:44:15.722832 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:44:15.722863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:44:41.200721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:45:11.200727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:45:15.733900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:45:15.733930 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:45:41.200673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:46:11.200711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:46:15.741148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:46:15.741180 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:46:41.200681 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:47:11.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:47:15.748296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:47:15.748327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:47:41.200730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:48:11.200687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:48:15.763409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:48:15.763459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:48:41.201052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:49:11.200686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:49:15.772684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:49:15.772712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:49:41.200748 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:50:11.200673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:50:15.778338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:50:15.778371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:50:41.200737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:51:11.200730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:51:15.785815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:51:15.785849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:51:41.200732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:52:11.200730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:52:15.791854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:52:15.791881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:52:41.200732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:53:11.200773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:53:15.800643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:53:15.800676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:53:41.200726 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:54:11.200728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:54:15.813680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:54:15.813720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:54:41.200760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:55:11.200708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:55:15.824726 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:55:15.824759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:55:41.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:56:11.200705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:56:15.830940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:56:15.830970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:56:41.200735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:57:11.200725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:57:15.838196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:57:15.838230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:57:41.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:58:11.200730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:58:15.846195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:58:15.846248 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:58:41.200755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:59:11.200759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 06:59:15.854322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:59:15.854361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 06:59:41.200710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:00:11.200695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:00:15.865604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:00:15.865630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:00:41.200689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:01:11.200717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:01:15.875635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:01:15.875669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:01:41.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:02:11.200737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:02:15.882113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:02:15.882172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:02:41.200718 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:03:11.200727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:03:15.888778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:03:15.888810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:03:41.201033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:04:11.200676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:04:15.896551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:04:15.896582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:04:41.200714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:05:11.200750 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:05:15.910063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:05:15.910092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:05:41.200695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:06:11.200697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:06:15.917088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:06:15.917119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:06:41.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:07:11.200683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:07:15.927705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:07:15.927744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:07:41.200698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:08:11.200645 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:08:15.934077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:08:15.934117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:08:41.200895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:09:11.200708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:09:15.943595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:09:15.943629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:09:41.200733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:10:11.200693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:10:15.951646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:10:15.951679 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:10:41.200709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:11:11.200722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:11:15.959592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:11:15.959618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:11:41.200686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:12:11.200716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/11 07:12:15.966250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/11 07:12:15.966281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host