2022/01/14 03:35:22.749453 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/14 03:35:22.749509 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/14 03:35:22.749686 metrics.go:23: INFO Metrics logging every 30s
2022/01/14 03:35:22.749696 logstash.go:90: INFO Max Retries set to: 3
2022/01/14 03:35:22.749840 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/14 03:35:22.749964 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-ghblt
2022/01/14 03:35:22.750198 async.go:63: INFO Flush Interval set to: 1s
2022/01/14 03:35:22.750230 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/14 03:35:22.750718 beat.go:221: INFO filebeat start running.
2022/01/14 03:35:22.750838 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/14 03:35:22.870849 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/14 03:35:22.870968 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/14 03:35:22.871017 crawler.go:38: INFO Loading Prospectors: 1
2022/01/14 03:35:22.871186 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/14 03:35:22.871207 registrar.go:236: INFO Starting Registrar
2022/01/14 03:35:22.871266 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/14 03:35:22.871279 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/14 03:35:22.871328 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/14 03:35:22.871277 sync.go:41: INFO Start sending events to output
2022/01/14 03:35:22.872037 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/14 03:35:22.872126 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/14 03:35:22.872247 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/14 03:35:22.872266 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/14 03:35:22.872272 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/14 03:35:22.920355 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:22.920385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:23.923742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:23.923771 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:25.927087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:25.927136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:29.932721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:29.932766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:37.941963 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:37.942017 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:52.750040 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/14 03:35:53.950016 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:35:53.950062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:36:22.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:36:25.955905 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:36:25.955938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:36:52.750121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:37:22.750127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:37:25.963367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:37:25.963415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:37:52.750069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:38:22.750075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:38:25.971051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:38:25.971096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:38:52.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:39:22.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:39:25.981522 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:39:25.981585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:39:52.750061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:40:22.749985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:40:25.988624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:40:25.988660 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:40:27.882713 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/14 03:40:52.750146 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/14 03:41:22.750097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:41:25.996991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:41:25.997024 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:41:52.749992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:42:22.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:42:26.003912 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:42:26.003945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:42:52.750591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:43:22.750068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:43:26.019848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:43:26.019971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:43:52.750044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:44:22.750086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:44:26.027849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:44:26.027885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:44:52.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:45:22.750125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:45:26.035800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:45:26.035835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:45:52.750036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:46:22.749986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:46:26.043261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:46:26.043285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:46:52.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:47:22.750061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:47:26.051224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:47:26.051259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:47:52.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:48:22.749952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:48:26.058219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:48:26.058264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:48:52.750076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:49:22.750039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:49:26.066605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:49:26.066646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:49:52.750063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:50:22.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:50:26.074291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:50:26.074329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:50:52.750004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:51:22.750049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:51:26.081852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:51:26.081882 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:51:52.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:52:22.750111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:52:26.089007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:52:26.089038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:52:52.750008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:53:22.750021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:53:26.099578 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:53:26.099688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:53:52.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:54:22.750081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:54:26.107447 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:54:26.107479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:54:52.750124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:55:22.750139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:55:26.115627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:55:26.115685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:55:52.750034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:56:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:56:26.123660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:56:26.123705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:56:52.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:57:22.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:57:26.132445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:57:26.132487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:57:52.750110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:58:22.750126 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:58:26.139856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:58:26.139889 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:58:52.750063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:59:22.750082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 03:59:26.148216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:59:26.148247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 03:59:52.750241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:00:22.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:00:26.156364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:00:26.156395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:00:52.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:01:22.750001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:01:26.170948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:01:26.170993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:01:52.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:02:22.750058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:02:26.179314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:02:26.179366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:02:52.750048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:03:22.749978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:03:26.187286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:03:26.187318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:03:52.750056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:04:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:04:26.194852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:04:26.194892 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:04:52.749999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:05:22.749971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:05:26.203968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:05:26.204018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:05:52.750062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:06:22.750028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:06:26.210880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:06:26.210919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:06:52.750033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:07:22.750059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:07:26.222558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:07:26.222594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:07:52.750080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:08:22.750025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:08:26.229714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:08:26.229769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:08:52.750006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:09:22.750509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:09:26.238199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:09:26.238230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:09:52.750048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:10:22.750081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:10:26.245819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:10:26.245851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:10:52.750028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:11:22.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:11:26.255173 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:11:26.255204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:11:52.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:12:22.750025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:12:26.262755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:12:26.262806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:12:52.750022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:13:22.749948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:13:26.273761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:13:26.273803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:13:52.750043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:14:22.749973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:14:26.280871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:14:26.280903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:14:52.750006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:15:22.750035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:15:26.291689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:15:26.291722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:15:52.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:16:22.749999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:16:26.298727 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:16:26.298754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:16:52.749999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:17:22.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:17:26.306991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:17:26.307031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:17:52.749988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:18:22.750049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:18:26.315608 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:18:26.315638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:18:52.750023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:19:22.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:19:26.324705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:19:26.324741 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:19:52.750032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:20:22.749975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:20:26.331306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:20:26.331335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:20:52.749997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:21:22.750042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:21:26.339992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:21:26.340021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:21:52.750022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:22:22.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:22:26.346599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:22:26.346635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:22:52.749997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:23:22.750071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:23:26.355319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:23:26.355349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:23:52.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:24:22.749979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:24:26.363398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:24:26.363433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:24:52.750050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:25:22.749960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:25:26.373962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:25:26.374006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:25:52.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:26:22.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:26:26.380887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:26:26.380918 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:26:52.750036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:27:22.750004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:27:26.390026 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:27:26.390079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:27:52.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:28:22.750048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:28:26.398744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:28:26.398813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:28:52.750051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:29:22.751873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:29:26.408440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:29:26.408470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:29:52.750114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:30:22.750041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:30:26.417366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:30:26.417413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:30:52.750056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:31:22.750014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:31:26.424943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:31:26.424977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:31:52.750029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:32:22.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:32:26.432779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:32:26.432806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:32:52.749973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:33:22.750103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:33:26.446396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:33:26.446441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:33:52.750042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:34:22.750049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:34:26.453177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:34:26.453220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:34:52.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:35:22.750014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:35:26.460588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:35:26.460618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:35:52.750059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:36:22.750002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:36:26.467350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:36:26.467382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:36:52.750068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:37:22.750067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:37:26.476466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:37:26.476498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:37:52.750063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:38:22.750033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:38:26.484184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:38:26.484220 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:38:52.750035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:39:22.750070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:39:26.494286 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:39:26.494312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:39:52.750049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:40:22.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:40:26.502299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:40:26.502330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:40:52.750019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:41:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:41:26.513314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:41:26.513350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:41:52.750085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:42:22.750000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:42:26.521451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:42:26.521491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:42:52.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:43:22.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:43:26.530653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:43:26.530688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:43:52.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:44:22.750096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:44:26.537764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:44:26.537796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:44:52.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:45:22.750058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:45:26.547838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:45:26.547911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:45:52.749968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:46:22.749998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:46:26.554469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:46:26.554508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:46:52.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:47:22.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:47:26.567441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:47:26.567476 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:47:52.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:48:22.750062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:48:26.612114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:48:26.612162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:48:52.750042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:49:22.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:49:26.620288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:49:26.620316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:49:52.750048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:50:22.750045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:50:26.627291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:50:26.627320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:50:52.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:51:22.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:51:26.635449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:51:26.635484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:51:52.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:52:22.749996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:52:26.646365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:52:26.646393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:52:52.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:53:22.749998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:53:26.653812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:53:26.653846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:53:52.750062 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:54:22.750043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:54:26.661232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:54:26.661263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:54:52.750000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:55:22.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:55:26.668990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:55:26.669092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:55:52.750042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:56:22.749978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:56:26.677180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:56:26.677216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:56:52.750067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:57:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:57:26.686823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:57:26.686860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:57:52.750009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:58:22.750074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:58:26.693674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:58:26.693707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:58:52.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:59:22.749992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 04:59:26.702172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:59:26.702213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 04:59:52.750090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:00:22.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:00:26.709064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:00:26.709103 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:00:52.749994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:01:22.750004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:01:26.720749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:01:26.720789 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:01:52.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:02:22.749965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:02:26.730351 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:02:26.730434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:02:52.750081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:03:22.750008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:03:26.739746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:03:26.739780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:03:52.750050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:04:22.750057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:04:26.747833 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:04:26.747868 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:04:52.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:05:22.750032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:05:26.755079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:05:26.755117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:05:52.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:06:22.749982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:06:26.762259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:06:26.762291 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:06:52.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:07:22.750004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:07:26.771119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:07:26.771156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:07:52.750035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:08:22.750998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:08:26.778716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:08:26.778748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:08:52.750034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:09:22.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:09:26.788875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:09:26.788910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:09:52.750068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:10:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:10:26.795687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:10:26.795719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:10:52.750076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:11:22.749986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:11:26.804997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:11:26.805031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:11:52.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:12:22.750063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:12:26.811846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:12:26.811872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:12:52.749986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:13:22.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:13:26.820721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:13:26.820750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:13:52.750107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:14:22.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:14:26.827985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:14:26.828018 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:14:52.750025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:15:22.750012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:15:26.838766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:15:26.838793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:15:52.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:16:22.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:16:26.847530 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:16:26.847559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:16:52.750076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:17:22.750131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:17:26.856613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:17:26.856643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:17:52.750034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:18:22.750076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:18:26.864078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:18:26.864107 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:18:52.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:19:22.750041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:19:26.874741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:19:26.874768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:19:52.750009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:20:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:20:26.881186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:20:26.881214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:20:52.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:21:22.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:21:26.890852 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:21:26.890885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:21:52.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:22:22.749939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:22:26.897555 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:22:26.897610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:22:52.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:23:22.750071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:23:26.912499 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:23:26.912536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:23:52.750036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:24:22.750028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:24:26.920316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:24:26.920356 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:24:52.749984 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:25:22.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:25:26.928915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:25:26.928954 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:25:52.750073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:26:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:26:26.935945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:26:26.935986 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:26:52.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:27:22.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:27:26.943862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:27:26.943899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:27:52.750021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:28:22.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:28:26.950985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:28:26.951025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:28:52.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:29:22.750022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:29:26.958103 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:29:26.958133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:29:52.750021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:30:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:30:26.965081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:30:26.965111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:30:52.750517 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:31:22.750014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:31:26.973542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:31:26.973577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:31:52.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:32:22.749975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:32:26.980918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:32:26.980952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:32:52.750040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:33:22.749985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:33:26.994336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:33:26.994364 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:33:52.749975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:34:22.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:34:27.001209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:34:27.001243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:34:52.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:35:22.750034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:35:27.013275 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:35:27.013307 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:35:52.750076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:36:22.750008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:36:27.019831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:36:27.019864 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:36:52.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:37:22.750083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:37:27.029974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:37:27.030004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:37:52.750004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:38:22.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:38:27.037509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:38:27.037550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:38:52.750046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:39:22.750113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:39:27.050376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:39:27.050433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:39:52.749988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:40:22.750025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:40:27.058308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:40:27.058339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:40:52.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:41:22.750048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:41:27.069799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:41:27.069827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:41:52.750029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:42:22.750005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:42:27.078569 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:42:27.078605 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:42:52.750119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:43:22.749982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:43:27.087716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:43:27.087752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:43:52.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:44:22.750020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:44:27.094864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:44:27.094900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:44:52.750023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:45:22.751052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:45:27.107242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:45:27.107271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:45:52.750109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:46:22.750014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:46:27.115264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:46:27.115296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:46:52.750107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:47:22.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:47:27.126346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:47:27.126371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:47:52.749999 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:48:22.750091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:48:27.140870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:48:27.140917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:48:52.750036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:49:22.750020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:49:27.150653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:49:27.150687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:49:52.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:50:22.749957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:50:27.157065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:50:27.157098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:50:52.750000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:51:22.750069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:51:27.165367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:51:27.165413 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:51:52.750077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:52:22.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:52:27.173599 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:52:27.173640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:52:52.750068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:53:22.749951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:53:27.183703 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:53:27.183733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:53:52.749974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:54:22.750137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:54:27.191514 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:54:27.191545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:54:52.750047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:55:22.750014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:55:27.201557 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:55:27.201603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:55:52.750040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:56:22.749955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:56:27.208805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:56:27.208837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:56:52.749989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:57:22.750025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:57:27.217879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:57:27.217919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:57:52.750216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:58:22.750002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:58:27.225635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:58:27.225662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:58:52.750602 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:59:22.750093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 05:59:27.241655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:59:27.241685 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 05:59:52.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:00:22.750020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:00:27.249269 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:00:27.249309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:00:52.749970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:01:22.750005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:01:27.259294 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:01:27.259333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:01:52.750037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:02:22.750044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:02:27.268627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:02:27.268661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:02:52.750030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:03:22.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:03:27.277740 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:03:27.277776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:03:52.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:04:22.749962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:04:27.285523 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:04:27.285663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:04:52.749983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:05:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:05:27.296663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:05:27.296706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:05:52.750027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:06:22.750111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:06:27.304931 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:06:27.304965 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:06:52.750028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:07:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:07:27.317420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:07:27.317456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:07:52.750015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:08:22.750043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:08:27.328063 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:08:27.328094 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:08:52.750046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:09:22.750047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:09:27.337162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:09:27.337201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:09:52.750028 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:10:22.750031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:10:27.345284 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:10:27.345310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:10:52.750010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:11:22.750075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:11:27.354651 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:11:27.354676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:11:52.750023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:12:22.749982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:12:27.363201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:12:27.363230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:12:52.750048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:13:22.749998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:13:27.372612 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:13:27.372650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:13:52.750009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:14:22.750067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:14:27.380240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:14:27.380277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:14:52.750073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:15:22.749994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:15:27.389212 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:15:27.389243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:15:52.750041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:16:22.749974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:16:27.396457 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:16:27.396518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:16:52.750132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:17:22.750042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:17:27.413491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:17:27.413524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:17:52.750046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:18:22.750106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:18:27.420992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:18:27.421031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:18:52.750055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:19:22.749993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:19:27.428535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:19:27.428561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:19:52.750083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:20:22.750058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:20:27.434911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:20:27.434971 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:20:52.750071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:21:22.750085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:21:27.442456 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:21:27.442494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:21:52.750090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:22:22.749993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:22:27.449687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:22:27.449724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:22:52.750128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:23:22.750076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:23:27.458184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:23:27.458233 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:23:52.750034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:24:22.750031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:24:27.465019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:24:27.465048 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:24:52.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:25:22.749941 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:25:27.476370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:25:27.476409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:25:52.750071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:26:22.750020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:26:27.483370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:26:27.483403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:26:52.750087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:27:22.749975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:27:27.491242 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:27:27.491286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:27:52.750006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:28:22.750117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:28:27.498521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:28:27.498543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:28:52.749990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:29:22.750051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:29:27.506763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:29:27.506787 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:29:52.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:30:22.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:30:27.514592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:30:27.514931 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:30:52.749990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:31:22.750010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:31:27.522230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:31:27.522259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:31:52.749965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:32:22.749979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:32:27.527794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:32:27.527831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:32:52.750019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:33:22.750021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:33:27.536501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:33:27.536534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:33:52.750025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:34:22.750053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:34:27.542533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:34:27.542564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:34:52.750005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:35:22.750069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:35:27.552089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:35:27.552127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:35:52.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:36:22.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:36:27.558669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:36:27.558795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:36:52.750021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:37:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:37:27.567644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:37:27.567667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:37:52.750060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:38:22.750006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:38:27.574927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:38:27.575021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:38:52.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:39:22.750072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:39:27.581936 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:39:27.581963 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:39:52.750081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:40:22.750047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:40:27.588485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:40:27.588507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:40:52.750082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:41:22.750040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:41:27.596674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:41:27.596697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:41:52.750010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:42:22.750068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:42:27.602314 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:42:27.602352 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:42:52.750042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:43:22.750022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:43:27.611526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:43:27.611556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:43:52.750162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:44:22.750074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:44:27.617665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:44:27.617697 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:44:52.750068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:45:22.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:45:27.629949 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:45:27.629977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:45:52.750073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:46:22.750169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:46:27.635891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:46:27.635915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:46:52.750031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:47:22.750094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:47:27.644256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:47:27.644286 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:47:52.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:48:22.750080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:48:27.650348 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:48:27.650378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:48:52.750014 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:49:22.750083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:49:27.658975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:49:27.659029 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:49:52.749988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:50:22.750050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:50:27.667942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:50:27.667974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:50:52.750036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:51:22.750039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:51:27.677488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:51:27.677635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:51:52.750940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:52:22.749986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:52:27.682549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:52:27.682575 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:52:52.749994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:53:22.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:53:27.690605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:53:27.690717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:53:52.750147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:54:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:54:27.695274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:54:27.695301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:54:52.750141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:55:22.750038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:55:27.702911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:55:27.702947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:55:52.750010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:56:22.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:56:27.708038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:56:27.708074 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:56:52.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:57:22.750066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:57:27.715633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:57:27.715663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:57:52.750067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:58:22.750084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:58:27.720718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:58:27.720764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:58:52.750066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:59:22.750069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 06:59:27.728534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:59:27.728569 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 06:59:52.749972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:00:22.750029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:00:27.735320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:00:27.735416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:00:52.750136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:01:22.750011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:01:27.743634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:01:27.743748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:01:52.750053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:02:22.750052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:02:27.752982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:02:27.753010 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:02:52.750033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:03:22.749994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:03:27.758105 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:03:27.758140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:03:52.750046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:04:22.750036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:04:27.764347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:04:27.764383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:04:52.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:05:22.750007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:05:27.770285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:05:27.770312 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:05:52.750039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:06:22.750026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:06:27.827288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:06:27.827329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:06:52.750040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:07:22.750000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:07:27.834674 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:07:27.834702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:07:52.750054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:08:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:08:27.840403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:08:27.840433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:08:52.750013 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:09:22.750018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:09:27.848064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:09:27.848106 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:09:52.750009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:10:22.750016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:10:27.853601 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:10:27.853640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:10:52.750047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:11:22.750044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:11:27.859579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:11:27.859612 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:11:52.750000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:12:22.750017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:12:27.864404 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:12:27.864440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:12:52.750024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:13:22.749995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:13:27.872544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:13:27.872580 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:13:52.750022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:14:22.750003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:14:27.880501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:14:27.880539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:14:52.750009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:15:22.749994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/14 07:15:27.888816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/14 07:15:27.888849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host