By type
2022/03/19 03:38:45.481977 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/03/19 03:38:45.482157 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/19 03:38:45.482307 logstash.go:90: INFO Max Retries set to: 3
2022/03/19 03:38:45.482495 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/19 03:38:45.482675 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-tfmxg
2022/03/19 03:38:45.482943 async.go:63: INFO Flush Interval set to: 1s
2022/03/19 03:38:45.482977 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/19 03:38:45.483932 metrics.go:23: INFO Metrics logging every 30s
2022/03/19 03:38:45.486715 beat.go:221: INFO filebeat start running.
2022/03/19 03:38:45.486800 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/19 03:38:45.490697 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/19 03:38:45.490782 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/19 03:38:45.490834 crawler.go:38: INFO Loading Prospectors: 1
2022/03/19 03:38:45.491011 registrar.go:236: INFO Starting Registrar
2022/03/19 03:38:45.491232 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/19 03:38:45.491209 sync.go:41: INFO Start sending events to output
2022/03/19 03:38:45.491302 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/19 03:38:45.491436 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/19 03:38:45.491566 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/19 03:39:05.494084 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/19 03:39:05.494383 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/19 03:39:05.494476 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/19 03:39:05.494538 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/19 03:39:05.494576 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/19 03:39:10.554720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:10.554814 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:11.560991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:11.561034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:13.574241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:13.574280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:15.484444 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=72 registrar.writes=1
2022/03/19 03:39:17.608621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:17.608700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:25.620583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:25.620668 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:41.648405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:41.648461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:39:45.484292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:40:13.676410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:40:13.676446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:40:15.484267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:40:45.484280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:41:13.701062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:41:13.701142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:41:15.484562 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:41:45.484246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:42:13.723508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:13.723561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:42:15.484366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:42:45.484293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:43:13.749980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:43:13.750014 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:43:15.484213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:43:45.484241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:44:10.513413 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/19 03:44:13.802684 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:44:13.802720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:44:15.484431 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/19 03:44:45.484266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:45:13.824649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:45:13.824687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:45:15.484413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:45:45.484289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:46:13.866229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:46:13.866278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:46:15.484266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:46:45.484451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:47:13.934201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:47:13.934256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:47:15.484289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:47:45.484245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:48:14.009699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:48:14.009946 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:48:15.484279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:48:45.485379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:49:14.044880 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:49:14.044935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:49:15.484199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:49:45.485501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:50:14.068572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:50:14.068611 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:50:15.484228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:50:45.484232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:51:14.112637 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:51:14.112672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:51:15.484466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:51:45.484326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:52:14.135405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:52:14.135446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:52:15.484249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:52:45.484285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:53:14.160635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:53:14.160674 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:53:15.484251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:53:45.484230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:54:14.192580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:54:14.192618 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:54:15.484306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:54:45.484361 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:55:14.227906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:55:14.227966 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:55:15.484242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:55:45.484264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:56:14.260276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:56:14.260329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:56:15.484439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:56:45.484261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:57:14.282282 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:57:14.282420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:57:15.484314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:57:45.484263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:58:14.327586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:58:14.327621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:58:15.484300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:58:45.484342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:59:14.354695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:59:14.354747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 03:59:15.484286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 03:59:45.484263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:00:14.382073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:00:14.382117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:00:15.484368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:00:45.484530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:01:14.411468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:01:14.411522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:01:15.484344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:01:45.484356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:02:14.435600 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:02:14.435654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:02:15.484304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:02:45.484308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:03:14.465033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:03:14.465075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:03:15.484259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:03:45.484311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:04:14.485073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:04:14.485144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:04:15.484218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:04:45.484679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:05:14.518746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:05:14.518798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:05:15.484182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:05:45.484483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:06:14.545316 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:06:14.545370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:06:15.485328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:06:45.484302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:07:14.591943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:07:14.591991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:07:15.484276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:07:45.484365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:08:14.622648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:08:14.622700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:08:15.484240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:08:45.484262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:09:14.646327 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:09:14.646373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:09:15.484326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:09:45.484454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:10:14.680947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:10:14.680989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:10:15.484368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:10:45.484293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:11:14.703786 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:11:14.703822 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:11:15.484389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:11:45.484249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:12:14.727231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:12:14.727285 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:12:15.484345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:12:45.484215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:13:14.749142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:13:14.749191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:13:15.484252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:13:45.484230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:14:14.770567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:14:14.770608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:14:15.484257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:14:45.484239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:15:14.811237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:15:14.811302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:15:15.484270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:15:45.484285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:16:14.839140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:16:14.839173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:16:15.484384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:16:45.484314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:17:14.859367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:17:14.859406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:17:15.484307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:17:45.485315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:18:14.880680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:18:14.880717 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:18:15.484299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:18:45.484252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:19:14.910623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:19:14.910681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:19:15.484309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:19:45.484298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:20:14.929147 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:20:14.929182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:20:15.484263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:20:45.484680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:21:14.949661 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:21:14.949714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:21:15.484399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:21:45.484302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:22:14.982597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:22:14.982647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:22:15.484291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:22:45.484326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:23:15.002473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:23:15.002518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:23:15.484300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:23:45.484217 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:24:15.027443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:24:15.027497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:24:15.484268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:24:45.484272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:25:15.052317 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:25:15.052435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:25:15.484320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:25:45.484332 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:26:15.076493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:26:15.076563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:26:15.484359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:26:45.484319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:27:15.110815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:27:15.110870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:27:15.484316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:27:45.484267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:28:15.131644 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:28:15.131725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:28:15.484448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:28:45.484246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:29:15.152863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:29:15.152974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:29:15.484352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:29:45.484282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:30:15.172480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:30:15.172520 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:30:15.484321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:30:45.484421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:31:15.194919 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:31:15.194970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:31:15.484370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:31:45.484339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:32:15.220406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:32:15.220444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:32:15.484294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:32:45.484272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:33:15.277747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:33:15.277793 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:33:15.484234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:33:45.484268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:34:15.303586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:34:15.303638 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:34:15.484270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:34:45.485568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:35:15.324654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:35:15.324704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:35:15.484282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:35:45.484331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:36:15.347271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:36:15.347314 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:36:15.484263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:36:45.484291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:37:15.373625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:37:15.373670 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:37:15.485506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:37:45.484325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:38:15.393943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:38:15.393990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:38:15.484324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:38:45.484295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:39:15.415941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:39:15.415993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:39:15.484278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:39:45.484262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:40:15.444745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:40:15.444776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:40:15.484208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:40:45.484399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:41:15.463400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:41:15.463450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:41:15.484293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:41:45.484400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:42:15.484281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:42:15.489400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:42:15.489517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:42:45.484254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:43:15.484245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:43:15.516484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:43:15.516523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:43:45.484389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:44:15.484270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:44:15.541414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:44:15.541453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:44:45.484419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:45:15.484472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:45:15.584815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:45:15.584852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:45:45.484247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:46:15.484241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:46:15.612106 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:46:15.612161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:46:45.484182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:47:15.484238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:47:15.651153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:47:15.651212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:47:45.484669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:48:15.484247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:48:15.685706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:48:15.685760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:48:45.484284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:49:15.484229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:49:15.709030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:49:15.709147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:49:45.484482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:50:15.484290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:50:15.749366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:50:15.749416 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:50:45.484317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:51:15.484289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:51:15.770352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:51:15.770381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:51:45.484196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:52:15.484330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:52:15.799053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:52:15.799095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:52:45.484333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:53:15.484427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:53:15.842468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:53:15.842508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:53:45.484259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:54:15.484281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:54:15.877145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:54:15.877201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:54:45.484320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:55:15.484250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:55:15.925596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:55:15.925637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:55:45.484319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:56:15.484290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:56:15.968704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:56:15.968757 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:56:45.484262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:57:15.484267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:57:16.016331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:57:16.016373 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:57:45.484270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:58:15.484280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:58:16.039344 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:58:16.039382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:58:45.484317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:59:15.484311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 04:59:16.079414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:59:16.079457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 04:59:45.484304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:00:15.484512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:00:16.119437 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:00:16.119491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:00:45.484248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:01:15.484303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:01:16.193178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:01:16.193222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:01:45.484802 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:02:15.484226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:02:16.196302 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:02:16.196332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:02:45.484333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:03:15.484437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:03:16.203743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:03:16.203794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:03:45.484253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:04:15.484265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:04:16.207035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:04:16.207071 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:04:45.484284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:05:15.484282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:05:16.211494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:05:16.211537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:05:45.484260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:06:15.484275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:06:16.215219 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:06:16.215260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:06:45.484186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:07:15.484309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:07:16.218928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:07:16.218981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:07:45.484387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:08:15.484214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:08:16.224232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:08:16.224375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:08:45.484329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:09:15.484228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:09:16.228388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:09:16.228479 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:09:45.484479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:10:15.484213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:10:16.232038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:10:16.232079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:10:45.484287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:11:15.484252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:11:16.236125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:11:16.236159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:11:45.484288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:12:15.484275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:12:16.247134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:12:16.247196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:12:45.484351 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:13:15.484366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:13:16.251335 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:13:16.251381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:13:45.484222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:14:15.484311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:14:16.254699 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:14:16.254749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:14:45.484194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:15:15.484272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:15:16.261581 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:15:16.261624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:15:45.484262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:16:15.485702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:16:16.267490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:16:16.267522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:16:45.484306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:17:15.484266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:17:16.278354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:17:16.278386 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:17:45.484301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:18:15.484629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:18:16.282787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:18:16.282819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:18:45.484446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:19:15.484327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:19:16.288297 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:19:16.288329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:19:45.484319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:20:15.484277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:20:16.292524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:20:16.292567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:20:45.484339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:21:15.484248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:21:16.298741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:21:16.298780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:21:45.484274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:22:15.484288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:22:16.302819 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:22:16.302861 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:22:45.484496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:23:15.484254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:23:16.306086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:23:16.306124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:23:45.484255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:24:15.484334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:24:16.310414 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:24:16.310449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:24:45.484413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:25:15.484198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:25:16.314935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:25:16.314993 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:25:45.484245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:26:15.484321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:26:16.319377 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:26:16.319430 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:26:45.484766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:27:15.484383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:27:16.325484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:27:16.325539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:27:45.484449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:28:15.484246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:28:16.329494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:28:16.329527 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:28:45.484315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:29:15.484300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:29:16.333394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:29:16.333449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:29:45.484208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:30:15.484206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:30:16.338123 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:30:16.338309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:30:45.484355 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:31:15.484262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:31:16.342592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:31:16.342648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:31:45.484394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:32:15.484379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:32:16.346927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:32:16.346981 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:32:45.484348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:33:15.484253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:33:16.351200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:33:16.351257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:33:45.484260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:34:15.484284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:34:16.355150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:34:16.355191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:34:45.484291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:35:15.484268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:35:16.360793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:35:16.360855 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:35:45.484330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:36:15.484306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:36:16.365804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:36:16.365854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:36:45.484222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:37:15.484266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:37:16.369613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:37:16.369667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:37:45.484313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:38:15.484348 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:38:16.374491 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:38:16.374538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:38:45.484252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:39:15.484590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:39:16.380878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:39:16.380911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:39:45.484249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:40:15.484403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:40:16.387083 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:40:16.387130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:40:45.484260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:41:15.484956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:41:16.391428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:41:16.391489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:41:45.484329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:42:15.484267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:42:16.395510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:42:16.395552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:42:45.484299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:43:15.484701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:43:16.399739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:43:16.399775 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:43:45.484270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:44:15.484394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:44:16.403594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:44:16.403628 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:44:45.484182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:45:15.484326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:45:16.409831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:45:16.409866 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:45:45.484257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:46:15.484267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:46:16.413443 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:46:16.413496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:46:45.484294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:47:15.484576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:47:16.419128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:47:16.419170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:47:45.484394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:48:15.484288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:48:16.423836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:48:16.423901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:48:45.484420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:49:15.484312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:49:16.428513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:49:16.428568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:49:45.484343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:50:15.484451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:50:16.432431 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:50:16.432474 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:50:45.484322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:51:15.484928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:51:16.440099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:51:16.440152 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:51:45.484205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:52:15.484244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/19 05:52:16.445694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/19 05:52:16.445731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host