By type
2022/03/18 03:20:54.094499 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/18 03:20:54.094615 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/18 03:20:54.094782 logstash.go:90: INFO Max Retries set to: 3
2022/03/18 03:20:54.095007 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/18 03:20:54.095227 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-5mqtc
2022/03/18 03:20:54.095619 metrics.go:23: INFO Metrics logging every 30s
2022/03/18 03:20:54.095990 async.go:63: INFO Flush Interval set to: 1s
2022/03/18 03:20:54.096035 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/18 03:20:54.096995 beat.go:221: INFO filebeat start running.
2022/03/18 03:20:54.097135 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/18 03:20:54.103176 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/18 03:20:54.103287 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/18 03:20:54.103382 crawler.go:38: INFO Loading Prospectors: 1
2022/03/18 03:20:54.103532 registrar.go:236: INFO Starting Registrar
2022/03/18 03:20:54.103664 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/18 03:20:54.103687 sync.go:41: INFO Start sending events to output
2022/03/18 03:20:54.103740 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/18 03:20:54.103849 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/18 03:20:54.103905 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/18 03:21:14.113042 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/18 03:21:14.113565 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/18 03:21:14.113669 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/18 03:21:14.113687 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/18 03:21:14.113702 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/18 03:21:19.137543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:19.137638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:20.141441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:20.141495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:22.145409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:22.145452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:24.096346 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=64 registrar.writes=1
2022/03/18 03:21:26.159209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:26.159359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:34.178743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:34.178782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:50.207370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:50.207454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:21:54.096112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:22:22.230230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:22:22.230302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:22:24.096038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:22:54.096120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:23:22.259151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:23:22.259226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:23:24.096299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:23:54.096072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:24:22.308465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:24:22.308516 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:24:24.096143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:24:54.096163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:25:22.356154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:25:22.356212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:25:24.103100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:25:54.095940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:26:19.143468 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/18 03:26:22.152231 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/18 03:26:22.152255 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/18 03:26:22.152262 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/18 03:26:22.410614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:26:22.410658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:26:24.096132 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/18 03:26:39.161563 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/18 03:26:54.096332 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/18 03:27:22.442079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:27:22.442162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:27:24.096146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:27:54.096159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:28:22.469518 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:28:22.469575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:28:24.096584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:28:54.097727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:29:22.523491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:29:22.523564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:29:24.110767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:29:54.096052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:30:22.542911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:30:22.542973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:30:24.096179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:30:54.095948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:31:22.569632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:31:22.569796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:31:24.098069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:31:54.096152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:32:22.592064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:32:22.592331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:32:24.096191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:32:54.096018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:33:22.622148 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:33:22.622396 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:33:24.096088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:33:54.096082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:34:22.667871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:34:22.667928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:34:24.095980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:34:54.097613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:35:22.695735 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:35:22.695782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:35:24.096005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:35:54.096313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:36:22.747000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:36:22.747059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:36:24.095988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:36:54.096237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:37:22.772803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:37:22.772864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:37:24.095920 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:37:54.095983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:38:22.799855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:38:22.799934 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:38:24.095926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:38:54.096023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:39:22.831712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:39:22.831902 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:39:24.101174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:39:54.095967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:40:22.910073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:40:22.910122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:40:24.096119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:40:54.095998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:41:22.932979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:41:22.933022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:41:24.095943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:41:54.096384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:42:22.955812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:42:22.955870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:42:24.096063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:42:54.096073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:43:22.980093 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:43:22.980289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:43:24.095975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:43:54.095942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:44:23.031041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:44:23.031083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:44:24.096039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:44:54.096005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:45:23.053527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:45:23.053570 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:45:24.096107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:45:54.095977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:46:23.140558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:46:23.141005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:46:24.096516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:46:54.096181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:47:23.170962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:47:23.171010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:47:24.096037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:47:54.096658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:48:23.213880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:48:23.213942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:48:24.095952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:48:54.096051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:49:23.235649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:49:23.235689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:49:24.096040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:49:54.096133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:50:23.267837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:50:23.267894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:50:24.099563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:50:54.095929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:51:23.309523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:51:23.309673 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:51:24.096124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:51:54.095958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:52:23.334758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:52:23.334804 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:52:24.096007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:52:54.095906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:53:23.361787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:53:23.361855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:53:24.095907 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:53:54.095994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:54:23.384136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:54:23.384232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:54:24.096182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:54:54.096019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:55:23.412936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:55:23.413392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:55:24.095961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:55:54.096235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:56:23.435975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:56:23.436045 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:56:24.096150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:56:54.096084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:57:23.464363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:57:23.464413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:57:24.097843 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:57:54.096058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:58:23.489577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:58:23.489639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:58:24.095992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:58:54.096027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:59:23.512427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:59:23.512494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 03:59:24.096106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 03:59:54.095993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:00:23.536358 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:00:23.536574 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:00:24.098102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:00:54.095985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:01:23.558731 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:01:23.558814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:01:24.096050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:01:54.096151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:02:23.581960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:02:23.582018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:02:24.096031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:02:54.095985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:03:23.612721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:03:23.612782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:03:24.099919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:03:54.095997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:04:23.636155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:04:23.636204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:04:24.096034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:04:54.096017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:05:23.669415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:05:23.669586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:05:24.095925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:05:54.096273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:06:23.695377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:06:23.695442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:06:24.096126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:06:54.096079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:07:23.718274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:07:23.718319 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:07:24.095937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:07:54.095904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:08:23.751711 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:08:23.751765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:08:24.095988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:08:54.096032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:09:23.775511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:09:23.776167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:09:24.096118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:09:54.095991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:10:23.795161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:10:23.795207 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:10:24.096000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:10:54.095997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:11:23.820719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:11:23.820778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:11:24.095950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:11:54.096176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:12:23.853867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:12:23.853932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:12:24.096083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:12:54.095986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:13:23.892901 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:13:23.892962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:13:24.096085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:13:54.096094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:14:23.917098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:14:23.917189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:14:24.096055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:14:54.096100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:15:23.944759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:15:23.944834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:15:24.096566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:15:54.096038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:16:23.971068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:16:23.971133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:16:24.096033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:16:54.096106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:17:23.997355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:17:23.997416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:17:24.096074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:17:54.095992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:18:24.027803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:18:24.028154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:18:24.096056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:18:54.096004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:19:24.053381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:19:24.053442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:19:24.096233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:19:54.096113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:20:24.081784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:20:24.082157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:20:24.096034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:20:54.095951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:21:24.095879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:21:24.117344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:21:24.117482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:21:54.096002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:22:24.096248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:22:24.155217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:22:24.155289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:22:54.096118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:23:24.096202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:23:24.182101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:23:24.182167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:23:54.095929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:24:24.097264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:24:24.217260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:24:24.217326 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:24:54.095951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:25:24.096192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:25:24.240389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:25:24.240484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:25:54.095970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:26:24.096038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:26:24.264595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:26:24.264667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:26:54.095998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:27:24.096999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:27:24.300847 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:27:24.300921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:27:54.096196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:28:24.096056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:28:26.330596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:28:26.330767 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:28:54.096065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:29:24.098528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:29:26.352956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:29:26.353008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:29:54.095961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:30:24.096131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:30:26.375287 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:30:26.375369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:30:54.096133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:31:24.096161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:31:26.396804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:31:26.396841 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:31:54.096157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:32:24.096024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:32:26.425632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:32:26.425722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:32:54.096052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:33:24.098944 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:33:26.450784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:33:26.450830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:33:54.096112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:34:24.096007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:34:26.478312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:34:26.478356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:34:54.096018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:35:24.095966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:35:26.520331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:35:26.520388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:35:54.096068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:36:24.096114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:36:26.543986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:36:26.544026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:36:54.096100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:37:24.096080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:37:26.571940 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:37:26.571989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:37:54.096204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:38:24.096089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:38:26.596783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:38:26.596827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:38:54.096035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:39:24.096257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:39:26.622782 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:39:26.622833 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:39:54.095980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:40:24.096107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:40:26.646398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:40:26.648036 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:40:54.096156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:41:24.096301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:41:26.674294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:41:26.674335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:41:54.096015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:42:24.096214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:42:26.746346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:42:26.746383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:42:54.095968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:43:24.096012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:43:26.769648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:43:26.769689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:43:54.095962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:44:24.098013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:44:26.793599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:44:26.793667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:44:54.095993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:45:24.096724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:45:26.814135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:45:26.814174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:45:54.096063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:46:24.096051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:46:26.848702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:46:26.848781 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:46:54.096009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:47:24.096072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:47:26.875861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:47:26.875913 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:47:54.096182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:48:24.096074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:48:26.897630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:48:26.897682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:48:54.096107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:49:24.096028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:49:26.921025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:49:26.921073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:49:54.096107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:50:24.096030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:50:26.946458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:50:26.946499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:50:54.096104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:51:24.099070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:51:27.000821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:51:27.001019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:51:54.096093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:52:24.096255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:52:27.055878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:52:27.055919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:52:54.096075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:53:24.096148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:53:27.092256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:53:27.092303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:53:54.095985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:54:24.096024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:54:27.128380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:54:27.128436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:54:54.096022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:55:24.096033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:55:27.154360 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:55:27.154401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:55:54.097286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:56:24.096010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:56:27.184577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:56:27.184620 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:56:54.096015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:57:24.095955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:57:27.221852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:57:27.221911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:57:54.096039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:58:24.095931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:58:27.270850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:58:27.270891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:58:54.096152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:59:24.096054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 04:59:27.312817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:59:27.312858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 04:59:54.095959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:00:24.096214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:00:27.352045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:00:27.352109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:00:54.096725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:01:24.096068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:01:27.385232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:01:27.385463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:01:54.096090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:02:24.102151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:02:27.410712 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:02:27.410777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:02:54.096120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:03:24.096176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:03:27.438913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:03:27.439089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:03:54.098048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:04:24.095966 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:04:27.467785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:04:27.467823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:04:54.096131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:05:24.096358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:05:27.498928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:05:27.498977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:05:54.095996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:06:24.096038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:06:27.540698 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:06:27.540746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:06:54.096022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:07:24.096016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/18 05:07:27.565748 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:07:27.565884 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/18 05:07:54.096013 metrics.go:34: INFO No non-zero metrics in the last 30s